898
As someone not in tech, I have no idea how to refer to my tech friends' jobs (lemmy.world)
submitted 2 years ago by to c/programmer_humor@programming.dev
340 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 25 points 2 years ago (1 child)

Depends. I've studied for my engineering title, I have standards and ethics. Requirements, specification, design, architecture, programming, testing, integration, delivery, everything is part of my job. If you are a programmer, you only do programming.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -3 points 2 years ago (2 children)

    Yeah, that's bullshit.

    Look at the state of software in the world. Even for Boeing standards, most software is abysmal. You can have personal standards all you want, if business daddy wants to deliver untested crap, I might object, but I can't stop it and it's usually not a hill I would want to die on.

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

    I might object, but I can’t stop it

    I'd argue that if you seriously consider yourself a software engineer, and you take the "engineer" part seriously, you should be quitting and blowing the whistle if that happens. If you just go along with it, then sure, you're not an engineer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 years ago

    Dude, you're living in fantasy land if you're being serious. Engineers build all types of shoddy and dangerous crap just because they're being paid to do it. Most of weapons manufacturing is mech eng. Almost no one is gonna quit their job over some ethical dispute, even if it's costing lives.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago

    Sure, and go where else exactly?

    The entire industry works on shipping duct taped products.

    I do have my standards, but there's a point at which you have to say "it's good enough". If someone's at risk of dying or being harmed, yeah, that's a real problem. If the application keeps crashing and loses the business money, that's not my problem, I can only notify my superiors about my concerns.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 2 years ago* (1 child)

    That's why I said it depends. If a billion dollar company decides to cut costs even more to gain more and more profits, they hire an army of codemonkeys in India and that is what you get.

    If you work at a mid sized company interested in sustainable growth, you might get a software engineering position where you are the business daddy and if you say "I won't deliver that untested" then it won't be delivered untested.

    I'm working at a company in Germany and we are leading in our field. I have one boss and he listens to what I tell him because he doesn't have a clue about software engineering and that's what he hired me and my team for.

    Look into Agile, servant leadership and new work (the real stuff and not the garbage "hip" companies want to make you believe) if you want to understand.

    It's the old principles that kill companies like Boeing, because they think they can make big profits like it's 1984 solely by pumping money into an army of wage slaves.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago

    Look into "how a company works", because that directly works against anything you say.

    Not that I disagree with your ambition, I would like to only ship tested code. But if you're working with deadlines and fixed budgets, that's often enough impossible. I can't even get a proper specification out of my clients, and even if they do, it'll change in a week. You can be as agile as you want, if money runs out, there's not much you can do.

  • permalink
  • fedilink
  • source
  • parent