Gregory's ServerIf you're a decent software engineer, your assumptions will be:
- "everyone uses dialup over a shitty phone line that goes to one of those electromechanical telephone exchanges from 60s" instead of "the internet is fast enough these days"
- "everyone MAYBE has 8 GB of storage on their phone, half of which is taken by the OS" instead of "storage is cheap and 100 MB per app is okay, grow up, it's {{ current_year }}"
- "your user won't give a shit about your 'developer experience' and how 'beautiful' your code is" instead of "Kotlin and React and Electron are required, no one uses raw platform APIs/native controls/whatever anymore because it's so EASY to develop with all these new abstractions"
|
Top-level
 5 comments
[DATA EXPUNGED]
 @grishka @bouncepaw I've been saying "We don't need more powerful computers, we need more efficient software" a lot recently to #BigTech brands - it seems right to put it here too
 @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. @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. |