6 ms·
This dismissal of business requirements as not technical is very interesting. Don't you ever get business requirements that touch hundreds of existing use case
by pdhborges 4y ago
This dismissal of business requirements as not technical is very interesting.
Don't you ever get business requirements that touch hundreds of existing use cases? Or business requirements that sudenly require paying atention to concurrency in multiple parts of the code? Or business requirements that introduce processes that produce and process huge amounts of data?
- plaguepilled 4y agoBusiness requirements are absolutely crucial, but they are not in any way technical. Conflating business and technical requirements just means the business requirements are not understood correctly.
- pdhborges 4y agoI'll rephrase my point: This dismissal of business requirements as not generating technical problems big enough to require deep work is very interesting.
- TeMPOraL 4y agoI think you need to look at the whole sentence: > If it's your typical web app implementing some business requirements, then there's no deep work required - it's just talking to the requirements source and converting that into code, as per the chosen web framework. The key phrase is typical web app. The sentence isn't saying that business requirements always generate shallow work. They're saying that working on a typical web app is almost entirely shallow work.