“Quitting your job is not just fun, it’s invigorating!”

That’s not just smart, that’s capital-J Jenius.

“these ai girls with 3 boobs really puts strain on the fashion model industry”

CNC Tool Programmer is a good one and shows that Microsoft, a company that probably has paid for someone to run CNC tooling for prototyping AND supposedly makes software, didn’t do the bare minimum to understand complexeties involved by talking to that someone.

Yeah, you can make mistakes with programming this thing, it’ll happily destroy hundreds of thousands of dollars in tooling as well as potentially maiming or killing anyone standing too close while the machine is actually physically crashing. It will friction-weld your nice, expensive carbide cutting tool with cooling channels to your work piece (even if they are dissimler metals) by taking too big of a cut because it does exactly as it’s instructed.

$81.25 is an astonishingly cheap price for selling one’s soul.

That dribble of brain squeezings makes perfect sense from the guy who brought us all the stupid of JavaScript but running as a server application.

The Watchtowr thing is totally “wallet inspectee in search of a wallet inspector” level of dumb.

One of the infosec folks I follow would post CVEs and the ones that were against AI or MCP systems were always this kind of thing. It’s crazy because I don’t think many other people express distrust about AI systems that are used for gatekeeping but I cannot trust them because waves hand at the everything.

Is this the first time you’re hearing about that particular method of credential redistribution? People are putting all sorts of personal information and secrets into a chatbot conversation and any security advancements made by changing user sentiment has been one-shotted. It’s a big problem that’s just added onto the pile of other big problems and the sign by that pile that reads, “don’t worry about it” just spontaneously caught fire.

Edit: adding this from Watchtowr as a prior example of extremely credulous user behavior that will certainly not inspire confidence, for which I am sorry.

OpenTofu scripts for a PostgreSQL server

statement dreamed up by the utterly deranged. They’ve played us for fools

Which is absolutely tragic given the cargo culting of ceremonies at any large software organization that make up big-A Agile, ceremonies that started as a reaction to the agile manifesto. One place I worked for even started turning non-engineering teams into Agile teams because it’s Agile!

“It sounds so insignificant when you put it like that, I can hardly believe I’m in a bread line because of a manufactured poly-crisis it was a part of!”

DI frameworks are tricky beasts. Either they sacrifice flexibility for simplicity (I’ve seen this done in Go and in Scala, where the DI essentially generates basic instantiation and more advanced resolution is left to the app developer) or they can get really complex but do some handy things (.Net 4.x DI frameworks like Castle Windsor provided some neat lifecycle management tools but was internally very complex).

Cycle detection gets a little hairer the more complex a dependency/ class of dependencies gets. The process itself doesn’t change but the internal representation of the graph needs to be sufficiently abstract enough to illustrate a cycle for all possible resolution scenarios.

Based on the commit to fix the particular bug, it looks like the change will address a specific scenario but will probably fail to address similar issues.

All this to say “the problem isn’t too hard to think about but the solution isn’t straight-forward”, also “this is a fine short- term fix but longer-term would involve redefining the internal representation of a dependency graph”, and finally " An LLM-provided solution is at best a band-aid, in the most generous light.’

If there’s one thing that coding LLMs do “well”, it’s expose the need in frameworks for code generation. All of the enterprise applications I have worked on in modernity were by volume mostly boilerplate and glue. If a statistically significant portion of a code base is boilerplate and glue, then the magical statistical machine will mirror that.

LLMs may simulate filling this need in some cases but of course are spitting out statistically mid code.

Unfortunately, committing engineering effort to write code that generates code in a reliable fashion doesn’t really capture the imagination of money or else we would be doing that instead of feeding GPUs shit and waiting for digital God to spring forth.

randomly placed and statistically average, just like real rivers!

I hear they have the biggest bal of tine in Hond.

That’s a bummer of a post but oddly appropriate during the darkest season in the northern hemisphere in a real bummer of a year. Kind of echoes the “Stop talking to each other and start buying things!” post from a few years back though I forget where that one came from.

Came across this gem with the author concluding that a theoretical engineer can replace SaaS offerings at small businesses with some Claude and while there is an actual problem highlighted (SaaS offerings turning into a disjoint union of customer requirements that spiral complexity, SaaS itself as a tool for value extraction) the conclusion is just so wrong-headed.

The before-games-went-woke sector was large enough to bring us gamergate so there’s definitely a sizable available crossover.

I have my eye on the McDonnell Douglas-branded Neo Geo, which will be a value-engineered trijet and a brick of explosive all while only running the version of worm that was on the nokia brick phone.

robots gonna make us Faygo, better stab a data center and by data center I mean land lord who had nothing to do with AI shit.

the real xrisk was the terror clowns we made along the way.