Thank you, I'll check it out

Yes! Będę szybko i skutecznie mówił o kilku podstawowych rzeczach co by zrozumiał się biznes i developerzy.

Cool ideas: On the protocols which are text based (REST over HTTP, for example), use AI for self-healing when unexpected behaviour happens. Sure, it will be a lot slower, but it would be fun to see two apps talking to each other, trying to handle a situation before passing to developers.

I feel pretty much the same, with one thing I'd like to ask you - can you elaborate on the errors more and tell how much these are distracting you? I hear a lot of conversations about AI generating errors, but my own experience is that none of them was worth remembering for more than 5 minutes.

Yes, especially if written in a consistent manner (no stray return create_object() in the middle ;) )

You can have abstractions, but the "clever" ones are usually the ones that only you can understand, before you don't.

One more thing: Think about rewriting tests every time you play the game and see that the systems are not coming together to a fun experience, and you need to scrap the idea and do something else.

Tests become a lot harder to keep if you're pivoting week after week or month after month.

Function patterns: early exit or ”no, no, yes!” | Michał Moroz A pattern for functions that makes them easier to read and reason about.

michalmoroz.com/writing/func... – a simple idea helping to write better code. Stay tuned for more bits and pieces. #programming