Graf Zahl wrote:I don't want to insult you, but I got a colleague like that, too. And this guy's driving me nuts because ultimately his attitude works against the project.
Hehe, I don't doubt that. Having someone like me on the team has its pros and cons, just like with every other developer personality.
Graf Zahl wrote:True, but in general, when the backlog is not cleaned the project won't go forward. How do you manage? Where I work there's a clear roadmap what needs to be done, but keeping the backlog of issues in order is the most important thing because if that becomes a problem, the project would be in trouble.
Where I currently work I'm responsible for coding one of the epics from the roadmap. I usually don't deal with the small feature requests or bug tickets. If a ticket does get assigned to me I do eventually fix and close it, so it isn't like I completely 100% ignore the ticket system. I just don't use it to manage my own thoughts and plans like some other developers do.
Some development methods (mostly scrum/agile) thinks my kind of role shouldn't really exist. In those systems all developers are treated as alike and I'm supposed to decompose my entire battle plan into 1-2 day tasks before even really starting. Then my boss/scrum master needs to ask me every day if I solved the current task yet, officially to "help" me, but in reality to force me to walk forward ("sprint") every single day - like whipping an ox. It might very well be more efficient, but it sure hell isn't fun to work like that. So when I "forget" to do things, it is partly my way of sabotaging systems that I find destroys the fun of working.
Sorry to folks that feels those systems work for them - anyone insisting I need to follow them is effectively asking me to quit. Luckily for me, there's plenty of jobs out there that aren't drowned in this kind of red tape. They are usually more fun, too, as the agile method is usually overkill in the startup phase.