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,753 views
- Design Principles by Example: Talk to an Interface or an Abstraction? - 4,333 views
- Object-Orientation is not Really About Objects - 1,323 views
- “We Train You to Be the Best Programmer You Can Be” - 1,315 views
- Email Subscription - 1,258 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
Tag Archives: test code
How Do We Know Our Tests Work Tomorrow?
When writing a test case, good practices suggest that we verify the test can fail. But how can we know the test code doesn’t break later? Continue reading
Posted in Software Development
Tagged test code, test-driven development, testing, unit test
Leave a comment
Test-Driven Development Done Right
A couple of years ago, I had at least two misconceptions about Test-Driven Development: (1) you should write all your tests up-front and (2) after verifying that a test case can fail, you should make it pass right away. [...] Continue reading
Posted in Software Development
Tagged book, interface, production code, test code, test-driven development, testing, user interface
Leave a comment
Twitter Updates
