Books have limited print runs. Many books in libraries are only borrowed and perhaps read a few times. Niche titles more so. Books go out of print and are hard to search for arbitrary text.
740 karma · joined January 25, 2009
Where do you get your information, Fox News?
It was because of grievous breaches of campaign financing. The kind of thing that brings the integrity of their electoral system at serious risk.
Incredibly common.
The first is subtle bug analysis which needs almost monomaniacal focus and creativity to solve - and is quite mysterious to less technical folk.
The second is, of course, major refactorings, which result in no discernable difference in functionality of any of the touched components, but which unlock future stability and velocity opportunities.
I’d argue that this is also true for a class of senior software engineers in real codebases.
As a senior tech leader, it was often extremely hard to convince product and financial leaders that this time was well spent!
0. https://www.ifw-kiel.de/publications/news/ukraine-support-af...
Election interference does occur, and to protect democracy, courts must act where there is clear evidence.
Or are you referring to Hungary in your second paragraph?
Seriously, -ize endings in the Cambridge spelling tradition relies on you knowing the etymology of the word, and if it’s from the Ancient Greek, that’s the one you use. Otherwise -ise for French or Latin words.
It sounds a bit like the Erlang BEAM VM to be honest, the BEAM processes tend to be small and there are a lot of them in real-world applications, and message passing is a first class construct (along with some others like ETS which are “cheats” that offer other tradeoffs for specific cases)
It’s like the MBAs looked at the Soviet Union’s fake markets, and thought to themselves “we want some of that, please”.
Are there other virtualisation-driven designs for hardware devices out there rather than the qemu stuff?
To “stand over” is a verb meaning roughly to “threaten, with menace”.
But it doesn’t necessarily mean that that’s the party or parties that have undertaken the attacks.
Edit: spelling, never ran into the NL word for clay in writing as an adult language learner not into geophysics, civil engineering or pottery
I’ve been part of turnarounds where senior execs have said that the three hundred people here will lose their job if nothing changes. I still talk to some of those teams that transformed themselves and others, and made it.
As I’ve learned it, I found it very charming and often surprisingly sweet - as an example idiomatic terms for urination and defecation are very funny: plassen (making a large pond) and klaaivormen (forming clay) - add to that a rather easy to rhyme language with a tendency towards charming and heartfelt emotional range, and the end result is quite nice.
Add lots of domestic and Caribbean regional variation in the home countries, close sister languages: Vlaams (certainly in its higher form a very different register of the language than the Hollands standard form), Afrikaans and West-Frisk, Papiamento etc and you’ve got a very cosy (gezellig!) and dynamic inter-language community!
The aggressive simplification of standard Dutch initially offended my tastes, but later I’ve found that particular discipline improved my English by accident and I’m now a fan of the sparse elegance and surprising nuance of that style …
It’s the sophisticated version of “Don’t attempt any change” brigade’s position.
My observations from a lifetime in very large, cumbersome orgs is that improvement only comes from change and in highly dysfunctional, low-performance and low-ambition environments almost any reasonable change, supported by a really tiny number of engaged participants with a clue, leads to outsized positive step changes.
Even better, doing this as a sustained, tide-coming-in approach over several years can create more engaged people with a clue and slow transition to high-ambition, moderate-to-good performance cultures.
It’s worth the effort if you’re not doing it alone, and know that all the attempts pay off as part of a cumulative push. It changes lives both in the service delivery org, as well as those they’re supposed to support.
The problem with resume-driven technology choices are a kind of tech debt that typically costs a lot of cash to operate and perhaps worse, delivers terrible opportunity costs, both which really do sink businesses.
Premature scaling doesn’t. The challenge is not leaving it too late. Even doing that though only has led to a very few high-profile business failures.
A bank exists not as an isolated entitity, but as a node in a local, regional and global network of transactions.
Your phone as a “classic banking infrastructure” (nonsense phrase) can’t do credit card acquiring or realtime transactions because it’s not connected to the payment rails, transaction switches and so on (like SWIFT but all of the other less global ones run by central banks and private entities).
In developed societies, instant settlement for bank-bank transfers is the norm, and cash flow is dependent on that.
Russia and Iran pay about 2-5% for above-board (non-sanctioned) cross border transactions due to their extra costs of not being in SWIFT and USD sanctions, and between 20-50% where physical middle-people are needed to move pallets of USD.
> The final piece of advice for any practitioner of corporate stupidity is to keep moving. It is vital to avoid being landed with your own mistakes.
I've obviously been working with masters of this game.
I used to think that the 737MAX line would be the safest of Boeing's products because of all the extra attention after the terrible crashes, but from the sounds of it, the rot runs too deep in Boeing.
Not dealing with loads of technology choices in the early days is a boon.
Once we hit more than $100m in rev it made sense to allow a bit more optimisation for purpose - but only when we had cash flow to pay for it. Otherwise all these fancy-shmancy choices are just dressed-up tech debt.
Booked off late December 1999 and early January 2000 two years in advance, and had it written into contracts. They tried to cancel my leave in December, lol. Most colleagues NYE plans were disrupted and while they were paid overtime, it wasn’t worth it. I had a party with 100 close friends on a family farm and listened on a shortwave radio to hear that New Zealsnd hadn’t been disrupted. The jelly wrestling then began.
Seriously, the teams working on Y2K defects fixed lots of stuff in embedded systems, finance and HR tools, control systems and the like.
The Y2K team’s goal was to correct 99.999% of defects, and they estimated having up to 3 life threatening incidents after the date change, and lots more less critical issues.
In the wash up, I heard of only one potentially life threatening incident, when a pump control system errored out and filled a major harbour with oil.
Three years later, during a business crisis, I discovered a critical backup system for business data had not run its schedule on 1 January 2000 or subsequently. Cost at least a couple billion dollars of losses to investors, due to the ensuing crisis in reporting, lol.
Overengineering is a plague amongst SWEs, and almost as dangerous as failing to sell the product in the market.