Productivity

It took some time before I could say that TDD really works (for me). I don't think the problem was TDD, but my design and coding skills.

Seamless user experience and resolving conflicts are the biggest challenges when developing collaborative apps.

Producing more code in a unit of time is not a measure of high-quality code or productivity. Let's dive deeper into measuring developer productivity.

It's rubbish, says Grady Brooch. This kind of surveillance makes geeks feel less safe, says Kent Beck.

This is how we went from a startup of 4 to a company of 20 people, all working remotely.

Let me share what I've learned, as an engineer who has deep-dived into the business side of the pool, about why priorities change, and how that actually benefits me.

A few thousand lines of code everyone is satisfied with and understands used to sound like science fiction – now it was reality.

In an attempt to speed up our development process, my teammates and I took a somewhat controversial route – we introduced pair programming. And it worked. 

Engineers often use the rubber duck approach when they are stuck, but why not draw for our little yellow friend instead?

The term was coined by Ward Cunningham in 1992. at the OOPSLA conference [1] as a metaphor for developing a software asset. He concluded that the development process leads to new learning, as it depends upon artifacts he coined as technical debt.