▲ 442 ▼ A ‘demoralizing' trend has computer science grads out of work — even minimum wage jobs. Are 6-figure tech careers over? (www.yahoo.com) submitted 1 year ago by chobeat@lemmy.ml to c/technology@lemmy.world 197 comments fedilink hide all child comments
[–] sobchak@programming.dev 5 points 1 year ago (6 children) If their work brings in > 100k in revenue then they should. permalink fedilink source parent hideshow 6 child comments replies: [+] GreenKnight23@lemmy.world -10 points 1 year ago (5 children) 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? permalink fedilink source parent hideshow 5 child comments replies: [–] KumaLumaJuma@feddit.uk 7 points 1 year ago keep in mind, you fuck up a steak at a cooking job you're out the cost of the meal + time. What? Where? permalink fedilink source parent [–] chilicheeselies@lemmy.world 8 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you understand how that proves my point, right? permalink fedilink source parent [–] sobchak@programming.dev 4 points 1 year ago (1 child) 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). permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you're almost there... permalink fedilink source parent
[+] GreenKnight23@lemmy.world -10 points 1 year ago (5 children) 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? permalink fedilink source parent hideshow 5 child comments replies: [–] KumaLumaJuma@feddit.uk 7 points 1 year ago keep in mind, you fuck up a steak at a cooking job you're out the cost of the meal + time. What? Where? permalink fedilink source parent [–] chilicheeselies@lemmy.world 8 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you understand how that proves my point, right? permalink fedilink source parent [–] sobchak@programming.dev 4 points 1 year ago (1 child) 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). permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you're almost there... permalink fedilink source parent
[–] KumaLumaJuma@feddit.uk 7 points 1 year ago keep in mind, you fuck up a steak at a cooking job you're out the cost of the meal + time. What? Where? permalink fedilink source parent
[–] chilicheeselies@lemmy.world 8 points 1 year ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you understand how that proves my point, right? permalink fedilink source parent
[–] GreenKnight23@lemmy.world -3 points 1 year ago you understand how that proves my point, right? permalink fedilink source parent
[–] sobchak@programming.dev 4 points 1 year ago (1 child) 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). permalink fedilink source parent hideshow 1 child comment replies: [–] GreenKnight23@lemmy.world -3 points 1 year ago you're almost there... permalink fedilink source parent
[–] GreenKnight23@lemmy.world -3 points 1 year ago you're almost there... permalink fedilink source parent