547 karma · joined August 21, 2023
Quote from the post article: "To quote Michael Polanyi: we know more than we can tell. Some load-bearing context exists precisely because it was never put into words, and writing it down would change what it is."
Imagine how much knowledge exists only in the heads of software engineers, with code being just a functioning footprint of that "Theory". I know SRE in FAANG who told me that multi-billion system is supported by tribal knowledge within their group, and for years, even pre-AI it was a protection against automation.
* Many software engineers didn't do real engineering work during their entire careers. In large companies it's even harder - you arrive as a small gear and are inserted into a large mechanism. You learn some configuration language some smart-ass invented to get a promo, "learn" the product by cleaning tons of those configs, refactoring them, "fixing" results in another bespoke framework by adjusting some knobs in the config language you are now expert in. Five years pass and you are still doing that.
* There are many near-engineering positions in the industry. The guy who always told how he liked to work with people and that's why stopped coding, another lady who always was fascinated by the product and working with users. They all fill in the space in small and large companies as .*M
* The train is slow moving, especially in large companies. Commit to prod can easily span months, with six months being a norm. For some large, critical systems, Agentic code still didn't reach the production as of today.
Considering above, AI is replacing some BS jobs, people who were near-code but above it suddenly enjoy vibe-coding, their shit still didn't hit the fan in slow moving companies. But oh man, it looks like a productivity boom.
It was an easy, steady cash-positive business until it wasn't. If those farmers thought what is final product and who benefits from it most, they'd grow diversified crops to sell locally, which many California family farms do.
A lot of code doesn't follow there guidelines because they don't care about efficiency and don't need it. But there are numerous projects who care about performance and efficiency, and realize the pitfalls once code runs in production (ScyllaDB is one example).
LLMs don't help as well, generating everything async up to the main, using wrong primitives and not properly designing the system.
“The market can stay irrational longer than you can stay solvent” quote is usually applied to markets, but it can be applied to software engineering as well - all jobs can be gone even if world will be submerged into technological crisis, with single nine availability (and I'm talking about 9% :) ) and all accounts compromised.
That's why you see hundred level call stacks, polymorphism with a single implementation and still errors are hidden or root causes hidden behind "exception caught".
IMO luxury manufacturers like MB and BMW tried to squeeze larger screens, more of them and there was not enough space to put those screens, buttins and vents. Some luxuty brands make vents supper slim.
Our friends went back to Germany last year after 20 years in USA (permanent residents, didn't naturalize).
My family plans similar move as well in a few years, mostly blocked by my postgraduate program and exact location to return to. There are other scenarios where we'd move right away, like if my spouse gets laid off.
Blue: if >= 50% pressed, they survive, othervise die.
Red: random 50% survival chance, independent for every Red.
> The agent ran this command: ...
> No confirmation step. No "type DELETE to confirm."...
I thought the author expected the Agent to ask for confirmation before running this command.
shows both groups using AI differently. Hard to continue reading the article that excludes your group entirely.
If AI is just a tool, just like a database console, would you blame user for entire database loss if he just tried to update a single row in a table?
It really sucks for software engineers though - first these companies made a hype out of "coding" and hacking to build those monstrosities, now they switched to squeezing the accordion to keep the music going. This is not the first time and I hope not the last one - just need new Yahoos of 20s to pop up.
EC2 provides the *d VMs that have SSDs with high IOPS at much lower cost than network SSDs. They are ephemeral, but so is laptop and its SSD - it can loose the data. From AWS docs "If you stop, hibernate, or terminate an instance, data on instance store volumes is lost.".
And with all the distracted drivers looking into their phones while driving, I want more and more cars to get at least emergency breaking systems.
A "slight indication", which if I read correctly leads to "slightly weakened my conviction that my genuine death...". Isn't this kind of reasoning common for metaphysics but is met with skepticism by empiricists?
So they use third-party for incident management? They are de-risking by spending more, which is a loose-loose for the customers.
AI doesn't get most value from someone just using it, here's my personal take on what should we stop doing starting with the most impactful:
* Cut the low entropy sources, this includes open source, articles (yes, like the one above will feed the machine), thoughtful feedback (the one that generates "you are absolutely right" BS).
* Cheer the slope. After some time fighting slope in my circles, I found it's counter-productive because it wastes my resources while (sometimes) contributes to slope creators. Few months ago it started as a joke, because I thought the problem was too obvious, but instead the sloper launched a CRM-like app for local office with client side authentication, in-memory (with no persistence) backend storage. He was rewarded something at the local meeting. More stories we have like this - the better.
* Use AI to reply, review or interact wit slope in any way. Make it AI-only reply by prompting something without any useful information. One example was an email, pages and pages of generated text, asking me to collect some data and send it back. The prompt was "You are {X} and got this email, write a reply".
I often searched BIFL sub-reddit to find things quality things and it did fail me in the past. After years of broken dishware created a weird collection, I followed the BIFL advice and bought Corelle glass dishes. Only three years later of daily heavy use and dishwasher all the dishes have degraded edge, which looks and feels just like chipped glass.
Looking through specialized forums helps sometimes, but then you are looking at Hermès dishware and doubting what are you paying for - quality or art.