My team has this one shared component that gets involved in like every feature’s development. This year, we’re loading like 5 different features onto it, all with different timelines, and my head’s about to explode trying to figure out how to make it all fly.
How does everyone else do their software releases? Do you freeze prod and then do one big release later? Throw everything into prod during dev, hope no one sees the unreleased stuff, and just announce it later? Or something else entirely?
Step 1 use git
Step 1.2 attempt to understand the whimsical tale the project manager sold the client on
Step 1.4 realize those dreams.
Step 2 feature freeze
Step 3 blocking issues are addressed
Step 4 QA
Step 4.2 discover what the project manager really meant, goto step 1.4.
Step 5 smoke test
Step 6 release
Step 7 goto step 1.2
Step 8 add Linux support
Step 9. Write documentation
But real programmers never do that. That code was hard to write, so it should be hard to read!
:-)
You don’t write self documenting code?
I write self documenting code, as long as you are a Python interpreter.
You are trying to kill the fun :-)
(maybe you are too young to know the C one liner’s contests?)
Warning in step 5: Magic smoke was let out of EVB on two occasions because someone forgot to check the power supply.
Error in step 8: Attempting to install Linux on target MCU overran my 300k of flash.