Code complete and enterprise architecture books | Ramblin' & Amblin' | Oct 27, 2026

I think two of the most valuable books that I've read on software engineering, software developments, are CodeCom plete, one, and then two, and you don't necessarily need to read both of them. The point about CodeComplete is that it is holistic, it covers different languages, it covers different concepts, it has historical backing, it will take you through a broad range of topics inside of software engineering that will help you have a more cohesive, connected understanding of why things are the way they are in software engineering and where it came from. So it isn't so much just, here's how to write code, but it 's, here's how to write code and here's how it was written in Vortran, here's how it was written in Java, and see, you know, like, and it goes back in history, and it exposes to a lot of different thoughts, it's very, one of my favorite curated books. The other one is Patterns of Enterprise Application Architecture, that one I treat more like a recipe book of different concepts that's come together, like understanding message cues, things like extraction patterns, and a broad range of stuff that isn't as low level as the gang of four books, book where it really goes into the depth of how to like build a command object, how to build a service object, how to, I mean, service objects I would find in Panerts of Enterprise Application Architecture.

I want to make sure I'm not misrecalling here the enterprise integration patterns, they look very similar and I kind of like mix them a bit in my head, but for me, it was, I really really valued code complete and patterns of enterprise application architecture, I'm going to also give a shout out to the original FXCOP guidebook from Microsoft back in the early days of .NET when they came out with FXCOP, and this was really one of my first interactions with Trulinter that formatted and had opinionated guidance. That's ultimately, that's ultimately helped me reason with the code because the trick is that you use these tools to inform you, just like a spell checker, it's there to, ah, bureaucracy, I got to spell that word again, I got it wrong again. And then, and then sit there and, you know, practice it and then retype it, don't let it just auto-fix for you, but, um , ah, yeah. Yeah, uh, code complete, uh, that was foundational for me and, ah, the, um, patterns of enterprise application architecture and FXCOPs were incredibly useful for me when I was working on the, ah, real-time project for TicketsNow and, um, expanding my skills and also having a shared, um, language.

That I could sit down and point at a concept with my team and, and my collaborators and say, okay, this is, this is what we're doing and why. And I didn't have to explain it, you can just read the book . All right, thanks. Bye.