undefined | Better HN

0 pointsryandrake4y ago0 comments

I once worked at a place on the opposite side of the "process" spectrum:

No source control

No bug tracker

No formal QA

No versioning or release process. When a customer needed a build they just took whatever happened to be on the lead developer's PC at the time.

No roadmap planning process. The CEO would walk into your office and spout off about some idea for the product, and that's what you'd be working on next.

And I can assure you the did not do agile or scrum. Wasn't a really great place to work. Very chaotic and everything was a fire to put out. Lots of turnover and burnout too. Would not recommend. There's a sweet spot in the middle of the 'process' spectrum.

0 comments

topkai224y ago

I interned in the software process group for a defense company building sattelites. It had the other extreme of the process spectrum- true waterfall/CMMI processes in place, but they were so painful that people just did work and then figured out how to claim they followed the process afterwards. They actually had a couple good processes that I walked away with (different levels of formality for code reviews, structured and a risk based QA processes), but overall it was about frustration and a molasses like movement. I was glad to end up on consumer software for a while after college.

j / k navigate · click thread line to collapse