4 ms·
In 'the olden days' programming projects were batch processing jobs on mainframes and had simple requirements, simple processes and easily predictable fail cond
by thedevindevops 6y ago
In 'the olden days' programming projects were batch processing jobs on mainframes and had simple requirements, simple processes and easily predictable fail conditions.
Nowadays the all-singing, all-dancing one-stop-shop that has become the user's expectation has pages and pages of requirements, complex processes and fail conditions that could not only fill several books but are dependent on a whole host of other systems.
In short, it's user expectations (which ironically is the same reason it's more expensive to make a movie these days)
- thorin 6y agoDon't worry, most projects in the olden days were over budget and time too. The business normally manage to make things complicated enough to overrun the schedule. I'm only able to go back about 30 years but Fred Brooks seemed to agree. What we don't have these days is large teams of career programmers that have worked on the same systems and technologies within the same business or industry for 10+ years, often supported by business people with the same experience. This makes us more susceptible to consultants, marketing and technology fads.