751
Real programmer test (lemy.lol)
submitted 7 months ago by to c/programmer_humor@programming.dev
35 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 22 points 7 months ago (8 children)

If it's a task that has to be done every day for 4 years, you're actually saving time. And that's if we assume only one person has to do it, if it's 10 people, you're saving time after 5-6 months. 10 minutes adds up quickly once it starts scaling.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 15 points 7 months ago (4 children)

    Assuming you set it up perfectly the first time, instead of it breaking for some reason six weeks later and then you spend three hours figuring out/remembering how you set it up in the first place and another two nights after work fixing it so it works as intended.

    Also your use case has changed, so it needs to be retooled to address the new situation.

    Other than that... worth it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 7 points 7 months ago (2 children)

    spend three hours figuring out/remembering how you set it up in the first place

    I mean, you could also leave comments in your code, but that's just me

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 7 months ago

    My comments:

    // Do not change this timeout value. There's a compatibility issue that causes requests to hang. Come back later to add details

    // Should probably refactor this bit

    // drunk, fix later

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 7 months ago*

    5 years is also a pretty arbitrary span to go with. You could smoothly discount future time savings instead, but then your discounting curve is arbitrary.

    The most rigorous way to go would be to set some kind of future goal, and then work your way backwards to find some kind of statistical description of the shortest path there, or else set some kind of future metric at a specific time and find the path that maximises it. This is pretty much how you design your investing portfolio, just with money instead of labour.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 7 months ago

    Came here to say that. I'd rather spend 4 days automating my local development environment than spend half an hour every time figuring out why my deps are mismatched, or what is the correct env var to put over there.

    If everyone on the team wastes 10 minutes on random BS every day, it is thousands of money compounding over months.

  • permalink
  • fedilink
  • source
  • parent