1. Software Development in the Twenty-First Century
I remember the early years of my career, back in the 1990s. After three years, I considered myself a senior developer. I could mix assembly with Pascal and impress my friends. I could code fluently in at least four programming languages. Most important, I could write cryptic Delphi code—using very few lines of code and obscure Windows application programming interfaces (APIs)—that very few developers were able to understand.
That’s how seniority was measured back then. If you couldn’t understand a piece of code, normally it was because you were not senior enough. And writing code that no one else could understand would make you a senior developer straightaway. It was very common to hear managers ...
Get The Software Craftsman: Professionalism, Pragmatism, Pride now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
