@jherr 2/2 And then you need to decide wether to "quickfix" the bug or resolve the root cause which can be a huge refactoring sometimes.
Also when you are new to a project you need to "learn" the codebase which ofc also increases time taken in those cases.
@jherr Often, it's not just about finding the bug, but also resolving it in a proper manner. For example, while debugging you spot the cause of the bug but it turns out that the root cause is some bad design (e.g. spaghetti code) 1/2.
@TkDodo@jherr I would agree with you but I have read about this topic so so much repeatedly over the years and it is just not that easy. There are multiple approaches to do this and EACH has its downsides. Even patterns like the double-submit cookie have downsides.
@petergyang In general: You just need to try to 'move' more over the day. Static sitting (or standing!) over longer periods of time puts huge stress on your back.
@flaviocopes Thats a bad example. GraphQL has established itself. It simply isnt "hyped" anymore but is just considered where it makes sense. It might not be as popular as classic REST but it is still widely adopted.