Renaming 'I Code It' to 'The Pragmatic Developer'

Hi everyone,

I’m excited to share that I’m renaming my newsletter from 'I Code It' to 'The Pragmatic Developer'. I’ve always loved the name 'I Code It'—it feels like saying "I build things" or "I write books." That’s why it's been used for my blog and other platforms. However, for my newsletter, I feel the name doesn't fully convey the rich content I aim to deliver to you.

This newsletter is about more than just clean code and refactoring techniques, it's about sharing practical tips for software engineering in general. Occasionally, I also touch on topics like writing and personal knowledge management, though these aren't the main focus.

With 'The Pragmatic Developer', I plan to dive deeper into software design and craftsmanship. Imagine starting with a real-world, less-than-perfect code snippet from my daily work. I believe that scenario-based examples, particularly those that allow us to compare 'before' and 'after' versions and discuss the context in more depth, enhance learning and make it easier to apply these insights to your own projects.

I’d invite you to suggest improvements, and then I'd share my solution in the next issue, explaining my approach.

I think the best way to learn is through small, relevant examples. I'd love to hear what you think about this format or what you'd prefer. Your input is crucial.

Thank you for being part of this journey. Let's continue to learn and improve together.