I think that my point is exactly in line. This line from Wikipedia:
>> "The Bible of Software Engineering", because "everybody quotes it, some people read it, and a few people go by it"
Exactly my point; everyone will complain about complexity being the biggest problem in software development (everyone agrees about this); and yet these same people will keep making decisions that will increase complexity within their own projects (for example):
- To use Jira instead of Trello.
- TypeScript instead of JavaScript.
- 100% code coverage in tests instead of well targeted integration/functional tests.
- Hire more people instead of focusing on improving internal practices and coding style.
I have years of commercial experience in both JavaScript and TypeScript as a developers and yes TypeScript adds a lot of complexity over JavaScript.
I've worked for at least one company that had 100% unit AND integration test coverage of every line of code across all projects. It took about 3 days for an engineer to rename a single property in one of the API endpoints because of the time it took to get all the tests passing again. Most of them were useless and added no value to the project.
>> "The Bible of Software Engineering", because "everybody quotes it, some people read it, and a few people go by it"
Exactly my point; everyone will complain about complexity being the biggest problem in software development (everyone agrees about this); and yet these same people will keep making decisions that will increase complexity within their own projects (for example):
- To use Jira instead of Trello.
- TypeScript instead of JavaScript.
- 100% code coverage in tests instead of well targeted integration/functional tests.
- Hire more people instead of focusing on improving internal practices and coding style.