Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
bosi5093yNot that long so nothing useful like refactoring or test or code style improvements were left.
I love it when in a sprint is time left to just do a bit of housekeeping in our apps. -
@bosi that’s where we are right now is just refactoring the entire codebase to Kotlin because we have no issue tickets right now 🤷🏾♂️
-
sariel85873yBeen doing that for about 3 months now.
When I take one if these tickets though, I'm told it's not important enough to work on, but they also told me the day before to make the ticket and work it. -
Ison1113y@100110111
This seems like the most sensible compromise if you're not willing to honestly tell a higher up that you're out of work and can take on something else.
Refactoring for the sake of refactoring is not a practical approach. If you're out of work, take some backlogged tasks or perhaps work on some infrastructure projects. -
@Ison I would like to agree with you. However, in our case, that is exactly what we are supposed to do if we have no issues of higher importance. If you’re working with a system where tech debt has accumulated unchecked for 15 years, there’s no excuse not to do some housekeeping, or in this case, even renovation.
Related Rants
Has anyone else ever been stuck in a 'doSomething()' limbo where your dev section has no tickets so you have to create your own tickets so that you still seem productive?
rant
wtf
tickets
bored
kotlin
java
work
mobile