Maybe the whole software engineering subject is rather vague in my head. What my teacher told me was that there's basically two paths: traditional software engineering and agile methods. The course I'm taking on the university is about the traditional software engineering. So I'm talking about that.
What they have presented to us thus far is a lot of documents, each with a different name. You're supposed to fill each document in each stage of development, called the iterations. The teacher even showed us a table about the software development process, and according to that table coding is only a small part of it. Frankly, I always thought coding was almost all there is.
So all that got me wondering if all that bureocracy gets used in real life. After I read "you weren't meant to have a boss" I thought all that software engineering stuff related very closely to what he describes as a consequence of big companies and lots of people working together.
What they have presented to us thus far is a lot of documents, each with a different name. You're supposed to fill each document in each stage of development, called the iterations. The teacher even showed us a table about the software development process, and according to that table coding is only a small part of it. Frankly, I always thought coding was almost all there is.
So all that got me wondering if all that bureocracy gets used in real life. After I read "you weren't meant to have a boss" I thought all that software engineering stuff related very closely to what he describes as a consequence of big companies and lots of people working together.