At my office, we heavily lean on Postgres' JSONB capabilities, especially for archived data that is occasionally accessed, and also to handle data dumps from other services. The JSONB traversal operators are intuitive and the searching is fast-enough to be useful. Yet another reason that I reach for Postgres first time, every time.
I was a young teen when it first came out -- in retrospect, I think it's cool, but at the time, everybody I knew felt like it was baldly pandering to our demographic / 'disaffected slackers' in general, and looked upon it with mild disdain
My guess based on context is that "FNP" refers to the indigenous people of Australia [maybe 'First Nations People?' -- however that term is more generally used in North America, to my knowledge], but that acronym isn't present in the article. Would you clarify for our benefit please?
It does indeed refer to the indigenous people of Australia, and is a general term used by many indigenous people who were displaced by colonisation in Australia, the USA and Canada. Australian Aboriginal People use this term freely - I believe it is politically leveraged in a contemporary context to indicate alignment with other displaced peoples around the world. Euro-Australians are generally not as content with the use of this phrase, since it indicates a path to sovereignty and serves as a reminder of Australia's rough past.
However, from the FNP-side, it is considered better than the phrases "Aborigine" or "Indigenous", since these phrases can be used to refer to the condition of various flora and fauna, and thus de-humanizes the subject. The FN people in my family prefer that I refer to them thus as FNP.
There is a better guideline for how this should be addressed, because as you no doubt can understand, its a sensitive issue:
"Similarly to above ('First Australians'), 'First Nations' recognises Aboriginal and Torres Strait Islander people as the sovereign people of this land. It goes further than 'First Australians' as it recognises various language groups as separate and unique sovereign nations. It is widely used to describe the First Peoples in Canada and other countries across the globe. Over recent years, the use of this term has grown in popularity. It is a better choice than many outdated and offensive terms described above."
I haven't once heard 'First Nations People' used on the ground other than by visiting speakers (usually from overseas). Indigenous & Koorie are the most common terms used here (I live in the Northern Rivers - Bundjalung country).
Well, I learned it from my FNP relatives, who much prefer it over "Aborigine" or "Indigenous" - as these terms have become very loaded, and there is the desire to indicate that the people who were displaced by European colonisation were indeed the first sovereign nation on the continent. YMMV.
The "first nations" phrase is used frequently on aboriginal radio in perth (Noongar fm 100.9) At least half the people they talk to are from the eastern states, so I don't think that the phrase is unusual (at least among the sort of people who get interviewed on radio stations).
Sure, I'm just saying I don't hear it 'on the street' where I live. I honestly find the whole officially-approved nomenclature issue a bit overblown anyway. I'm completely happy to use whatever people prefer, but have known enough rednecks who can inflect racism into entitrely innocuous language, to feel that 'correct' word choice is a pretty small determinant of what's communicated. At least beyond the twitterverse.
we have a lesson_log channel [with standard entry format] in slack -- for all Slack's shortcomings, this works great, as the whole team can see lessons learned from every department
Yep, same here. I planned to buy a Tesla for environmental reasons when my current 15-year-old car gives up the ghost, but I had no clue about the sort of shenanigans described here.
There is absolutely no way I'd knowingly "buy" a car [or other major product, for that matter] which was subject to this sort of postsale unilateral manipulation on the part of the manufacturer / seller.
To my way of thinking, it's similar, but much worse, than the situation with HOAs [which I also decline to support]
edit: I'd already started switching to bike for commute and errands; now I'm even more inclined to continue in that direction rather than look to EVs
I've worked in both open and closed office environments -- currently have my own office, and it is _much_ easier for me to be productive without distractions in this arrangement. Huge improvement in quality of work and quality of life. It's possible that I could be persuaded to go back to an open-office environment, but it would require a _lot_ of additional compensation -- like maybe 50+%.
yep -- Centos [which distro I favor for servers] is verrry slow with patches, upgrades, and other additions -- but it is 100% rock solid with no surprises. I use other distros for desktop and various uses, but for servers, I stick with CentOS for stability [or Debian, if CentOS not available]
A big +1 to the suggestion about ear training; I sure wish I'd pursued it more seriously and earlier -- probably no other activity can transform one's understanding and ability to the degree ear training can, not to mention it makes one _much_ more able to play + improvise in a group setting --
Finding a beginning book / course / etc that engagingly + logically shows the relationships between scales and chords, modes, etc, and addresses some aspects of rhythm, was immensely helpful for me -- if it uses your instrument, so much the better -- mine was Richard Chapman's "The Complete Guitarist"
Once you have the basics in hand, there are a lot of elucidating paths available to follow, but one book on counterpoint that absolutely _turned my head around_ is Joseph Fux' "Steps to Parnassus" also called "The Study of Counterpoint" -- total lightbulb --
I also strongly recommend Aaron Copland's "How to Listen to Music"
I like JS. I use JS daily. JS is part of the workflow for nearly everyone I know who works with code. For me, ES6 is fantastic to use. Some of the better books on JS [I'm thinking specifically of Haverbeke's "Eloquent Javascript"] are general computing classics in their own right.
I used to be a snob about JS, due to the fact that in the 90s / early 2000s, it had major shortcomings and produced a lot of slow, crashy web pages. But when I learned modern JS, I realized that it is now a fully mature language equal to any other, and easily used in a huge variety of contexts [thanks in no small part to Node]
I have to use Javascript almost daily at work, I hate it.
Up until a year ago or so I hadn't really had to use it much, I'm finding it so bad I'm seriously looking at how I can get into an alternate career. Working with JS is a profoundly miserable experience.
Previously I was working on C# and SQL. I'm no fan of either of those, but at least with C# I can understand what the designers were thinking. Ideally I would be working in Clojure if it was up to me. Or Scala or F#.
Now it's Javascript as that is the code base our client uses. The client runs a number of production factories and have an internal web app that is mostly Javascript on the front end for monitoring these production lines.
It's made me angrily punch my desk and consider just quitting on the spot on a number of occasions.
I don't know how anyone tolerates using this day to day and doesn't want to jump off the roof. It's absolutely idiotic.
JS is a terrible language. The amount of pitfalls, language features you must avoid, and obscure paradigms you must follow to make JS usable is mind-boggling. Just because you can use JS well doesn't mean it's a good language.
