• GreenKnight23@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    11
    ·
    10 hours ago

    you’re ignoring the $2,000,000 in training costs from sr devs and mistakes.

    if you want to get serious about cost effectiveness, Jr devs should pay to work at a job.

    keep in mind, you fuck up a steak at a cooking job you’re out the cost of the meal + time.

    you fuck up a DB after a schema change you’re out thousands if not millions of dollars in outages, SLAs, and sales.

    still want to use revenue as a compensation performance metric?

    • KumaLumaJuma@feddit.uk
      link
      fedilink
      English
      arrow-up
      6
      ·
      10 hours ago

      keep in mind, you fuck up a steak at a cooking job you’re out the cost of the meal + time.

      What? Where?

    • chilicheeselies@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      10 hours ago

      To be fair, if a jr dev has enough acesss to screw a prod db from a schena update, then the issue is with the seniors and managers who did not set up the appropriate guard rails to prevent that.

    • sobchak@programming.dev
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      Idk, I’ve worked with recent grads where their work likely did bring in > $100k in a year. Maybe only took a month to get up to speed. Commits from all devs should be reviewed, and all code should be tested before pushing to prod, so those catastrophic costs should rarely be a problem. We had a good relationship with professors at a local university, and they’d send us their top students. The students would work with us for a while before usually getting picked up by big tech.

      Pretty sure my work right out of college brought the company around $300k the first year (wrote the firmware for an electronic control board mostly by myself, which allowed the company to secure a large contract).