ah, that makes perfectly sense. Yes, I don't use SSR.

I strictly separate frontend (Angular) code and backend (NestJS) code. I put shared code into a plain (npm) module, and install it in frontend and backend relative from file path like "../shared" or use npm workspaces. If you have more advanced use cases maybe utilize something like nx.

The ability to write Angular libraries which are not hard coupled to an Angular version, so that I don't have to upgrade all my libraries with each major Angular version.

Maybe this is helpful to you: I use this simple self written middleware in NestJS for that: github.com/shaman-appre...

100% agree. prompting -> reading -> accepting is a start, but sitting down and actual working with it gives you a much deeper understanding.

To be honest, I am not even sure, if right now the secondary costs exceed the gains of our genie - although, I would miss my genie as tool for sure

I absolutely feel the pain and call it "secondary cost of AI" - the time we invest in learning, configuring and controlling the genie, that we could have spent elsewhere.

As a general positive side-effect, which no code approaches didn't had: Writing specs for the AI (aka reasoning about the specs and writing docu) has now somehow become "sexy" for everyone.

They can't make it work - They haven't burned to much time. Now, the are hopefully more sensible about the trade-offs of invested time / possible customization etc, as they have felt some pain themselves.

Even if the (AI-) code will need expensive maintenance in the future, it will be a net profit for sure; in the worst case it can be re-developed (by an expensive developer) from scratch again with a validated user workflow already in place for reference.

They can make it work - great! They saved hand-offs, communication overhead, got immediate feedback...

Now, none-developers cannot only "expect both", but quickly try it themselves with different outputs:

> The AI coding discourse is a mess because we're all arguing from different vantage points

That is an obvious point, i didn't think at all about 😅 Always a pleasure and educational to read your thoughts 👍

(not to mention all the environmental, social, legal problems... - interesting times in many ways 🙃)

Nonetheless, I truly believe AI is a great additional tool for many things, especially for software development. But applied mindlessly, I fear about many unstable production systems, security issues, investment in money and time which could have been better invested in other things than AI

To admit, you created a system with among others expensive developers but cannot deliver the expected value; doing honest self-analysis / culture of praising mistakes and learning from them... I think, that is an important part of the real issue, but is not so easy and nice for certain egos.

I had a good read, thx!

I think, many managers are frustrated that their software projects are neither on schedule nor within budget, while developers are a major cost driver. Therefore, they strongly want to believe in the AI hype, which would be a nice, easy way out.