Gregory's Server@grishka @bouncepaw common is the engineer that thinks this way, rare is the project manager. the majority of developers are not hostile to actual use-cases, it is the budgets, both money and time, that don't care.
|
2 comments
voxel
@grishka @bouncepaw that's a great example of someone lacking basic domain knowledge. But there are also good engineers who work within business constraints and implement the kind of inefficiencies you talk about because the business won't allocate enough development time for a better solution. The reason for so many places using huge bloat.js libraries is they're faster, cheaper, flashier than bespoke solutions. |
voxel, actually no. A good engineer knows how to get the job done within given constraints. Knowing your own limits, and limits of the technologies you're using, is an indispensable part of engineering. The IT industry, however, thinks that it's absolutely fine to hire hundreds of junior developers who have no idea what they're doing, and put them in charge of critical decisions.
I know a guy who learned React but didn't learn JS. I built the backend for a simple app he had an idea for, he did the frontend. I had to explain him what XMLHttpRequest is, then watched him repeatedly try and fail to compose a valid URL with required parameters as the thing ran on my laptop through ngrok.
voxel, actually no. A good engineer knows how to get the job done within given constraints. Knowing your own limits, and limits of the technologies you're using, is an indispensable part of engineering. The IT industry, however, thinks that it's absolutely fine to hire hundreds of junior developers who have no idea what they're doing, and put them in charge of critical decisions.