What was the most fun and least fun you had while learning Swift for this project?
I remember having trouble making a Swift UI for my C app because I forgot to disable sandboxing in Xcode project settings. Spent a frustrating two hours debugging
At some point in their career the problem they're trying to solve will overwhelm even their own abilities - it just hasn't happened yet, but when it does, they'll be in for a reckoning.
All of the tooling, and processes, documentation, and code modularization that it takes us mortals to build complex things - this guy likely does in his sleep without it, until there's a problem he'll face where he can't anymore. He hasn't learned the curse of the gifted. You might have met this guy in high school - didn't need to study for his tests, aced most of his classes, then he specialized in college and ran into trouble because he never bothered to build such rigor into what he set out to achieve, it came naturally - and the longer that problem occurs the harder it becomes to learn the kinds of things that us mere mortals require.
My advice, if you can't manage him in house, manage him out
Musk bought Twitter with the same results a redneck buys a jacuzzi at the county faire - it was an expensive impulse purchase and the moment after buying it all your left with is regret
This seems very much like the episode of Veep'Boxes of lies' where they try to hide their nefarious deeds alongside the real day to day inter-workings of the vice presidents office but inundating the public with data.
This is a common strategy in litigation as well - if someone complains that you have pricked them with a needle, dump haystacks on your opponent's doorstep while also insisting on your right to a speedy trial.
Code is legacy the moment it's checked in - not writing tests is the equivalent of expecting the game of telephone to go flawlessly always and forever for every corner and major case written... This type of optimism when looked up in the OED has one definition: nope
That is why I like Michael Feathers' definition of legacy code, which is (paraphrasing):
> Legacy code is code not under test
That said, I'm not against the existence of legacy code, but any bugs damn well should be written up as tests to catch regressions.
That way new development can be done without tests (full TDD is tedious and often way too coupled to implementation imo) but any bugs are captured in a way that can't be tests written against the implementation and guard against regression.
Trump is far from being a poet but he is a good orator and in the very least an effective communicator.
It should be noted that a common aspect to practically all US presidential candidates is that they all dumb down their communication style when running election campaigns, as that's a key aspect of all winning candidacies.
