by notoriousarun on 7/3/21, 11:01 AM with 11 comments
by Swizec on 7/4/21, 9:29 PM
You can work around everything else. Prioritize speed or stability, use different standards for different areas, even any number of project management methodologies. A group of talented folks with a goal can make anything work.
But when you’re out of ideas, that’s when shipping dies. Your engineering department devolves into a pile of factorings and refactorings and turd polishing projects and academic exercises and none of it drives the business forward. It’s just busywork because engineers are expensive.
And trust me, they’re gonna get tired of the busywork and they will leave. You’ll get tired of paying them for busywork too.
by dirtyaura on 7/4/21, 9:23 PM
In our case, we have this situation with SW vs HW shipping culture. On the SW side, we focus on continuously developing features and have deliberately emphasized productivity over schedule-predictability, while on the HW side they naturally are focused more on schedule-predictability due to complex dependencies.
Now, this dichotomy has created an interesting discussions inside the company on the right way to ship products and projects, and to me, arguments mainly come from the fact that people come from the different shipping culture and have hard time to see the benefits and requirements of the other culture.
by catwind7 on 7/5/21, 4:20 AM