Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
Things like Svelte give me hope, it's cool to see framework-neutral methods of creating web components! It's a nice compromise between doing everything vanillaJS and the monolithic frameworks. It irritates me how many jobs expect experience with a library versus a concept or language. People can learn Rails without getting too deep into what an incredible language Ruby is, people can learn React and let create-react-app prevent them from having to learn how everything comes together under the covers, and we can always find abstractions to distance us from learning the finer details.
It's like the whole concept of DevOps. What do you mean you want a DevOps engineer? Do you want a build automation engineer? A sysadmin who is really good at automating things? An engineer who understands non-functional requirements? An unrealistic jack-of-all-trades who will save your broken "agile" process?
I feel like the focus on tools just creates silos within the company. It takes away opportunities to hire staff members who can bring new viewpoints to the table, who can question why things are done a certain way, and suggest better alternatives.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Things like Svelte give me hope, it's cool to see framework-neutral methods of creating web components! It's a nice compromise between doing everything vanillaJS and the monolithic frameworks. It irritates me how many jobs expect experience with a library versus a concept or language. People can learn Rails without getting too deep into what an incredible language Ruby is, people can learn React and let create-react-app prevent them from having to learn how everything comes together under the covers, and we can always find abstractions to distance us from learning the finer details.
It's like the whole concept of DevOps. What do you mean you want a DevOps engineer? Do you want a build automation engineer? A sysadmin who is really good at automating things? An engineer who understands non-functional requirements? An unrealistic jack-of-all-trades who will save your broken "agile" process?
I feel like the focus on tools just creates silos within the company. It takes away opportunities to hire staff members who can bring new viewpoints to the table, who can question why things are done a certain way, and suggest better alternatives.