I never understood the "low code" microbubble that was being inflated.
We went through that era already. We called them RAD tools, and they targeted the same sort of strange, mythical end user profile. Someone so technically capable and apt that they could navigate a dizzying domain of deeply buried checkboxes, property fields, and sprawling relationships & side-effects, but who was also simultaneously unable to understand source code or program structure.
When using them you would quickly hit a point where making changes to relatively simple things would take mounting an archeological dig of GUI controls that would have otherwise been a few simple find & replace operations on code in a regular environment.
Sure, though I'd ask more open ended questions about a problem to see where they go with it.
Maybe they land on using something like a debugger or wireshark or strace or whatever makes sense to dig into whatever horrible voodoo is plaguing them. The important thing is that they are creative and experienced at questioning or confirming their priors and eliminating thousands of paper cuts and yak barber shops for themselves, their team, and their organization, so that collectively everyone is enabled to operate at a high-level instead of everyone constantly bushwhacking their way toward eventual failure.
The "nano" questions are silly and tell you nothing useful about the candidate other than I guess their level of candor in being subordinate to obsequious lines of questioning.
However, the rest of the questions are just as pointless too.
As a hiring manager and product owner, the level of familiarity that an engineer has with using debugging and diagnosis tools (e.g. as simple as how to attach and effeciently use a debugger) is 100x more valuable to the predictable delivery and quality of the things they're building than Programming 101 trivia.
Writing code is quite possibly the easiest, least fraught time-sucking milestone-missing part of software development. The morass of the entire rest of the SDLC is where ambitions and dreams go to die. Version control expertise, build system esoteria, correct configuration & setup of dependencies, understanding how to test, being able to do more than printf'ing your way out of a Russian nesting doll inspired paper bag. That sort of thing.
They never had any meaning to begin with. Outside of ostensibly knowing how to program, the title carried with it no firmly held, measured, or maintained any baseline expertise of any kind. It's always been a hodgepodge of ad hoc criteria on a job by job and hype cycle by hype cycle basis.
Sam Altman is not a hapless victim at the mercy of the isolating effects of his financial success.
He was an opportunistic, amoral sociopath before he was rich, and the system he reaps advantage from strongly selects for hucksters of that particular ilk more than anything else.
He's just another Kalanick, Neumann, Holmes or Bankman-Fried.
Once you're running a fleet of autonomous vehicles, whatever century that finally becomes a reality, then it makes sense to optimize out of the operation a few people who make at or near minimum wage.
ZIRP happened as a long-term back-channel bailout to all the banks & funds holding the downside of the housing & derivatives market collapse. It allowed the financial sector to reinflate several asset classes that should have seen steeeeeeep declines & corrections, so that they didn't have to face insolvency.
Then on the back of that there were all these knock-on effects to cheap money, or more specifically net-negative yield on things that historically were supposed to be slow, safe value stores. One of which was epic amounts of money flooding into VC and VC making the attribution error of their access to money being correlated to their access to ability & insight, but in the prevailing environment there was no correcting feedback function for that either.
So, cheap-money became dumb-money, but sociologically we attribute lots-of-money to intelligence & capability, and from that a decade of Hundreds of Billions of Dollars of trite visionless total crap was born.
I spent all of ZIRP while it was happening being bothered by this. It was insanity inducing to watch huge valuations and associated piles of money chasing the most banal and/or impossibly ridiculous ventures for YEARS.
I also used to tell many, many VCs to their face that the only reason they existed at all wasn't because they had any worthwhile insights into investing or innovation, but because tons of massive upstream capital & funds had a choice between definitely essentially losing money investing in bonds or probably losing money funneling it through their brokerage... er... venture fund. The world's least qualified kingmakers minting new American royalty, and we'll all be paying the price for it for decades.
To add insult to injury, now huge numbers of those alsoran VCs are pivoting into "deep tech" investing, and brining their inane-SaaS myopia and completely misaligned expectations along with them.
FWIW… look at the portfolio pages of lots of VCs. They’re absolutely filthy with boring companies with boring products that obviously have absolutely no prayer whatsoever of being a “venture scale” business. Despite that fact, they managed to get multiple investors to put in Millions in capital. How?
They bullshitted the right sounding bullshit to a specific audience who absolutely laps up particular flavors of bullshit. Sometimes the flavor changes (e.g. DevOps, enterprise SaaS, crypto, AI), but they’re always hungry.
You of course don’t have to raise money if you don’t want to, but I’m sure you could do it too for damn near any idea you come up with as long as you also figure out how to relieve yourself of any sense of self-respect and prostrate yourself in front of the altar of VC buzzworthiness and tomes of fortune cookie wisdom.
Yes. It has all the telltale signs of a FOMO-hype bubble across multiple asset classes that's driven by multiple organizations cynically exploiting a combination of Gell-Mann Amnesia effect and human propensity to anthropomorphize things.
We went through that era already. We called them RAD tools, and they targeted the same sort of strange, mythical end user profile. Someone so technically capable and apt that they could navigate a dizzying domain of deeply buried checkboxes, property fields, and sprawling relationships & side-effects, but who was also simultaneously unable to understand source code or program structure.
When using them you would quickly hit a point where making changes to relatively simple things would take mounting an archeological dig of GUI controls that would have otherwise been a few simple find & replace operations on code in a regular environment.