Software is a critical part of our lives. We all use different software tools day in and day out, but most people don’t have a good sense of how software is actually made and maintained. I thought I’d share a little bit about how our process works by walking you through what our developers are “shipping” in a typical week of work at LACRM.
really cool to see the behind the scenes on this. most software companies are a total black box so its refreshing when someone actually shows what a dev week looks like. curious whether bug fixes or new feature work takes up more of a typical week?
1 Like
On average, I’d guess that each dev spends about one day per week on bug fixes (which includes things that aren’t technically bugs, but are little tiny changes we want to make). But because all code must be reviewed by a different dev and tested before getting deployed, the bug fixes are often getting deployed days after the code has been written.
There’s probably another half-day of meetings, reviewing code from other devs, etc. So each dev probably has something like 3.5 days per week to work on their main project.
Of course, sometimes things come up (e.g. occasionally a single bug takes a full week to fix, or there’s some urgent project that jumps to the front of the line), but what I described above is pretty typical I think.