Going back to old discussions with engineers, architects and CTOs, I noticed that practically all of them started their projects with passion and commitment but got trapped in the most crucial moments to be stuck with complexity, over-engineering and money-draining.
In a world where specialization is often hailed as the pinnacle of success, I find myself cheerfully perched atop the hill of ambiguity, happily wearing the badge of a “polyglot” in the tech cosmos.
The role of the software architect is yet a subject of various debate: it’s vaguely determined, hard to define and sometime misleads to nonsense responsibilities in some job descriptions.
I was asked often to help many of my customers making or launching their new website or portal, I won’t go here through the life cycle of such project but just focus on the real first step after getting contact : gathering information.
nine some years ago, I started wearing my freelance hat as a software developer … it started as simple tasks to become now a full professional activity to design or build full systems.
