2 ms·
I took a job once where they: 1. Had no bug tracking 2. Had no source control (the official code was whatever was on one of the engineer's laptops) 3. Had no
by ryandrake 10y ago
I took a job once where they:
1. Had no bug tracking
2. Had no source control (the official code was whatever was on one of the engineer's laptops)
3. Had no dedicated build machines (builds were done on that engineer's laptop)
4. Had no release process (build that went out was--you guessed it--copied from that engineer's laptop to a CD)
5. Had no formal QA
6. Had no documentation (either comments in the code, a spec, or a user manual)
7. Had no project management or roadmap planning (the CEO would just drop in and said we should do XYZ, and then a few weeks later "is it done yet?")
They thought their software problem was just that they didn't have enough smart engineers. Yea. You have to ask about these basic "hygiene" things.
- js2 10y agoOTOH, if you enjoy being a jack-of-all-trades, look at all the value you can add right out of the gate.
- ryandrake 10y agoDefinitely. The job was a terrific learning experience, and I've never had to wear as many hats as I did there. It was excellent experience and I saw it as a once-in-a-lifetime turnaround opportunity. The point is, you need to ask about the basics so you understand what you're getting into.
- wheresvic1 10y agoI think that it's the attitude of the people whom you would be working with which matters the most in this scenario. If they were not open to change and improvement then you would be stuck burning CDs as well!