
Also seen a lot of Storks. Must be a Lucky Day.

Database-guy, Typo-maker, Voyager. phd in I told you so, knighthood in.. also, the sky is blue... linktr.ee/pdevisser

Also seen a lot of Storks. Must be a Lucky Day.

Hmm. I m not buying it. Not yet. But still keeping this tweet for reference, just in case.
I haven’t lived here in awhile, but I see no other way to answer the hundreds of texts/DMs asking me if the world is, indeed, ending. In the span of six days, we’ve experienced; 11/12 — Microsoft outage 11/13 — Nationwide FAA ground stop 11/16 — Major US banking disruptions 11/17 — NSA’s classified internal network goes down We need far more analysis of why so much is breaking at once. I don’t want to get out over my skis here, and what I am hearing does not contradict the messaging that most of this is the result of screwy updates. But stepping back, the dots are starting to form a collective picture. We are seeing: • An explosion in severe and critical vulnerabilities, with AI accelerating discovery to 3X the number of vulnerabilities discovered in the same period last year. This is collectively being referred to as “vulnageddon” or “the vulnpocalypse.” • Mean time to exploit those vulnerabilities has collapsed to NEGATIVE SEVEN DAYS. AI allows attackers to find/exploit vulns far faster than software makers have time to fix them. • Powerful AI-enabled offensive tools like ARTEX have been thrown into the hands of every third tier nation state, cybercriminal and digital arsonist, which logically creates havoc. • This creates enormous pressure to compress patching windows and accelerate software updates, increasing the likelihood these fixes break things in unexpected, cascading ways. • Pressure to just “AI everything” means we are rolling out automated AI tooling on top of brittle infrastructure that can’t support it. My generation grew up in an extraordinary period of technological stability. We worked our way up the software stack, abstracting away layer after layer, until we lost a fundamental understanding of how the underlying systems actually work. We were told to “move fast and break things.” VCS told us to celebrate the idea that “software would eat the world.” Now we’re telling ourselves we can simply “roll out AI” across everything, as though nothing underneath will buckle. We never stopped to ask: SHOULD WE? Should we be digitizing every last nook and cranny of our companies, infrastructure, healthcare, homes, cars, bodies, lives? Especially when the complexity, interdependence, and fragility we were introducing overwhelmed our ability to understand/secure/maintain the systems we built? Nobody every asked: What if, in the name of progress, we were creating the ripest attack surface in human history? We are now entirely dependent on software systems that almost nobody understands end to end, that increasingly few people can repair, and that attackers can now probe at machine speed. We are hearing that incident response firms, the 911 for breach victims, are backlogged six months. Even those paid on retainer lack the bandwidth to triage every incident. The cavalry is disappearing. We are entering a period of unprecedented technological instability. “Software Beirut” is an incredibly apt analogy. We are in for a period of cascading failures, whether triggered by attackers, bad updates, or our own accumulated complexity. This, I’m sorry to say, is just the opening chapter.

/* todo: more...*/ That could be me. (I m still mostly human)
Human-written code has a signature, and it's a stale README nobody planned to fix.

Had to smile... (Will try not to repeat certain jokes though... sensitive matters there)
Sorry this is fucking hillarious

Yep. Good Advice there.
It would be cool if there was a coding language you could run *really* close to the database #iykyk

The debate on use of AI runs... Here are some things to take into consideration.
Key ideas I got from DevTalksRomania: - While AI can boost productivity on some specific tasks, great teamwork improves productivity on even more activities. This is like setting up an orchestra, where everyone needs to be tuned and work in synergy. - Writing tests manually can help you add determinism to your project. Generating both the app code and the test with AI may lead to AI writing tests on hallucinations. This is similar to OSS, where we'd write tests for a bug before implementing the fix. - When LLMs regress towards the mean, and everyone uses LLMs, the output would be of average quality, but clients don't want to pay for average, so expertise will be very valuable to differentiate from the rest. - When prototyping with a new tech, do it on an app that's unrelated to your business so that management doesn't promote the prototype to production-ready. - You can use the Maven daemon, parallel tests, and caching to speed up your build significantly. - Use linters and verifiers (e.g., ArchUnit) to speed up reviews, especially now that AI can easily generate lots of changes - Set up a rule in your team so that a PR cannot exceed a threshold of changes (e.g., at most 400 lines of changes), so that it's easier to review and approve one PR at a time.

I know a few of those companies...
sudox @kmcnam1 Sep 9

You know who you are...
Alfin @AlfinCodes Sep 7 0:07

Interesting
China published the most uncomfortable paper on vibe coding. ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds. The findings are brutal. The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning. They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself. Two major predictors emerged. Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds. But that wasn't even the main takeaway. Computer science achievement was a massive, dominant predictor of success. Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed. In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone. Why? Because vibe coding isn't about writing code. It’s about debugging logic. When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works. They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe. You can prompt your way past syntax. You cannot prompt your way past a fundamental lack of engineering intuition. The hype told us that learning to code is dead because language is all you need. The data just proved the opposite. To truly master the vibe, you still need to understand how the machine thinks.

This will turn out Prediction (sans blague)
PATHER@patchagil Aug 25

Difference between Developer & Tester

Should I broadcast this....? (Want to keep for later reference)
Nicknames for lazy coworkers: Cordless - only works for 2 hrs E.T. - always wants to go home KitKat - always taking a break Muffler - always exhausted Seaweed - just floats around all day Sensor light - only works if someone walks by Wheelbarrow - only works when pushed —expect a visit from HR

Many of the answers make sense. And has anyone seen Murphy around?
Can I ask a dumb question: If a UUID is "practically impossible" to duplicate, why do we still check for duplicates?

Pro tip: If the LLM generates code that you cannot understand, it means you need to upskill. Use AI to explain what was generated and provide more resources to help you keep up with the model. Being able to review the code that AI generates will become a mandatory requirement for software engineers.

BOFH level.
The HR department rolled out a massive corporate wellness initiative last month. They gave every department head a $15K budget to improve team mental health and workplace ergonomics. The sales director bought standing desks and ergonomic chairs for his entire floor. I took my $15K and purchased a commercial-grade sensory deprivation tank. I had it installed in the sub-basement next to the primary fiber optic line. When the head of HR asked how a saltwater isolation pod benefited the IT team, I had my answer ready. I told her that managing high-level network topology requires immense cognitive bandwidth. I explained that to visualize complex firewall configurations, my engineers need to achieve a state of 0 sensory input. I called it an "algorithmic meditation chamber." She wrote down the phrase and thanked me for prioritizing mental neuro-plasticity. We don't have any IT engineers. I'm the only person in the department, and my workload is entirely automated by a shell script I wrote during the Obama administration. I spend 3 hours every afternoon floating in body-temperature saltwater in absolute darkness. It's the most peaceful part of my workday. Nobody ever comes down to the sub-basement because I put a sign on the door warning of severe electromagnetic radiation. Yesterday, the CEO sent me an urgent email about a massive spike in dropped packets across our VPN. I was entirely submerged in Epsom salt at the time. I replied 2 hours later saying I had successfully rerouted the traffic while in a deep state of tactical visualization. He replied saying I was the absolute backbone of the company. Corporate wellness isn't about physical health. It's about isolating yourself from the people who sign your paychecks.

Relevant !
A BBC interviewer asked a Nobel physicist the simplest question in the world: why do two magnets push each other apart. He refused to answer it. What he did instead is the best seven minutes on thinking ever filmed. The man is Richard Feynman, at home in 1983, no blackboard, no notes, sitting in an armchair. He does not dodge because he cannot answer. He dodges because he wants you to see what the question is actually asking. So he takes an ordinary sentence, that a woman slipped on the ice and broke her hip, and starts asking why, and every answer opens another why, until the ground gives way. Then he turns it around on the interviewer with a question about ice that sounds trivial and is not. The point he arrives at is the uncomfortable one. Every explanation is only a translation into something you already accept without explanation. Magnets have no such translation. There is nothing more familiar than magnetism to reduce magnetism to, which is why every answer you were given at school was a picture, not a reason. It matters more now than it did in 1983. Any tool will hand you a fluent answer in a second. Knowing which questions actually have a bottom is the part that is still yours. One question. Seven minutes. It is in the video.