I assume that - even though there's a strong public interest argument for it - government orgs are prone to blanket banning the release of source code, for the same primary reason that businesses are prone to doing so. That is, too high a chance of sensitive data (passwords, tokens, IP addresses, etc) being hard-coded in all-too-often non-12-factor-aspiring code; and too much security / liability headache if said sensitive data gets out.
There's probably also some actual business logic that government orgs want to and are legally permitted to keep secret. In the OP's case of a parking ticket database, maybe there's software talking to that database, whose source code includes the logic of picking when / where parking inspectors should conduct a "random" blitz of issuing fines.
I've still got Signal installed, but never use it, I only ever ended up chatting on it with a few ex-colleagues, who were fellow devs / nerds.
I have so many WhatsApp group chats (here in Australia) that are critical for me these days, and that I don't control, and that have way too many people, and way too diverse a range of people, for me to have any hope whatsoever of migrating them all to Signal. School parents group chats (one for each class that my kids are in). Strata (aka Home Owners Association) committee group chat. Scouts group chat. Various friends groups chats. Boycotting WhatsApp is not an option for me, it would literally make me unable to function in a number of my day-to-day responsibilities.
Yes, I see that all the time on Facebook too, top-most 10% of a thread is actual comments, bottom-most 90% is "Friend McFriendface" name reffing. It's quite annoying.
About half my blog articles are technical in nature, and their purpose is primarily to serve as howto docs / "yay I built this thing" write-ups for future me, and for anyone else that's interested. I enjoy writing those articles a bit, although I usually enjoy the hacking that precipitated the writing more.
The other half are me deep-diving into random corners of history, geography, philosophy, economics, anthropology, politics, and the like. I REALLY enjoy writing those articles: both the actual writing of the words; and the hours upon hours spent lost in a smoky haze of Wikipedia, public datasets, Google Books, journal articles, other peoples' blogs, YouTube videos, and so on. AFAIK those articles get few hits, and that's fine with me, it's just my hobby.
From my anecdotal experience, of what my close friends share with me via DM these days, sadly it is indeed 95% video, and it is indeed 95% Instagram / TikTok / Facebook / Twitter / YouTube (in descending order). I continue to share with them 75% long-form articles, and 75% personal web sites / mainstream media web sites.
I have personally met people who, like me, really don't have cash to splash; but who, unlike me, and to my surprise, have literally told me "I pay for all the streaming services every month, whether I use them or not, there's no way I could be bothered to cancel/re-subscribe". So, from my limited anecdotal experience at least, no, it's not a vast overestimation, and in fact it's probably often not about how wealthy people are either - it's about how many people out there are willing to pay for the privilege of set and forget, rather than having to think about one more thing on a regular basis.
I make the streaming services work like this already. I have neither the time nor the interest in watching anything on streaming most months. I have all my subscriptions cancelled all the time. When I want to watch something badly enough on service x, I sign in, re-activate, get charged for one month, then immediately cancel the subscription. Then watch the thing. Then not get charged again until I want to watch something else badly enough in another 6 months' time.
If composable query builders have fallen out of fashion, that's news to me. I've used SQLAlchemy in Python fairly heavily over the years, it's gotta be one of the best out there, I plan to continue using it for many more years. And I've recently gotten my feet wet with Ecto in Elixir, I'm quite impressed with it too.
Considering that Yahoo doesn't really exist anymore, and that Yahoo Mail is just a relic of Yahoo's heyday that is somehow still hanging around, I assume nobody has bothered to actually maintain its handling of security protocols for about a decade.
Fair enough. My point in penning the article was simply: "sea level rise to date has been not much, sea level rise yet to occur is a lot". I don't disagree with your argument, that "a whole lot more sea level rise" may be the least of our problems. Although, sea level rise is interrelated with many of the other effects that you mentioned. It will result in a loss of land (duh). A lot of that lost land will be once-very-fertile land. So it will be a big part of the food insecurity picture. Increased salinity will be another bad one, and most of that extra salt will come from the risen-up sea getting into fresh water tables. And that in turn will be a big cause of fresh water scarcity. So, sea level rise is about much more than just "millions of houses (and some entire countries!) will be under water".
Author here. That was definitely not my intent! How can a sea level rise of potentially 1.6 metres (approx 5 feet) within the next 75 years, possibly put you at ease, or sound "very manageable"?!
Author here. No, unfortunately there aren't any such photos that I know of, and that's because even though sea level rise to date is verifiable via reliable measurements, in most of the world the sea level hasn't risen enough to be discernible to the human eye.
In the article, I linked to a number of fact checks of "then and now" photos, that claim to be evidence that sea level rise isn't real, and that have been determined to be false claims.
You should do, and I usually do, both "pure" unit tests (with all I/O - database calls, reading/writing local files, 3rd party API calls, etc - being mocked), and integration tests (with ideally all I/O really happening). More of the former, and less of the latter, in line with the "testing pyramid" approach.
There is value in testing "assuming that the database returns 3 rows with Foo IDs and Foo Descriptions, my code should serve a JSON response containing the Foo IDs and the Foo Descriptions concatenated together". And there is also value in testing "when my code executes SELECT id, description FROM foo LIMIT 3, the real database should return 3 rows with Foo IDs and Foo Descriptions". Granted, there's also a big advantage in that the former can run much faster, with zero environment setup / teardown complexity required. But my main point is, different test suites should test different things.
However, if you're unable or unwilling to write two different test suites, and if you're able to easily and reliably have a database available in dev / CI, then ok, I concede, just write integration tests.
Plus, perhaps the biggest complexity of all is that the currency rates are often not free, particularly if you want "live pricing" (updated every few seconds), and particularly if it's for commercial use. And, the fact that they may or may not be free, also illustrates well the fact that there are no definitive rates, there are only "rates according to X".
Good on you for open sourcing the code. Its destiny may yet be as a hidden gem that makes some peoples' lives better. In which case, not what I'd call a failure.
Feels like OP is basically implementing exceptions and exception handling at the application level. If this is what you want, then why not just switch to one of the many other languages that has exceptions built in at the language level?
Indeed. The central Sydney locality of Haymarket is that in name only. Same for Wheat Road and The Goods Line. Wholesale fresh produce has all been in Homebush / Flemington for years now, barely accessible to anyone without a semi-trailer and the willingness to purchase a truckload. Shipping also long gone from the central spots of Walsh Bay / Barangaroo / Darling Harbour, all now relegated to Container City aka Port Botany.
Relax, folks, entities have plenty of other options, there still won't be support for Do-Not-Shoot, Do-Not-Rape, Do-Not-Stone, fun for the whole family.
Despite the apparently glowing write-up from the time, hailing it as a success, no doubt there were constant cringeworthy "technical issues", of crackly lines, poor volume, calls dropping off, etc - I can well imagine the organisers saying: "we pulled it off once, for the lolz, but only just... Never again!"
Ummm... driving out of my metro area, in any direction, on a work day: zero traffic! Doing so at the start of a long weekend / during Xmas - New Year: horrendous traffic! Is that not the case for you?
Only some of these are really Postgres specific (use "text" / "timestamptz"; make psql more useful; copy to CSV). Most of them apply to relational databases in general (learn how to normalise!; yes, NULL is weird; learn how indexes work!; locks and long-running transactions will bite you; avoid storing and querying JSON blobs of doom). Not that that detracts from the usefulness of this article - pretty much all of them are important things to know when working with Postgres.
I typically try to take annual leave and to travel exactly on the opposite dates to what this tool recommends. That's because I care more about avoiding the significant extra expense, traffic, and crowds of travel over public holiday periods, than I do about getting a few extra "free days" of leave. No free lunch!
The military operates that way with 99% of their personnel, who are grunts, expected to only ever follow orders, to never think for themselves. They're expendable cannon fodder - think of them as pieces of hardware in a software company. But with the 1% at the very top (basically just generals), I'd say the bus factor comes into play, same as in any other organisation - certain individuals have all the knowledge of certain domains, and if enough of those individuals are taken out, the wheels grind to a halt. That's why targeted assassinations happen to the top brass.