2 ms·

When shopping for a hammer I don’t look for the most hyped up well marketed one. I pick something that will do the job correctly. Part of the saturation levels

When shopping for a hammer I don’t look for the most hyped up well marketed one. I pick something that will do the job correctly. Part of the saturation levels of tooling has to do with the job market. Potential employers put in the latest tooling meaning prospects then have to learn it in a hurry or be left behind. Don’t follow the hype. A good craftsperson never blames their tools.

tbrownaw 4y ago
> A good craftsperson never blames their tools. But isn't this because they supposedly know which tools to use, and have the agency to choose? I'm not sure it quite applies to cases where you're a small fish and all the employers are bandwagonning on some tool that you don't agree is any good.
- sacrosanct 4y ago
  I’m referring to the fact that employers sometimes lazily include certain requirements that are overkill for the task at hand and largely unwarranted. Do I need $trendyBuildTool when the project is five files with 100 lines of code that I can easily deploy without using such superfluous tooling? I should get to pick my tooling yet also have baseline knowledge of HTML, JS, & CSS. Learning a toolset just because it’s trendy and hyped up is backwards and doesn’t take into account that most projects will never be amazing Crystal Palaces or large abstractions.
yetanother12345 4y ago
> Part of the saturation levels of tooling has to do with the job market. .. but it works like this: You have this thing that you can use for all kinds of purposes, called ECMA Script, or JS. As marketing people say, it "adds value to the product" Problem with it (the JS) is that it is really easy to get started with it. So, the people that have spent years developing these fancy (value add) "solutions" rightfully fear for their job security, as: - when the time comes that they should demand a raise, the manager might rightfully reason that the added cost isn't worth it as they could just train a college grad for the job much cheaper. So, what do they (experienced devs in big corps) do? They build "Barriers To Entry" so called: Teh Frrrrrameworkz! ta-daa Invent convoluted layers upon layers on top of this very simple yet efficient thing, JS -- layers that grow so complicated that they require significantly more study and practice to master than the very simple tool (JS) that anyone can learn to solve very basic tasks with in an hour. That way they make "development" a bureaucratic standardized hell of a process in stead of just "getting things done", and the effect is that they increase their own job security. ...and you can still accomplish the same things in vanilla JS, only these "developers" (now as senior as to being the ones doing the employment interviews) spend great effort trying to convince every new/potential colleague that you can't. End result: all teh Interwebs filled with "spinners" and lazyload and much other user-hostile stuff built to satisfy automated testing, search engines and whatnot - not users. Very little that "just works" ... and a totally recalibrated job market, introducing roles/functions such as DevOps and much other nonsese like it.

tbrownaw 4y ago

> A good craftsperson never blames their tools. But isn't this because they supposedly know which tools to use, and have the agency to choose? I'm not sure it quite applies to cases where you're a small fish and all the employers are bandwagonning on some tool that you don't agree is any good.

sacrosanct 4y ago
I’m referring to the fact that employers sometimes lazily include certain requirements that are overkill for the task at hand and largely unwarranted. Do I need $trendyBuildTool when the project is five files with 100 lines of code that I can easily deploy without using such superfluous tooling? I should get to pick my tooling yet also have baseline knowledge of HTML, JS, & CSS. Learning a toolset just because it’s trendy and hyped up is backwards and doesn’t take into account that most projects will never be amazing Crystal Palaces or large abstractions.

yetanother12345 4y ago

> Part of the saturation levels of tooling has to do with the job market. .. but it works like this: You have this thing that you can use for all kinds of purposes, called ECMA Script, or JS. As marketing people say, it "adds value to the product" Problem with it (the JS) is that it is really easy to get started with it. So, the people that have spent years developing these fancy (value add) "solutions" rightfully fear for their job security, as: - when the time comes that they should demand a raise, the manager might rightfully reason that the added cost isn't worth it as they could just train a college grad for the job much cheaper. So, what do they (experienced devs in big corps) do? They build "Barriers To Entry" so called: Teh Frrrrrameworkz! ta-daa Invent convoluted layers upon layers on top of this very simple yet efficient thing, JS -- layers that grow so complicated that they require significantly more study and practice to master than the very simple tool (JS) that anyone can learn to solve very basic tasks with in an hour. That way they make "development" a bureaucratic standardized hell of a process in stead of just "getting things done", and the effect is that they increase their own job security. ...and you can still accomplish the same things in vanilla JS, only these "developers" (now as senior as to being the ones doing the employment interviews) spend great effort trying to convince every new/potential colleague that you can't. End result: all teh Interwebs filled with "spinners" and lazyload and much other user-hostile stuff built to satisfy automated testing, search engines and whatnot - not users. Very little that "just works" ... and a totally recalibrated job market, introducing roles/functions such as DevOps and much other nonsese like it.