Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
nam178873713dSo sad but true.
I think the programming job market has changed. To make money for living you need to know those fancy tools/toys. Your resume must be filled with trendy keywords. Nobody cares about your programming/problem solving skill anymore. So sad but true.
Fast-Nop1076912dAnd then there's embedded where you still need an oscilloscope for software debugging. Looking at the disassembly is not uncommon when you want to know whether the compiler is really generating the expected code. People refrain from bloat because the next smaller chip is cheaper and needs less energy. You won't be using huge bloated libraries for anything even semi-serious because achieving code coverage during verification would be a show stopper.
Bitkris40212dI share with you the same worries but in the meanwhile I would like to ask: doesn't WebAssembly sound like a gamechanger instead?
Fast-Nop1076912d@Bitkris IMO not because WASM just means that the same bloated stuff can run somewhat faster. The dev process will not change except for a final compilation stage in release mode.
Theoretically, it could enable heavy client-side computations, but in a world where mobile internet usage has long surpassed desktop, nobody will do that because it drains the batteries.
This is what actually happens
cursee1787712dWow you said it very well. That's what I wanna say as well. But I could only say "going too fast" 😁 I'm that articulate.
Root4070110dSounds like pandering to the false god of public opinion.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job