Author: stanley
-
Write Self-Documented Code
I don’t know if anybody actually reads the comments that we sometimes write as Javadoc. Do you? I don’t, most of the time. That’s why I think it’s important to write code that speaks for itself and that does not need a comment. I’d go this far: if you need a comment, your code should…
-
Thoughts on Object Oriented Programming
Object Oriented programming is hard. It’s easy to program in a language like Java, but hard to get it right. Why? Because Object-Oriented programming is more than just writing classes and methods. OO programming is way more than that. I think the hardest thing in OO programming is the ability to create objects with cohesive…
-
My SOA Views
I have not done any SOA development yet. I’ve just been reading and hearing a lot about it. I’m reading the Enterprise SOA e-book at ACM.org now (my first on SOA; so far it is a very good book) and I just want to share some of my SOA views. I think the Service Oriented…
-
Code Style Is Important
Lessons from the Google Web Toolkit… I’ve been looking at the sample projects from the Google Web Toolkit. Mostly looking at code and playing around with the apps. Based on this, I think I can learn couple things from the toolkit and the source they provide. First of all, if you have not looked at…
-
Never Duplicate
How many times have you been thinking “let me just copy this here. It’s not going to change. And if it changes, I’m going to modify it in both places.” I think that’s a critical sin. You might remember, but the next maintainer might not. I have commited it many times, no doubt about it.…
-
Programming on Purpose — P.J. Plauger
This book is dated, no question about it. However, it contains several excellent essays that are as relevant today as they were decades ago. A lot of the techniques discussed in the book are no longer used. This was a book written in the days of structured programming. Those days are over. Thus, I found…
-
Encapsulation vs Abstraction
I must admit. I am still having hard time seeing a real difference. I am still having hard time defining them both.One thing I am sure: both are fundamental principles of object oriented programming. I am going to try to learn them here and explain the differences. Just so I know for future. “Abstraction and…
-
A Simple Design
Simplicity always wins, in my opinion. The following two quotes from Programming Pearls (book I’m reading now) need no further comment: they nail it.
-
Architects Must Write Code
That’s an exact title from Johanna Rothman’s blog post. I totally agree: architects must code. If you an architect you need feedback. You need feedback because you want to make a better architecture in the future, to make improvements, and to see what doesn’t work. How do you get that feedback? You need to write…
-
Duplication Principle
What’s the single most important thing when writing code? And practical? To me, it’s the DRY, OAOO principle. Don’t know what those acronyms mean? 🙂 Don’t Repeat Yourself, and Once And Only Once principle. Not repeating the same code in different places is the single most important thing you can do to make your project…
Recent Posts
- Hello world!
- The Software Craftsman
- Write Debuggable Code!
- Effective Programming: More Than Writing Code
- Fundamentals of programming
Tags
2010 2011 abstraction advanced Books code concepts Craftsmanship design patterns encapsulation goals gof grasp immutability innerclass Java javascript jpa learning patterns practicing quality Quotes reading recommended reference solid tdd testing unclebob
Comments
Good blog! I really love how it is simple on my eyes and the data are well written. I'm wondering…
Hi, this is a comment. To get started with moderating, editing, and deleting comments, please visit the Comments screen in…