Post AUsb8Ij9qCSiIHHqKG by zstix@fosstodon.org
 (DIR) More posts by zstix@fosstodon.org
 (DIR) Post #AUsb8Ij9qCSiIHHqKG by zstix@fosstodon.org
       2023-04-21T14:29:05Z
       
       0 likes, 0 repeats
       
       When you're under tight deadlines (always) it's easy to slip into the mode of "this code is fine for now, we can come back to refactor". But that refactor work rarely happens.I'd like to think it's possible to work quickly without accruing a lot of tech debt, but I'm not sure how to teach folks that skill. What even is that skill? Discipline? Forethought?Whatever it is, it's likely not a hard technical skill, but an attitude. Those are hard to help people adopt.
       
 (DIR) Post #AUsb8Jo9p63Ve4dLl2 by skypage@noagendasocial.com
       2023-04-21T14:36:17Z
       
       0 likes, 0 repeats
       
       @zstixIt's a difficult balance to strike. The best I've seen done to address the issue in a corporate setting is having a dedicated part of the release cycle where addressing tech debt and refactoring makes sense and is encouraged, the earlier part where larger features are written. That way there's a good chance to shake out any bugs between addressing tech debt and other major changes
       
 (DIR) Post #AUsbQ2X8muRzHY7mJU by zstix@fosstodon.org
       2023-04-21T14:39:29Z
       
       0 likes, 0 repeats
       
       @skypage I love that idea in theory and, when I've worked at some corporate places, we had the space to do that.Some places unfortunately see that refactor time as an easy thing to cut to achieve more feature releases. Like you said tho, it's a balance.