Torsten Severing
torstensevering.bsky.social
Torsten Severing
@torstensevering.bsky.social
Reposted by Torsten Severing
This is why ISO certificates mean absolutely nothing

PostNL has ISO certificates on everything... but then ships this kind of bug to production, making it unusable. Clearly no E2E tests, no monitoring

(We always knew ISO was BS for software development - but now there's proof)
January 23, 2026 at 12:31 PM
ah, that makes perfectly sense. Yes, I don't use SSR.
December 9, 2025 at 7:30 PM
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.
December 9, 2025 at 6:47 PM
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.
December 9, 2025 at 5:28 PM
Maybe this is helpful to you: I use this simple self written middleware in NestJS for that: github.com/shaman-appre...
github.com
December 9, 2025 at 5:24 PM
100% agree. prompting -> reading -> accepting is a start, but sitting down and actual working with it gives you a much deeper understanding.
December 5, 2025 at 4:12 PM
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
November 19, 2025 at 3:20 PM
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.
November 19, 2025 at 3:20 PM
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.
November 13, 2025 at 4:52 PM
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.
November 13, 2025 at 4:51 PM
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.
November 13, 2025 at 4:51 PM
They can make it work - great! They saved hand-offs, communication overhead, got immediate feedback...
November 13, 2025 at 4:50 PM
Now, none-developers cannot only "expect both", but quickly try it themselves with different outputs:
November 13, 2025 at 4:48 PM
> 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 👍
October 26, 2025 at 4:49 PM