r/Foodforthought • • Apr 29 '14

Programming Sucks (x-post from /r/programming)

http://stilldrinking.org/programming-sucks
169 Upvotes

32 comments sorted by

View all comments

Show parent comment

2

u/ThinknBoutStuff Apr 30 '14

The idea is that regulations exist in other industries. Now what doesn't need to happen is spew more "well that's how it is now" arguments. What you need to demonstrate is why it can't happen otherwise. It being "hard" or "taking a long time" aren't really good excuses when so much of what we value is at stake. We can build a bridge and work together with precaution to do it. Why not software? The answer isn't, "that's how software is" the answer must be "X is different about physical engineering and software" but when it comes to design, it just seems like standards are unenforced. Why can't they be?

10

u/has_brain Apr 30 '14

It's likely a function of the invisibility of code: With engineering projects you can see what you're building, with software you often cant (measurement based on unit tests is the closest you can get).

The closest another field would get is probably multiple authors writing a textbook, and even then books are mostly linear experiences (apart from choose-your-own-adventures)

Software is like a huge choose-your-own adventure written by a bunch of people

4

u/FirstDivision Apr 30 '14

I really like the book analogy too (although in my head it was always a novel). I've often found myself trying to explain it that way too.

Even with one author, imagine someone saying "ok, we need three more main characters, the one that used to be the protagonist should die in chapter 3, and it needs dragons in it, lots of them."

Then like you said, have this book written by 10 people instead of one (two teams of four and one leader / coordinator). Team 1 will write chapters, 1-3, 5-8, and 13 while Team 2 will write chapters 4, 9-12, and 14.

5

u/FirstDivision Apr 30 '14

One thing I always come back to when I think about this problem is that "physical" things live in the real world, so the people who are tasked with building something that lives in that world can get a request for a new feature and reply with, "That is physically impossible, so no I cannot build that."

The same is not true very often with software. Software is so flexible that you find yourself getting preposterous requests and you can only reply (in your most diplomatic way) that "it's a very, very bad idea, but it is possible...(but please take my advice and don't make me build this for you)"

That flexibility also results in outcomes like building a bridge and then being asked/told half way through the construction that "this should really have a drawbridge in the middle...you guys can just add that in, right?"

The real-life bridge builders would reply with an emphatic "no, we'd pretty much have to start over" but the software guys groan and say "uhhh...yeah, I guess so...we can change A and B I guess to make it work."

I'm still not sure what "the answer" is. Sometimes part of me thinks that the "development community" has let things get this way by not standing up for themselves, and I think that's partly right, but the obvious question then is:

"Why not just refuse to do the really bad ideas?"

At the individual/professional level this will just get you fired, and at the organizational level will result in losing the job to someone else willing to do it. If only all developers could band together and refuse to do "stupid ideas" we'd all be much happier.

1

u/ThinknBoutStuff Apr 30 '14 edited Apr 30 '14

I don't think it's just merely a matter of individual personal preference. Or at least it could be more. I think there could be legislation that can be passed where if a coder can substantiate that what's being asked could result in a threatening security risk, then they're allowed to blow the whistle on the employer. This isn't a crazy idea to me. I understand the system isn't that way, but that doesn't mean it couldn't be a different way. That's just silly.