This reminds me of a colleague who was always ranting that our code was not documented well enough. He did not understand that documenting code in easily understandable sentences for everybody would fill whole books and that a normal person would not be able to keep the code path in his mental stack while reading page after page. Then he wanted at least the shortest possible summary of the code, which of course is the code itself.
The guy basically did not want to read the code to understand the logic behind. When I took an hour and literally read the code for him and explained what I was reading including the well placed comments here and there everything was clear.
AI is like this in my opinion. Some guys waste hours to generate code they can’t debug for days because they don’t understand what they read, while it would take maybe two hours to think and a day to implement and test to get the job done.
I don’t like this trend. It’s like the people that can’t read docs or texts anymore. They need some random person making a 43 minute YouTube video to write code they don’t understand. Taking shortcuts in life usually never goes well in the long run. You have to learn and refine your skills each and every day to be and stay competent.
AI is a tool in our toolbox. You can use it to be more productive. And that’s it.
My house is operating at around 3,5-4 bar after the pressure regulator. Since I have no gauge I can‘t deliver the pressure of the supply. I guess it is around 6 bar. Small town in Germany.
We also have mandatory check valves since a couple of years to prevent water from entering the supply from the buildings in case the pressure drops.