Our families think we do magic and our bosses think we're capable of doing (most) anything. When shit goes south, we tend to get fired, not sued. Fired in an industry where jobs are relatively easy to find with higher than average salaries.

There's no licensure for what we do. You have to go to med school to be a doctor. You have to go to law school to be an attorney. You don't even have to have a DEGREE to get many coding jobs, even if the work risks real human lives. How good that is for society is up for debate. I flip-flop on this. If we make a huge mistake like blowing away a prod database, we're not banned from practicing again.

When the public is out for blood for something a business does, the media doesn't automatically paint a bullseye on developers. The public is not asking to raise the barrier to entry for our jobs, even though there's so many reasons people could make up to argue that a government should regulate us.

I'm just saying that out of all the things we could complain about, there's a lot we should be thankful for. Some would even say we've got it made.

  • 4
    *angry face* ...fair though. We aren’t held to account for most of our screwups.
  • 5
    @broseph I think we are, just not with the level of punitive ire we'd see for other disciplines. I'd much rather be fired and do something else than get stripped of credentials and end up forced to retire in shame.
  • 1
    @zyrolasting i'm guessing you haven't been keeping up with the news lately. Those required regs and licenses are on their way, along with all the bureaucracy and expense to go with them.

    The only question remaining is whether it's really security they're worried about or is it just that certain parties are upset that the cookie jar doesn't have an opening large enough for them to fit their greedy, grubby paws in 🤔
  • 2
    This is tricky. I'm all for accountability, but what we do is inherently problematic and rarely done in a vacuum.

    I recently worked for a team where I was forced to modify some really messy code that maintained state in unusual ways, and the class did too many things. I wasn't allowed to clean that up. It's the sort of thing where I would tell anyone, "Don't do this - it's confusing and makes defects more likely."

    I unit tested my code, but it went to production without any load testing, had some ugly impact, and had to be rolled back.

    Despite all of the circumstances, I hate what happened because it was my code. At the same time, I never would have written something that made such a defect easy to introduce, and I would have fixed it if I could.

    I feel accountable, but at the same time I realize that we just have to live with it. If no one points fingers, I don't point fingers.
  • 1
    Interesting point of view. Never thought about it that way.
  • 0
  • 1
    @zyrolasting just goin on intuition mostly. I started working on an idea for a cooperative labor network a year or two ago for the same reasons you just mentioned and at some point it occurred to me that the govt should cut the shit and set up a similar thing so I started putting all the pieces together as to why they haven't as I went along.

    These new "security" issues with the big companies that everyone uses is just the tip of whats to come. To put it simply, software is where the automotive was back in the 40's and 50's when you could still feasibly stand a chance at forming your on car company.

    We're now entering the 60's and 70's, when all the small automakers got choked out by regulations and had no choice but to sell to the likes of Ford, Gm, Dodge...

    Or in this case most Fb, google, Ms, apple, etc. Eventually even linux will be forced to run solely with their propr. distros b/c the liability would be too much for them to stay attached to the open source comm.
Your Job Suck?
Get a Better Job
Add Comment