3 Not So Obvious Things I Learned From 10 years of TDD
(This was originally published as a Twitter thread. I think it deserves to be preserved in a less ephemeral medium.
Book Summary: The Pragmatic Programmer 20th Anniversary Edition- Chapter 1
This article is the first from a series where I’m going to summarize important
books for the software engineering
TDD: Act-First to Drive Design
> I know tests should drive the design, but I never really understood how to do
it. And I don’
There's no such thing as a technical decision
Let me just tell you something right away: strange as it sounds, your goal as a software developer is not
Solving Real World Bad Design by Applying the Tell, don't Ask Principle
Can you spot bad design when you see it? Can you tell what’s wrong here?
if (!response.getStatusCode().is2xxSuccessful(
Build people, not tech
Retrospectives, build-measure-learn and continuous improvement are all
activities and practices that companies and their agile teams do to support
project
The simple act that changes the future of your team
On my previous article, I talked about how bad clever code is and how to avoid it. And at the
Clever code is bad. Don't write clever code.
“Wait! Isn’t code supposed to be smart? Programming IS hard! We have to be smart!”
Nope.
Code is supposed
The one skill I wish I master as a Tech Lead
I’ve been leading teams for 5 years now and I can tell you: it’s freakin’ hard – but not
3 books that will take you to the next level
You can write code and make the computer do what you want – no problem. You can even do it in
