Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do.
-- Steve Jobs
Showing posts with label Clean Code. Show all posts
Showing posts with label Clean Code. Show all posts

Monday, September 19, 2011

Don’t rewrite Your Application | Java Code Geeks

Don’t rewrite Your Application - Java Code Geeks
When stuck with a legacy code base you’ll hear the claim “We’ll have to rewrite this from scratch in order to fix it!” It sounds promising. You start with a clean slate. You can do all the good stuff without all the mistakes. The only problem: It doesn’t work. Here is why.

Wednesday, April 6, 2011

Clean Code - A Handbook of Agile Software Craftsmanship

Clean Code - Slashdot
I attended Bob Martin's keynote speech and design patterns workshop at the 2010 Better Software / Agile conference in Las Vegas. His views on professionalism, software craftsmanship and clean code have definitely given me a new outlook on what it means to be a professional software developer. After reading Cory Foy's review on Slashdot I recently purchased this book and am looking forward to working through it.
As developers, system admins, and a variety of other roles in IT, we have to deal with code on a daily basis. Sometimes it's just one-off scripts we never have to see again. Sometimes we stare at something that, for the life of us, we can't understand how it came out of a human mind (or, as the book puts it, has a high WTF/minute count). But there is a time when you find code that is a joy to use, to read and to understand. Clean Code sets out to help developers write that third kind of code through a series of essay-type chapters on a variety of topics. But does it really help?

I had the pleasure of attending Bob Martin (Uncle Bob)'s sessions at several agile software conferences over the past several years. In them, Bob has a unique way of showing us the value of clean code. This book is no different. There is a warning in the introduction that this is going to be hard work — this isn't a "feel good" kind of book, but one where we slog through crappy code to understand how to make it better. The authors also point out that this is their view of what clean code is all about — and fully acknowledge that readers may "violently disagree" with some of the concepts.

Tuesday, April 5, 2011

Uncle Bob - The Clean Coder: Software Craftsmanship: What it's all about?

The Clean Coder: Software Craftsmanship: What it's all about?
Why is there a software craftsmanship movement?  What motivated it?  What drives it now?  One thing; and one thing only.

We are tired of writing crap.

That's it.  The fat lady sang.  Good nite Gracy. Over and out.
We're tired of writing crap. We are tired of embarrassing ourselves and our employers by delivering lousy software.  We have had enough of telling our customers to reboot at midnight.  We don't want bug lists that are a thousand pages long.  We don't want code that grows more tangled and corrupt with every passing day.  We're tired of doing a bad job.  We want to start doing a good job.
That's ... what ... this ... is ... about.  Nothing else.