• ramirezmike@programming.dev
    link
    fedilink
    arrow-up
    76
    ·
    edit-2
    2 months ago

    the term normally refers to a developer that can be productive in every layer required for a typical application to work.

    They can do the front end design/styling/implementation and are familiar with front end languages and frameworks

    They can do the backend API design and are familiar with the typical backend languages and patterns.

    They can do the database table design, write and optimize queries.

    They can handle the ci/cd scripting that handles building and deploying the application

    They can design and write the automation tests and are familiar with the libraries used for that.

    And a bunch of other crap like load testing or familiarity with cloud services.

    The latest thing added to the list is AI model creation which is a nightmare… but, I can’t say no 🤷‍♂️

    • frezik
      link
      fedilink
      arrow-up
      72
      ·
      edit-2
      2 months ago

      Also, in practice, they’re usually only good at one or two of the things on the list (at best) and hack their way through the rest. As much as people make fun of overspecialization, it happens in every field for a reason.

          • frezik
            link
            fedilink
            arrow-up
            6
            ·
            2 months ago

            I have seen SQL written by professional Oracle DBAs. What I learned is that I do not want to look at SQL written by professional Oracle DBAs.

      • _____@lemm.ee
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 months ago

        Eh, not sure if this is true at all. I think the reality is that niche specialized roles are valuable (frontend expert) but you are not “hacking” your way in full stack unless you are a junior or just bad at development.

        I don’t consider myself to be hacking anything I do, even things I’m not as strong in (ci cd) I pay full attention to documentation and examples before blinding coding or writing ci scripts

    • Rusty Shackleford@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      Start saying no. If you don’t know how, start learning. It’s hurting everyone up and down the industry.

      I am almost purely focussed on creating DNNs (“deep neural networks” for the unaware) and it’s almost always a nightmare work-wise, even without all the rest of the other crap.

    • stebo@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      2 months ago

      The latest thing added to the list is AI model creation which is a nightmare… but, I can’t say no 🤷‍♂️

      That’s funny, I’m working with AI models for my thesis. Good to know that professional programmers struggle with it too.