Writing solid code
by Steve Maguire · first published 1993
72% recommend28% neutral
Why HN recommends it
Practical, easy-to-read advice on preventing bugs, with C examples that apply to any language. It explains why code is good and suits newer programmers and teams building defensive coding habits.
Summarised by Claude from recommending comments
A Microsoft developer examines the problem of programming "bugs, " showing how and where developers make mistakes along the development process and providing ways users can detect errors early. Original.
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2012–2025Algorithms on strings, trees, and sequences
Dan Gusfield
Recommended by 3 · mentioned by 63 recommend · 6 mention3 recommend · 63 recommend
2011–2022Debugging the development process
Steve Maguire
Recommended by 6 · mentioned by 86 recommend · 8 mention6 recommend · 86 recommend
2007–2026Code Complete
Steve McConnell
Recommended by 393 · mentioned by 669393 recommend · 669 mention393 recommend · 669393 recommend
2007–2026The Practice of Programming
Brian W. Kernighan
Recommended by 90 · mentioned by 12890 recommend · 128 mention90 recommend · 12890 recommend
2020–2024Righting Software
Juval Löwy
Recommended by 4 · mentioned by 94 recommend · 9 mention4 recommend · 94 recommend
2007–2026The Pragmatic Programmer
Andy Hunt, Dave Thomas
Recommended by 353 · mentioned by 589353 recommend · 589 mention353 recommend · 589353 recommend
2011–2026The Art of Readable Code
Dustin Boswell
Recommended by 11 · mentioned by 1411 recommend · 14 mention11 recommend · 1411 recommend
2007–2022Software project survival guide
Steve McConnell
Recommended by 12 · mentioned by 1512 recommend · 15 mention12 recommend · 1512 recommend
…few people in these positions have heard of them, let alone read them. For example, the Microsoft Press books form the 90s are great. Debugging the Development Process, Software Project Survival Guide, Writing Solid Code, Rapid Development, and then books like The Mythical Man-Month, and Peopleware. Just a passing familiarity is all I ask. But no. Favored people and 'can't be hit by a bus' people get away with anything,…
on “Get Shit Done: The Worst Startup Culture” ↗The best book I ever read about programming was Writing Solid Code, by Steve Macquire.
on “Five Memorable Books About Programming” ↗Another classic: "Writing Solid Code" by Steve Maguire http://www.amazon.com/dp/1556155514
on “Cello: Higher level programming in C” ↗Try having your team read these books: http://www.amazon.com/Writing-Solid-Code-Microsoft-Programmi... http://www.amazon.com/Practice-Programming-Addison-Wesley-Pr... http://www.amazon.com/Code-Complete-Practical-Handbook-Const... I know these are old books and are C and C++ oriented,…
on “Ask HN: How do I get my team to write better code?” ↗I didn't think it was ever worth reading. Steve Maguire's "Writing Solid Code" was much better, though TBH it's been so long I have no idea how it holds up.
on “Books Programmers Don't Really Read (2008)” ↗One of the seminal books for me was Writing Solid Code[0], written about 25 years ago. It's quite dated, but has a lot of stuff that is still relevant. I remember that one of his sections was titled "FLEXIBILITY BREEDS BUGS". Here's the first paragraph:…
on “Software Design for Flexibility” ↗I've found some books like Maguire's "Writing Solid Code" and McConnell's "Code Complete" to be helpful, but your best resources are probably the source code to systems similar to your definition of 'real'. Depending on this definition, I'd suggest looking…
on “30 years of C” ↗…graduating from university and it was great preparation for real-world programming work. The other programming epiphany books for me were: * Eric Evans' "Domain-Driven Design" * Steve Maguire's "Writing Solid Code" * and SICP
on “Code Complete” ↗I've read some of the books listed, but the two books that completely changed how I write code weren't---_Writing Solid Code_ by Steve Maquire and _Thinking Forth_ by Leo Brodie. The second one is by far the more mind bending of the two, and it's available online (for free) if you search for it.
on “What is the single most influential book every programmer should read?” ↗Agreed on Code Complete. Never understood why people thought it was worth reading. Much better is Steve Maguire's Writing Solid Code.
on “Books Programmers Don't Really Read But Recommend” ↗I've read both, and while Code Complete covers a LOT of ground, I like Maguire's style and his practical information. I wouldn't want to be without Code Complete, but Writing Solid Code (and his followup, Debugging the Development Process) has plenty of decent info. And some dated. Much of Maquire's coverage is VERY C++ centered, so people using anything else are going to skip a bunch.…
on “Books Programmers Don't Really Read (2008)” ↗McConnell, Steve. Code Complete. Redmond, WA: Microsoft Press, 1993. McConnell, Steve. Software Project Survival Guide. Redmond, WA: Microsoft Press, 1998. Maguire, Steve. Writing Solid Code. Redmond, WA: Microsoft Press, 1993. Ranade and Nash. The Elements of C Programming Style. New York: McGraw-Hill, 1992. Kernighan and Plauger. The Elements of Programming Style. New York: McGraw-Hill,…
on “Ask HN: What are the books you wish your colleagues had read?” ↗Writing Solid Code by Steve Maguire - 245 pages but really well written and an enjoyable read. Examples in C but principles are applicable with any language.
on “Ask HN: Best books under 200 pages for developers?” ↗Writing Solid Code by Steve Maguire Really well written and an easy read. Examples in C but applicable to any language. At some point I was reading it once a year.
on “Ask HN: Best book for software engineers (besides the well-known ones)?” ↗…and none of us writes perfect code. If "Bob" had learned from his peers during code reviews, he would have been fine. To answer your question: The Pragmatic Programmer by David Thomas and Andrew Hunt, Writing Solid Code by Steve Maguire, and Code Complete by Steve McConnell.
on “The sunny side of firing someone” ↗