Our industry has come far; we moved from direct memory access on those early machines to various architectures and abstractions. Many of us built our professional careers through the mobile revolution. The landscape is shifting drastically. With cross-platform frameworks maturing, backend-driven UI architectures expanding, and, ofc, AI tools dramatically lowering the syntax barrier, the traditional walls are crumbling. I'm convinced the job of a developer will not go away, but it's changing. What we will explore together: - Do we even still need the traditional split of specializations like mobile, frontend, and backend developers? - For those who have tried transitioning teams or themselves to a true "full-stack" model, a path I chose myself: where did you hit the hardest friction points? - If we assume the traditional lines continue to blur, how should we change the way we interview, hire, and mentor the next generation of engineers who are entering the field right now? These questions are designed to stir up healthy debate, moving the room from nostalgic reflection to concrete forecasting. Let's talk about how we got here and where we can go from here in the new era.

For a generation of developers, Uncle Bob’s Clean Code wasn’t just a book—it was a manifesto. While "Effective [Add Language here]" books guide us in syntax, Clean Code taught us our coding standards. A set of rules so strict that many criticized it, such as the number of lines per method. But the game has changed. The hands on the keyboard are often no longer human, and the code our LLMs write is far from what traditional “Clean Code” is. AI favors verbosity over abstraction and completion over long-term maintainability; it even adds “evil” comments everywhere because that’s how its completion works. Are these rules still valid when refactorings happen in the blink of an eye? But humans will still review the code, won't they? Let’s revisit the rules!