Tag Archives: good design
I’ve been wanting to set up a software-development blog for some time. And for some time I’ve been wrestling with the pains of managing multiple WordPress blogs. Back in the day, when I had just my writing blog and a … Continue reading
This blog post is intended to sabotage any chance that I’ll get a “normal” software-engineering job, because I don’t think I could ever go back to a “normal” job.
Writing is a communication skill. And they say that communication skills and the other soft skills are what programmers need today. Effective developers don’t work alone. They work with others in a team. And a team member needs to communicate … Continue reading
What is “good” code? Some define it as “beautiful.” Some equate it with experience. Some with cleverness. Some can’t tell you what it is. Others know it when they see it. For me, “good” means maintainable. Good code, yes, has … Continue reading
I’ve been meaning for some time to write about how slow “quick and dirty” is, how misnamed the term is, how misguided are the hoards of managers (many of them former and current software developers) who embrace “quick and dirty” … Continue reading
Have you ever been here? Refactoring old code, seeing new code that partially de-factors it, and taking out my frustrations in code comments. The old comment for a struct declaration: // This structure will be generated // and stay with … Continue reading
Quality is one of those ineffable abstractions. Ask ten people, “What is good design?” Get twenty answers. But Jim Shore’s answer is actually worth something. A good software design minimizes the time required to create, modify, and maintain the software … Continue reading