4 ms·

> Meanwhile the guys who were doing all the new stuff, sucked at trying to juggle 12 things because it looked good on a resume. This isn't helped by the curren

by sli 6y ago

> Meanwhile the guys who were doing all the new stuff, sucked at trying to juggle 12 things because it looked good on a resume. This isn't helped by the current trend of trying to hire mostly fullstack developers, also known as hiring one person to do the job of three people. It does almost nothing but incentivize packing resumes to hopefully make the cut and burn people out from switching modes.

watwut 6y ago
Fullstack does not mean that you will burn out. Fullstack can mean 40 hours a week, never overtime. Also, for smaller apps, after you had at least few months of experience with all technologies, it is not difficult to switch modes. People who specialize will be better at their specialization, but you will be good enough for majority of apps.
- lolive 6y ago
  The JavaScript fatigue is NOT a myth. [and CSS/layout is really tough, too]
  - marcosdumay 6y ago
    All of that applies to frontend development too. At the end of the day, some people like Javascrip and CSS. And "full stack" only means that they will work with those, SQL, and some backend language (that may be Javascript too). It doesn't imply anything on the workload, all it does imply is that the place is hiring a generalist instead of specialists.
    - lolive 6y ago
      The last job offer that made me smile was for an AI / fullstack developper. Aka the platypus of software dev. The problem is pretty simple. Let's say you are cutting-edge in all the technologies that make you very adaptable at time T. You get hired. You decide a stack A/B/C/... for your next project. You get stuck in that project for ... let's say 3 years. (a reasonable time for a project to reach production and have a few real-life iterations). If you are not an assh... who leaves after 2 years (leaving the production/maintenance to others, i.e never having lived the "hell" of maintaining things for real), then you are 3 years-behind in all the technologies that are not in the A/B/C/... stack. Now, at time T+3, you are ... the obsolete man [for TTZ fans only :)]
    - lolive 6y ago
      Frontend has very few to do with HTML and CSS nowadays. It all has to do with framework choice, the build toolchain, the unit-testing of the front, the server-side rendering vs the client-side, the architectural layers (or bricks) to use on the client-side, SEO, performance, CI/CD, browser compatibility, components lifecycle (yumm, library versions upgrade!).

by sli 6y ago

watwut 6y ago

Fullstack does not mean that you will burn out. Fullstack can mean 40 hours a week, never overtime. Also, for smaller apps, after you had at least few months of experience with all technologies, it is not difficult to switch modes. People who specialize will be better at their specialization, but you will be good enough for majority of apps.

lolive 6y ago
The JavaScript fatigue is NOT a myth. [and CSS/layout is really tough, too]
- marcosdumay 6y ago
  All of that applies to frontend development too. At the end of the day, some people like Javascrip and CSS. And "full stack" only means that they will work with those, SQL, and some backend language (that may be Javascript too). It doesn't imply anything on the workload, all it does imply is that the place is hiring a generalist instead of specialists.
  - lolive 6y ago
    The last job offer that made me smile was for an AI / fullstack developper. Aka the platypus of software dev. The problem is pretty simple. Let's say you are cutting-edge in all the technologies that make you very adaptable at time T. You get hired. You decide a stack A/B/C/... for your next project. You get stuck in that project for ... let's say 3 years. (a reasonable time for a project to reach production and have a few real-life iterations). If you are not an assh... who leaves after 2 years (leaving the production/maintenance to others, i.e never having lived the "hell" of maintaining things for real), then you are 3 years-behind in all the technologies that are not in the A/B/C/... stack. Now, at time T+3, you are ... the obsolete man [for TTZ fans only :)]
  - lolive 6y ago
    Frontend has very few to do with HTML and CSS nowadays. It all has to do with framework choice, the build toolchain, the unit-testing of the front, the server-side rendering vs the client-side, the architectural layers (or bricks) to use on the client-side, SEO, performance, CI/CD, browser compatibility, components lifecycle (yumm, library versions upgrade!).