Nice, I should rename my article too, I actually told the readers how to repay the technical debt, in time without full sprints refactorings. Basically including the time in the next tasks, like you said too.
There are many topics to talk about, including Efficiency vs Productivity, fixing issues is not always the same with writing code.
I would also include at "stop wasting time in meetings and stand-ups." most of the Scrum meetings, but that's a subject for an entire book.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
I read your linked article--very nice. I can tell you've been deep in the trenches and survived. I especially agree with your points about continuous small improvements and how long it takes to convert crappy code into less crappy code.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice, I should rename my article too, I actually told the readers how to repay the technical debt, in time without full sprints refactorings. Basically including the time in the next tasks, like you said too.
There are many topics to talk about, including Efficiency vs Productivity, fixing issues is not always the same with writing code.
I would also include at "stop wasting time in meetings and stand-ups." most of the Scrum meetings, but that's a subject for an entire book.
Thanks.
I read your linked article--very nice. I can tell you've been deep in the trenches and survived. I especially agree with your points about continuous small improvements and how long it takes to convert crappy code into less crappy code.