3 ms·
Agree. The worst issue for me is how unfocused the efforts are. I experienced issues at a large media company where new features to the public site to improve
by weego 11y ago
Agree.
The worst issue for me is how unfocused the efforts are. I experienced issues at a large media company where new features to the public site to improve user experience where delayed for entire sprints because someone in the team became obsessed with the notion that their env was wrong because they were using grunt instead of gulp, or they used a particular Sass processor that relied on Ruby and they could use one that was pure JS.
I quite like writing JS and have done on and off for over 17 years, I just don't understand the constant and wilful reinvention and fragmentation in front end development.
- Klathmon 11y agoThat sounds like your developer's problem, not the technology's problem. Would you blame the language C++ if the developer was constantly compiling their own compiler from master every single day and spending hours upon hours dealing with that?
- weego 11y agoIt wasn't a single developer, it was a subset culture in the team of frontend developers. Those 2 examples were 2 different devs. I don't really get your point though. Are suggesting that JS fragments and reinvents itself outside of the will of the general populace of frontend developers? How else could the problems in frontend dev arise if not from the culture created by the people?
- deleted 11y ago[deleted]
- mtberatwork 11y agoGiven how difficult it can be to get past HR keyword filters when applying for a new job ("Oh we need a candidate with gulp experience, not grunt."), I can see how folks are fearful that they aren't using the "right" technologies. It's insanity.
- deleted 11y ago[deleted]