3 ms·
Flawed feedback. I trained myself in Elixir for a few weekends and once things started to click in my head (I was always an OOP / imperative programming guy so
by pdimitar 9y ago
Flawed feedback. I trained myself in Elixir for a few weekends and once things started to click in my head (I was always an OOP / imperative programming guy so learning functional programming took me some trying) then I was able to do a mini-project that had real value... in 2 working days.
I didn't have to deal with dependencies for more than 10 seconds (not an exaggeration), I didn't have to transpile, I didn't have to include shims / polyfills, I didn't have to explicitly include 2-3 CLI "task runners", etc. weird crap from the JS ecosystem that everybody in there thinks is normal for some reason.
You can't just expect people to worship your tech stack and blame them for "not being experienced enough". Hell, if you put enough labor, you can get solid experience on a custom-tailored banking system written in COBOL, or custom-programmed FPGA CPU units. You can become an expert manual tailor, too. But that's not the point.
IMO the point is -- are you able to immerse yourself in the tech stack you're proclaiming and be useful in business terms no more than 1-2 weeks later? If no, then your stack isn't worth investing into, especially after your stack is known to change trends as if it's some kind of a glamour fashion empire.