• invertedspear@lemm.ee
    6·
    7 months ago

    As a fullstack developer I don’t appreciate you calling me out like this. Write an efficient SQL query you framework monkeys.

    But also, this is very true.

  • Dr. Wesker@lemmy.sdf.orgEnglish
    3·
    7 months ago

    I can’t be the only person who thinks “full stack” translates to “master of nothing.” One of the best career moves I ever made was shrug off the pressure to go full stack, and dedicate myself to backend only.

    • Fal@yiffit.netEnglish
      01·
      7 months ago

      I think knowing about frontend is important for a senior or higher level engineer. I would expect someone at that level to be able to contribute where necessary, and know enough to make sane decisions and know when those decisions impact backend/frontend. But to be equally good at both isn’t reasonable

  • RonSijm@programming.dev
    2·
    7 months ago

    Backend Requirements: “When x,y goes in, I want x+y to come out!” - Okay

    Frontend Requirements: “Well it needs to be more user-friendly, and have this rockstar wow effect” - Yea wtf are you even talking about? You want me to add random glitter explosions, because I found a script for that, that’s pretty ‘wow effect’ right?

    • azertyfun@sh.itjust.works
      1·
      7 months ago

      Real back-end requirements: when x, y goes in (in JSON-as-an-XML-CDATA-block because historical reasons), I want you to output x+y+z+æ+the proof to P=NP.

      æ will require you yo compile x+y in CSV, email it to Jenny, who will email back the answer. She doesn’t quite know how to export excel sheets though so you’d better build a robust validator. No, we don’t know what æ is supposed to look like, Rob from Frontend knows but he’s on vacation for the next 8 months.

      The request must be processed under 100 ms as the frontend team won’t be able to prioritize asynchronous loading for another 10 sprints and we don’t want the webpage to freeze.

      And why does your API return a 400 when I send a picture of my feet? Please fix urgently, these errors are polluting my monitoring dashboard and we have KPIs on monitoring alerts.

  • frezik@midwest.social
    1·
    7 months ago

    Most disciplines get more specialized as they evolve. Full Stack goes against that trend, and this meme points at the problem with that. I don’t think it’s going to last.

  • Sickday@kbin.run
    1·
    7 months ago

    In my experience, that bottom image is equally applicable when Front End devs go Full Stack lol

  • ipkpjersi@lemmy.ml
    1·
    7 months ago

    As a full stack developer (more experienced in back end) working on a full stack task at work I can confirm, yes, this is very true lmao.

  • Saledovil@sh.itjust.works
    0·
    7 months ago

    If you hear ‘full stack’, run.

    What I was told by a fellow student, while I was writing my thesis (paraphrased).

    • Dr. Wesker@lemmy.sdf.orgEnglish
      1·
      7 months ago

      It may suggest the company doesn’t want to hire the appropriate amount of engineers, with the appropriate expertise, and instead want a mule. It also may suggest that product quality is a low priority.

      • KeriKitty (They(/It))@pawb.socialEnglish
        1·
        7 months ago

        Came here to ask if I’m the only one grossed out by the term “full stack” and its exploitative implications. Thanks for explaining why :3

        Hey, maybe they make up the difference in “exposure” or something! That’s a well-loved way to ask for free/underpaid work!

  • hector@sh.itjust.works
    0·
    7 months ago

    Guys I can’t do front-end! There was a time I was getting kinda good but now there’s too much CSS tricks to learn.

    I’m currently making an app for the fediverse and my back-end is amazing but I need help even beginning to make something decent for the front-end!

    This is a streaming app, and just developed the chat widget which looks good in OBS, that’s a start.

    But the player? Responsible layout? Aaaah it seems impossible.

    • frezik@midwest.social
      0·
      7 months ago

      It’d help if the JavaScript ecosystem could pause on inventing new frameworks every five minutes and instead focus on fixing their tooling problems.