Backend developer | Reader | Semi-writer | Golang | Node.js | PostgreSQL | Vim enthusiast
I like to understand how things work under the hood, but not too deep.
An example of what agile is:
You want a house. You plan to build a house. You start to divide the tasks among team members.
Then, they agree on a PoC: a ground floor with some roof over it. Also a drawing of where your door will be
Then, they start building out the walls and windows until they realize there's no pipe system... So that's marked as a tech debt and they agree on giving you a portable bathroom while they fix that.
Then, there are rooms without electricity, so during the planning they agree on drop a wall so you can have light there.
But now the problem is that that wall was a dependency for other walls, so the panic starts.
And since this is a house, there's no such thing like git so you're basically screwed...
(I like agile, but I always have fun writing about the bad takes)
An example of what agile is:
You want a house. You plan to build a house. You start to divide the tasks among team members.
Then, they agree on a PoC: a ground floor with some roof over it. Also a drawing of where your door will be
Then, they start building out the walls and windows until they realize there's no pipe system... So that's marked as a tech debt and they agree on giving you a portable bathroom while they fix that.
Then, there are rooms without electricity, so during the planning they agree on drop a wall so you can have light there.
But now the problem is that that wall was a dependency for other walls, so the panic starts.
And since this is a house, there's no such thing like git so you're basically screwed...
(I like agile, but I always have fun writing about the bad takes)
thanks!