FUS - Fear Uncertainty Doubt

yeah, classic conflict of interest.

However nobody is agreeing with that, that's how it's done, and move faster faster, because of goldrush! faster!@@@!

I'm using it, it's great and interoperable. Win - Mac, Mac - android, whatever is your wish. Any combination. However on Mac it prevents the laptop from sleep for some reason

That's quite impressive approach from the companies' perspective. Let's first use claude code and then we'll think who the code belongs to.

I think that the gold rush approach happening right now around me (my company EMs forcing me to work with claude as fast as possible) show really short-sight of all the management people.

First - I lose my understanding of the code base by relying too much on claude code.

Second - we drop all the good coding practices (like XP, code review etc.) because claude is reviewing claude's code.

Third - we just take a big smelly dump on the teamwork - it's easier and cheaper to let one developer drive the whole change from backend to frontend, despite there are (or were) two different teams - one for FE, one for BE.

Fourth - code commenting was passe, as the code is documentation itself... Unless... there is a problem with the context (which is). So when the people were writing the code, they would not understand the over-engineered code because of their fault. But now we make a step back for our beloved claude because it has small context... It's unfair treatment.

I could go on and on. And all those cultural changes are because of money. So I dub this "goldrush", open my popcorn and see what happens next.

> Third - we just take a big smelly dump on the teamwork - it's easier and cheaper to let one developer drive the whole change from backend to frontend, despite there are (or were) two different teams - one for FE, one for BE.

Agree with your other points, but IMO this one has always been better. You often need to design the backend and frontend to work with each other, and that requires a lot more coordination when it's separate teams.

One of the few things I do kind of like about LLM-assisted coding is that it's helping to bring back "lone wolf" programming. We currently default to using massive teams to build massive software because of all the work involved, but teams have a huge communication/documentation cost, and a lot can leak and be lost the more communication has to happen to get things done. Code assistants cut down on the "all the work involved" part, and I think will help to bring one-man shops back into fashion.

On the other hand, separating FE and BE between two teams, necessitating proper interfaces, can often be considered a feature.

I rarely see #3 yield better solutions, it's usually better to collaborate as a team on requirements and gotchas, but let one person own implementation.

But both backend and front-end? Do everyone have to be full stack?

Also, it's supremely easy do the wrong abstractions long term and compromise premature internal designs that will start to starve of human mental modeling, hence explaining with accountability how things work and what the plans are when an incident happens. Also, if the wrong generalizations are introduced, coded correctly and reviewed and approved by AIs, then who's even driving really?

people quickly have forgotten: when copilot was announced, there were warnings not to use it for company code because of the license attribution problem. so what's changed? that anthropic is willing to defend and indemnify?

I opened my popcorn for the unholy trinity of HN x law x AI, your comment was one of my faves, love the purple prose. :)

The fourth point about code commenting is the one that connects directly to the ownership question. When developers write comments to explain intent, those comments are evidence of human creative direction. When Claude writes the code and the comments, and the developer merges without adding their own explanation of the architectural decisions, the record of human authorship disappears along with the institutional knowledge. The documentation problem and the copyright problem are the same problem.

This Is exactly how civilizations die out. When AI was incoming I wrote similar predictions. This WILL happen, sooner or later. People will stop understanding what programming is. What is hard drive. Why storing files in cloud is not the same as having them on your HDD. And similar things

what other civilizations died out this way?

The bronze age collapse? The end of Rome?

I thought the cause of the bronze age collapse wasn't known (it wasn't a single civilization either), and the end of Rome, whichever "end" you ascribe to isn't caused by failure to manage or adapt to new technology. they weren't out-teched by anyone, or forgot how to do some technical work.

look at the roman roads and compare them to the contemporary ones. Those ancient roads are superior in some aspects (unbreaking, not filling with water etc), and still people try to find out how were they made.

Having that said, I agree with you: the forgetting of the technology was not a direct reason of the fall, it was a feature though...

I'm from Poland, and I have comparison with my colleagues from east. They can fix things we've already forgot how to fix in Poland. My friend fixed a broken Sony TV with a microscope and a soldering gun. I'd pay just 1000$ for the new TV, as he got advised in the official repair store, but since he was Russian, he fixed it by himself.

> the moment they officially acknowledge Linux support, then it becomes a support surface

untrue. There are no obligations from other hardware vendors, yet you can sometimes get good drivers from them, or at least specs. I think Apple indeed want their hardware to fade out to enforce buying another. Imagine that 20% of your returning customers no longer return after 3-5 years of planned obsolence

The mentioned light sensor started malfunctioning on my work's m3 after upgrading to tahoe. After a sleep it sometimes dimms the screen at max. Thankfully I have the monitor control app which brings it back for me. Such unneeded and faulty mechanism.

What cat cable works with it?

the same for me, however I can imagine that creating a good sleep analysing software based on the hypothethical HRM and accelerometer is mission impossible. I find the best software is Garmin at the moment of writing, or at least suits me well, and it blocks me from buying any opensource watch, unless I want to have two watches on my hands

Those who love Atari might be interested. It seems that people are creating internet solely for the emulators' purpose.

Those from the new world might get interested too, when seeing this video www.youtube.com/shorts/2TNCTREaa0Q of downloading the weather, and check it against the amount of data downloaded on our phones to get the current weather forecast. To estimate the amount of data downloaded on Atari it is enough to know that the upper boundary was 19.2kbit/s on the bus (which is probably achieved by this box from FujiNet)

I'm not affiliated, I've just found this on the internet and wanted to share it with you, marvellous and devoted people

I will ride the wave of my thoughts a bit more - imagine we all have only this thing in our pockets, downloading 4kb or so of weather forecast and showing messages at light speed. Zero distractions...