Follow Me
About
This blog is about software development. It's about figuring out how to improve ourselves, our code and the development process. There will be lots of questions and occationally, some epiphanies of mine.
My name is Johnny Bigert, and I am a software developer living in Stockholm, Sweden. I specialize in object-oriented software architecture and software testability. Visit my home page (mostly in Swedish).
Twitter Updates
-
Recent Posts
Most Viewed
- Design Patterns By Example: Implementing a State Machine - 11,750 views
- Design Principles by Example: Talk to an Interface or an Abstraction? - 4,330 views
- Object-Orientation is not Really About Objects - 1,322 views
- “We Train You to Be the Best Programmer You Can Be” - 1,315 views
- Email Subscription - 1,257 views
Recent Comments
- Johann Gerell on Characteristics of a Software Professional
- Gunnar Andersson on Characteristics of a Software Professional
- Johnny on Abstraction vs Compression
- James Coplien on Abstraction vs Compression
- Johnny on Sustainable Software Development, Part 1: Managing Technical Debt
Categories
Tags
abstraction acceptance test book bug fixing code coverage code smell collaboration communication company concurrency decoupling design pattern design principles development process Eclipse education employee experience functional test innovation interface inversion of control Java JUnitMax lean software development locks message passing modularity object-orientation OSGi production code programmer programming skills quality recruitment reduce waste software professional sustainable development test-driven development test code testing threads training unit test user interfaceArchives
A blog about the joys and perils of software development
Monthly Archives: April 2011
The Truth Behind Design Patterns
Design patterns help you write good software. How can you master all 23+ of them? You are probably better of focusing on the underlying truth: the design principles. Continue reading
Posted in Software Development
Tagged design pattern, design principles, object-orientation
Leave a comment
Design Principles by Example: Talk to an Interface or an Abstraction?
What is the relation between design principles “Talk to an interface, not an implementation” and “Talk to an abstraction, not a concrete”? When you apply them, you want to achieve different goals. Continue reading
Posted in Software Development
Tagged abstraction, decoupling, design principles, interface
Leave a comment
Object-Orientation is not Really About Objects
How do we write good object-oriented programs? Despite the name, it is not by focusing on objects. [...] From time to time, you come across OO programs that has a procedural flavor to them. There are few, if any, interfaces and classes are primarily used to organize related functions with data. Writing “procedural style OO programs” like this suffers from the same problem procedural programming do: coupling. [...] Continue reading
Posted in Software Development
Tagged decoupling, design principles, interface, object-orientation
3 Comments
Duplication-Driven Development?
What is the primary force that drives you when doing test-driven development? Surprisingly, it might just be code duplication. The book “Test-Driven Development by Example” by Kent Beck shows how code duplication springs naturally from TDD and *drives good design*. An appealing thought?
Continue reading
Posted in Software Development
Tagged code duplication, code smell, design pattern, test-driven development, unit test
Leave a comment
Great Books for a Software Developer
I have received questions about good books, so I thought I would share some titles with you. First, my absolute favorites, should be mandatory reading for everybody (so go ahead and read them right away): [...] Continue reading
Twitter Updates
