Ahh the famous git commands such as sort, uniq, head, and grep.

deleted by creator

The article says nothing about genai and uses a paywalled article as its source. A second source is an article written by the author.
Not sure what barrow this is peddling, other than repeating the absurd notion that software engineers are paid too much whilst the Australian Computer Society promotes articles stating that they should be paid at 1995 pay rates.

Are you disagreeing

As an ICT professional with over 40 years experience, all I see is poorly informed HR teams hiring the very cheapest graduates they can find and believing that Assumed Intelligence will make it all better after they decimated their experienced staff.
No wonder we have escalating data breaches and security nightmares, not to mention unstable consumer electronics and a growing list of terrifying trends in vehicle software implementations with absolutely no global mechanisms for regulation or certification

or agreeing with the author?

I’m not sure if my reading comprehension is what it used to be, but the author of the article seemed to share similar concerns with you.

Exactly.

Another problem with LLMs is that they are actually useful in some tasks and they can generate very good quality code if you’re diligent enough developer. I also have built personal tools with them, but I don’t have the knowledge of the code the LLM has hallucinated which means that before I would push this code forward I will have to basically familiarise myself with the code in a way how a code review works.

The knowledge you gain from this is also different from that of actually writing and running the code yourself. I have seen people who use LLMs to write commit messages which is the last thing you should do. Commit messages are probably the only places were we can meaningfully store the knowledge gathered during development and the more I see LLM commits the more I lose hope.

With more and more places pushing LLM generated code I’m getting real review fatigue. Code reviews used to be very reasonable and you could be very mindful about other persons code. Now it’s starting to be just LLM generated code which makes reviewing tedious as you are reading the same sloppy stuff in hopes that you can build your mental model of the changes to codebase before new LLM slop bomb hits the PR queue.

I worded my answer a bit wrongly.

In XML <person><name>Alice</name><age>30</age></person> is different from <person name="Alice" age="30" /> and they will never (de)serialize to each other. The original example by the articles author with the person is somewhat misguided.

They do contain the same bits of data, but represent different things and when designing your dtd / xsd you have to decide when to use attributes and when to use child elements.

The same data can be portrayed in two different ways.

And that is issue why? The specification decided which one you use and what do you need. For some things you consider things as attributes and for some things they are child elements.

JSON doesn’t even have attributes.

I’ve been pretty depressed after my burnout few years ago and have been unable to enjoy programming ever since. It’s my profession though so I still do it, but outside of the professional stuff I’ve only had a 1 month this year where I could enjoy sitting on a computer at home and to do some actual coding. Outside of coding there’s a lot of pondering, designing, and analysing related to development that I still do and enjoy, but it’s exhausting after working.

So you saw the vote for these three suggested names:

• Projected Source Control for Git
• VFS for Git
• Sparse VFS for Git

And decided that Filey McFileface won?