Statistics

Total Posts: 34
This Year: 0
This Month: 0
This Week: 0
Comments: 0


RSS 2.0

Recent Posts


On this page....


Archives

 Full Archives By Category
 2007 Calendar View

Categories


Admin

Sign In

Acknowledgments

DasBlog Theme Design by: Tom Watts
E-mail: Send mail to the author(s)
Theme Image by: dreamLogic

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

 Monday, February 02, 2009

This blog post is part of a series of blog posts concerning a Clean Code study circle that we developers at Admeta are persuing during 2009. Here you can find an introduction concerning the question why we are doing this and here you can find an overview of all chapters as well as some study circle recommendations.

Chapter 1 Clean Code questions:

  1. Before reading, take a moment to reflect what the concept of Clean Code means to you.
    • Is there anyone of the different "guru's" description of Clean Code (p7-12 + forword) that do you think lies closest to your own definition of Clean Code?
    • After having read the chapter, has the reading changed your conception?
  2. What is your experience / opinion of code generation tools or any other higher abstraction level of programming (4GL)?
    • Do you have any good or bad experience of building your own code generator (in some way)?
    • Where do you think we are heading when it comes to abstraction levels in languages and tools?
    • Do you consider this to be a bright future for us developers?
    • extra: What do you think of Joel Spolskys described "The Law of Leaky Abstractions"?
  3. Have you experienced something like "the Grand Redesign in the Sky" and how did that end?
  4. What is / has been your explanation to having written bad code (as we all have done!) in the past?
  5. Do you think it is suitable for us as a team to align to a "School Of Thoughts" (p12) or do you see any better path to having a more uniform clean code conception?
  6. What do you think of "the Boy Scout Rule" (p.14) applied to code?
  7. Are you familiar with any or all following Principles of Design (S.O.L.I.D.) (p15):
    • SRP - The Single Responsibility Principle
    • OCP - The Open / Closed Principle
    • LSP - The Liskov Substitution Principle
    • ISP - The Interface Segration Principle
    • DIP - The Dependency-Inversion Principle
  8. What do you think is the status of Clean Code at our company?

As a side-note, Robert C. Martin and Joel Spolsky, the two people basically mentioned above, seem to be disagreeing a lot these days (excellent summary here by Niclas Nilsson). I guess they have not read my writing upon the Truth vs the Truth... :-) They seem to have made up somewhat in the end though.

Tuesday, November 24, 2009 2:10:45 AM (GMT Standard Time, UTC+00:00)
Sorry. You need only reflect that one of the best ways to get yourself a reputation as a dangerous citizen these days is to go about repeating the very phrases which our founding fathers used in the struggle for independence.
I am from Fiji and know bad English, give please true I wrote the following sentence: "Mortgage note, mortgage decision protection insurance will thereof result you for your mortgage promises and first semiannual note stacks."

With love :-D, Ieesha.
Name
E-mail
(will show your gravatar icon)
Home page

Comment (Some html is allowed: a@href@title, b, i, strike, u) where the @ means "attribute." For example, you can use <a href="" title=""> or <blockquote cite="Scott">.  

Enter the code shown (prevents robots):

Live Comment Preview