4 ms·
It's interesting how these have held up: Do you use source control? Source control is much more common now than in 2000. I worked many years as a software d
by l0b0 6y ago
It's interesting how these have held up:
Do you use source control?
Source control is much more common now than in 2000. I worked many years as a software developer before encountering any team which used version control as a matter of course. Before crapping on those developers, consider that version control before DVCSes like Git was slow, broke frequently, took up valuable storage space, and usually required a server which was non-trivial to set up and maintain.
Do you make daily builds?
Not so relevant now that we can build on every commit for free.
Do you have an up-to-date schedule?
Not sure what to make of this. Software development is as difficult as ever to estimate.
Do you have a spec?
Not unless I'm implementing an ISO standard or something. Sounds a lot like waterfall.
Do programmers have quiet working conditions?
Haha, nope! Dilbertian low walls have completely taken over.
Do you use the best tools money can buy?
Depends where you work, but most places have onerous acquisition processes.
Do you have testers?
Only in big projects, where this seems pretty ubiquitous.
Do new candidates write code during their interview?
Still relevant in lots of companies.
Do you do hallway usability testing?
Did this one actually ever catch on anywhere except single-product shops?
Can you make a build in one step?
Do you fix bugs before writing new code?
Do you have a bug database?
Still super relevant.
- SAI_Peregrinus 6y agoHaving a spec isn't waterfall at all. A spec is just deciding on what to build before building, it answers the question of "what user visible features are required?" Agile calls specs Design Docs, and generates them from User Stories.