@GergelyOrosz No, the problem with big upfront planning is that it lacks context discovered through build, test and customer feedback processes. That feedback cycle is still required, but build phases can do more upfront as agent interviews can now provide some of that technical context
@eloffd@Grady_Booch@unclebobmartin No, it's the difference between a tool and a purpose. An implementation mindset versus a customer focused mindset. If the focus is on tools and not customer value, then value is unlikely to be delivered regardless of the toolset used.
@allenholub My daughter is in her last couple of weeks of school, is an avid fiction author and staunchly anti-AI. She uses tech to increase her productivity by using an app which wipes everything you've written during a session if you stop writing for a configured duration, circa 30s ๐คช
@brankopetric00 Even as part of a team running K8s apps on an internal cloud, when expanding to AWS, ECS was the way to do (admittedly after initially going EKS)
@GergelyOrosz The message shown in OP is specifically about incoming calls. Banks never call so all can just do this for any incoming call without knowing whether a legitimate call is in progress. Is behaviour the same for an outgoing call?
@slimjimmy Being a "smell" is not the same as "never do this". It is now like.. "hmm.. are you sure this cannot be located with data in a structure that reflects key concepts in the domain". You don't want to end up with bags of static functions tied together with spaghetti
@MichelSchudel@devo_1010FF@mariofusco True. Also code generation. Annotations are meant to be a soft coupling enabling behaviour within an enabling context. Lombok corrupts this completely. If you don't like the language, use a different one, but, I'd like to be able to compile Java with.. the java compiler.