I am exactly the potential user of this, as I am currently setting up a small collocated cluster and investigating software for management. But this doesn’t tell me anything that would actually matter in that decision.
What's the problem of the solution proposed ? Don't read/write code anymore. Have strong harness. That's how my team of ~30 has been operating for the most part.
The problem we are trying to solve was never to write code, was to solve business problems
"I don't understand the code anymore. It works." That's fine... today.
"I will never need to understand the code again" is a much different statement.
If you don't understand the code, and the code wasn't written by any human, when you're eventually painted into a corner, how hard is it going to be to get out? Will it be easier or harder than maintaining an understanding through however long it takes to get to that point?
You may be betting your company on the answer. How sure are you?
How is this different than working at a company with hundreds of developers, on a massive codebase? Do you ever really understand the entirety of that?
No. But somebody understood the high-level architecture, and somebody understood each piece in detail. And if you needed to work on piece X.Y.Z, you could find somebody who could tell you how X fit into the big picture, and somebody else who could tell you how Y fit in X, and somebody else who could tell you how Z fit into Y, and maybe somebody else who could tell you about the details of Z.
Why are you so aggressive ? What I am saying is how many folks are working nowadays and DHH gives an example of this in his linux distro and in his interview talking about his products.
Maybe try it out with an open mind ?
Do you expect me to break my work contract to convince a stranger on the internet that they're wrong ? lol
I know everything about Omarchy and latest vibe coded version just sucks like many’s have underlined already. I’m open minded to the point that I’d pay to look at your work. It’s always who can’t break the contract that we should trust, no one working in the open, and in the meanwhile software sucks more and more
Why would I work on the open tho ? The reason you always get that answer is because it's the norm. I am paid to develop software for a business like the majority of people I suppose.
Outside of my work I spend time with my family as I stare at screens enough during the day.
Maybe if you asked 20 years ago I'd be able to share some of my passion projects, unforutnately AI didn't exist back then
You are not open minded, you sound like you dont even have a mind of your own. You want to name and shame, just like the rest of your tribe, and because you can't you are just throwing toys out of the pram. Traditionally, I would tell you to grow up, but in your case that would mean to be reborn a few hundred times.
It's what keeps me away from the fediverse...
Outside it's a bit better so I lean bubble. But the training material that shapes the part of the network that activates when claude works on something technical might have negativity over-represented.
That’s just a gigantic bs you wouldn’t be able to stir an ai without code writing knowledge this approach in the long term we will make all of you shilling people go back to hand code crucial parts of the business logic
Sure ! I have been doing this for 2 decades now and started my career in VHDL / Hardware before going to embedded systems and then cloud. I am pretty sure I can understand hand code pretty well. I just don't need to write it. Why would it.
Configuring postgres to automatically failover instead of doing it manually. The automated system caused more downtime in a few months than manually doing it did for years before. All in the name of more automations and less downtime
For resolution of a problem you can’t prevent categorically, you have to spend a good bit of time pretending to be the computer before you can trust the computer to do it. A run book is a draft of a requirements doc for a program to do the same thing. And you can’t afford to test that program in production without loads of simulations first. And that’s running the process manually and checking aggressively for any signs of problems.
Some coworkers snaked the autoscaling work out from under me, and then ignored the advice I offered on low water marks and weeks of testing and rehearsals. All I can figure about their irrational exhuberence is something to do with claiming something for annual reviews? All I do know is we didn’t make it 40 hours from when they flipped it on until we had our worst outage in two years. Classic FAFO.
They were hoping to eventually get to a low water mark of just over 30% of our static cluster size, and they decided to use that for their initial go instead of my estimate of 40% being the low, and a recommendation that they start with 50-60% for the initial weeks and then ramp it down. When I refused to let it go in the status meeting, the team decided we should vote on it. Two guesses how that went.
A bug in the deployment logic the Ops team had for doing things like upgrading VMs caused the next update during daylight hours to spin up the new instances at the minimum cluster size, instead of the current cluster size. It was done outside peek hours but that still had us cut over with just under half of the hardware we needed at that moment. Because we were in such a fucking hurry to be something like third in line to use the new autoscaling support, nobody else had run into this problem yet (or system did a pretty good job of buffering everyone else).
A couple weeks later they’d looked at the stats and decided that we were spending less than a half hour a day running at the low water mark, and the additional shutdowns were causing churn that made it harder for us to detect problems like memory leaks. Surprise, surprise, they increased the min cluster size to exactly what I’d told them two weeks before.
Since “listen to me” isn’t a lesson that transfers to other teams, I will instead say, don’t transfer initiatives to a new team when there is less than 10% of the project left. The lack of friction you encounter may result in a lack of respect for the danger, and attention to potential problems. And if you must transfer, if your ideas about rollout timeline end up being less conservative than theirs, be patient and do it the slow way. They probably have encountered problems you haven’t seen yet.
Because AI cannot be trusted as a reliable source of information. Information is more trustworthy when it comes from from primary sources on the open web.
Why not ?
Can google be trusted ? Or facebook ?
How do people have been accessing the internet for the last decade you reckon and how's this any different ?
Google (as it originally) existed wasn't a source of information, it was an *index* of it. You were trusting google as a source for {search_query}, you were trusting the links it gave as a source (based on your own evaluation). LLMs are fundamentally different, because you are trusting the software to actually generate the information in a truthful way.
If you use google (sans AI), you're putting some trust in their page ranking algorithm. If you use it with AI, you're trusting the same algorithm (since that's how the model gets it's sources), but then you're trusting the model to evaluate the sources for credibility and extract the information you actually want.
Do you think the LLM reads every page on the internet before generating your answer? Of course not. What happens is that it use some sort of ranking algorithm to pick the pages that are most likely to answer your query and reads *them* (at best. At worst it just makes something up). You aren't avoiding the problems with ranking algorithms by asking an LLM, you're taking all of those problems, adding more problems on top, and pretending that this is somehow better.
No. Neither can be trusted as far as you can throw them. They're both incredibly invasive data brokers. Their customer facing products are just vehicles to show ads and Hoover up more PII and behavioral data on everyone.
I routinely run into Claude Opus and Fable making basic mistakes like misunderstanding a simple negation, which would be on top of whatever reliability issues there are with a source. I think that means it is functionally very different.
Of course yes, and it's even easier in some cases. Since there's a language that defines the functionality (e.g: formal methods) that the agent can use/veriy against
reply