-
First craft a language then build your software
-
What is simplicity in programming and why does it matter?
-
Specific vs. general: Which is better?
-
The best team ever
-
Spring Framework: Why I prefer a simpler solution nowadays
-
On crafting troubleshooting-friendly responses in web apps
-
It Is OK to Require Your Team-mates to Have Particular Domain/Technical Knowledge
-
Don't add unnecessary checks to your code, pretty please!
-
The Are No Silver Bullets: Which Error Handling Style to Pick For a Given Configuration of Constraints?
-
Challenging Myself With Coplien's Why Most Unit Testing is Waste
-
Focus & Do the Simplest Thing Possible
-
Tiny, Tiny Steps - Experience Report Developing A Feature In Minimal Value-Adding Increments
-
Frustration-Driven Development - Towards DevOps, Lean, Clojure
-
Seek Understanding
-
The Risks Of Big-Bang Deployments And Techniques For Step-wise Deployment
-
Bad Code: Are We Thinking Too Little?
-
Code Is Cheap, It's Knowledge Discovery That Costs
-
The Invisible Benefits Of Pair-Programming: Avoiding Wasteful Coding Excursions
-
Ignore requirements to gain flexibility, value, insights! The power of why
-
The Value and Perils of Performance Benchmarks in the Wake of TechEmpower's Web Framework Benchmark
-
The Sprinting Centipede Strategy: How to Improve Software Without Breaking It
-
Fast Code To Production Cycle Matters: For Pleasure, Productivity, Profit
-
Do You Know Why You Are Testing?! (On The Principles Underlying TDD)
-
My Scala vs. Clojure Impression In Pictures
-
The Best Code I Have Ever Written Is The Code I Never Wrote
-
Programming Like Kent Beck
-
Bad Code: Too Many Object Conversions Between Application Layers And How to Avoid Them
-
Beautiful Code: Simplicity Yields Power
-
How to Create Maintainable Acceptance Tests
-
Quiz: What's the Best Test Method Name?
-
What Changes When You Deploy More Frequently and Why You Should Do It
-
Principles for Creating Maintainable and Evolvable Tests
-
How to Fail With Drools or Any Other Tool/Framework/Library
-
Never Mix Public and Private Unit Tests! (Decoupling Tests from Implementation Details)
-
Only a Masochist Would Write Unit Tests in Java. Be Smarter, Use Groovy (or Scala...).
-
A Funny Story about the Pain of Monthly Deployments
-
Discussion: Agile not suitable for governmental IT?
-
What Do I Mean by a Legacy Code?
-
Code quality matters to the customers. A lot.
-
Clean Code: Four Simple Design Rules - Obligatory Read
-
If You Don't Use Pair Programming and Code Reviews as Teaching Tools You Waste Money
-
Knowing I'm Bad Programmer Makes Me Good Programmer