AtNightWeCode

One thing is sure. Claude has become terrible. Criticize any code Opus 4.7 created and it starts a blame game. Also. It denies that a version 4.7 even exists. Will look into moving back to ChatGPT that I quit because the mandatory spyware bs they added which I believe they nuked.

Uber must be the biggest tech company that got lucky with timing. They are so incredible stupid and incompetent. How on earth do you end up with that cost for AI per user.

CF would pretty much need to monitor this live in that case which is impossible. The pirates sometimes even create new domains for specific games.

This is a risk with shared IP addresses. I sold CF to many customers and I would say the risk in general is minimal. At least outside Spain. But people should stop whining and use a better service if needed.

But, but, but Opus 4.7 says "I'm Claude, an AI assistant made by Anthropic. I'm not familiar with "OpenClaw". How could it be that it somehow knows about OpenClaw anyway. Clearly these tools does NOT work as stated.

That's a great question. Maybe other services have flaws too.

The uptime with Claude is poor. I use it for workflows more or less 24/7. It is often unreliable. Fine, it is cheap. What I really dislike is the uneven quality of the service. Clearly it does NOT work as stated. Opus 4.7 sometimes give ancient code back. Just the other day it even stated that the latest version of Opus was 4.5 and 4.x something for ChatGPT.

ISS is complex because of the huge amount parts to assemble it. When it comes to precise technical cutting edge tech ASML is easily on top.

Where I live there was a common scam to manipulate voice recordings from phone calls. I was very careful back then with phone calls when I ran my own business. Like 15 years ago. Kinda crazy that any service would use voice recognition today as stated.

Did not read it all but most likely AI. I read the beginning and that was just garbage in my opinion. I did run the whole piece through my shortening tool and the text came back larger than normal which is also a tell that it's not written by a two-legged.

You know from the start that a text is just garbage when it divide things into two made up nonsense groups.

Yeah, still some fun limits in Azure SQL. Like you can't take the databases offline or pause the service.

It is a bit silly, yes. But opus sometimes gives answers like, I am not allowed to do x and then brags about doing it anyway. So it is not just a hindsight thing

"Backups can only be restored into the same project + environment." Sounds like another great feature of Railway.

With the difference that best practices in Azure SQL have always been to store your own copies of backups and run the database in some HA/GEO-redundancy mode that blocks deletion.

No mention of Leqembi or Kinsula? Both FDA approved. And Simufilam that was mentioned was cancelled because of a failed phase III study years ago.

But fair, improved biomarker data does not mean the drug is making any real improvements for the patients especially with the side effects. But it is also well known.

You need to compare total cost. Token count is irrelevant.

"Polishing a turd" is missing. Making something slightly better when it should be removed. Like running Flash apps in 2026.

I think the baseline is that code can be trash and still comply with SOLID. Therefor people get frustrated over it. Getting PR:s rejected and so on.

I think it is better to have real requirements like: The code needs to be testable in a simple way.

It is misused if anything. YAGNI is about functionality. What to add or not. But it has become an excuse for being lazy. Same people that interpreted the line “Working software over comprehensive documentation” as no need for documentation.

Or the even worse category. People sharing email.

I never got email routing to work. I doubt this will work in the general case.

You probably need a hefty security reimplementation if you want to add IPv6 to Github.

The normal behavior is that firewalls and proxys respond to the ICMP requests instead of forwarding them though...

My experience is that AI agents are not that good with Go. Not sure why but I think it is down to the low code quality of many major open source projects in Go.

In this market it is probably smarter to fire a large block of people. Chances are good that you can rehire some where you went too aggressive. Sucks for the people that got laid off though.

And also not doing it on a Friday.

Very good. I agree with most of it. One thing I disagree with is "The senior engineers I respect most have learned to trade cleverness for clarity, every time.". This sounds like the anti-pattern "design for lowest competence" or similar. This is a big trap. A little bit of magic is often better than clarity. Junior devs should learn to follow the rules and how things work without the actual need for deeper understanding.

What a complete moron. This is why every senior dev hates these idiots in mid management. The kids know better? Yeah right. The new kids knows nothing. Recognizing how things work is not knowledge.

The counter argument I would say is that having all these integer ids comes with many problems. You can't make em public cause they leak info. They are not unique across environments. Meaning you have to spin up a lot of bs envs to just run it. But retros are for complaining about test envs, right?

Uuid4 are only 224bits is a bs argument. Such a made up problem.

But a fair point is that one should use a sequential uuid to avoid fragmentation. One that has a time part.