Why does programming suck?
medium.com
Why does programming suck?
1–10 of 90 posts
Re: Why does programming suck?
#2Very interesting thoughts about this. I wouldn't think programming sucks, until you think about how it could be in an ideal world.
I'd love to see a follow-up article about what the OP thinks about that question.
Re: Why does programming suck?
#3Re: Why does programming suck?
#4Programming sucks if you're not interested in programming.
There's so much creativity one can put into programming. Especially when programming for oneself and not for Super Evil MegaCorp (not the actual game dev company [0]!). Sometimes it feels to me like art, for example when creating games.
My older brother, at some point in his live, he thought programming sucked as well. But then he stopped doing programming professionally and now just as a hobby and it became fun for him once again.
I will read the article later today :)
---
Re: Why does programming suck?
#5* There is always a deadline and pressure to deliver that exceeds quality controls. * Software development shifted from engineering to crafting a long time ago, mostly because of the prior pressure to deliver. * Poorer quality code that works and building new features on top are easier to sell, than rewrites and paying off technical dept.
I think it comes down to building in pieces that you don't mind throwing away when a better piece comes along.
Re: Why does programming suck?
#6Programming sucks if you're not interested in programming.
* costs and time, difficult to maintain
* difficult to hire developers, difficult to learn
* no diversity in industry
* users have no influence on product
Well, yes. Software is a labour intensive task. But given the number of jobs digitization has destroyed and the immense gains it provides, I don't think it so bad. Despite the authors criticism it's still an improvement.
I find his argument hard to follow, the author wants to solve 'the problem', but I don't quite get it. The all purpose machine was a good idea, having an evolving eco system, competition, forks, etc. is a good thing.
Re: Why does programming suck?
#7[No ability to execute, no debugging, no compilation step, no unit tests....]
Re: Why does programming suck?
#8There are too many wrong "conclusions" and premises in the text, just an example, here's the author writing about Babbage's and his Analytical Machine:
"he was focused on doing math fast and without errors. He didn’t care how complex the machine was as long as it accomplished that."
Of course, not true, Babbage had to care. He was designing a purely mechanical machine for years at the time when nobody had electrical logical circuits. He designed the simplest "universal enough" machine in the limits of the technology of his time. And the design was never built. But to claim that his design was "too complex" the author would have to design a significantly simpler one under the same limitations and goals.
The whole article is, unfortunately, like this. Uses something that actually happened or somebody did say, "concludes" something else. And the claims that aren't that kind of "conclusions" also sound like from somebody who only very partially understands what he writes about.
This doesn't mean that the author shouldn't attempt to write more articles, he can learn something from it (although I'd suggest him to base his writing on his own, specific, experiences) just that this article as it is is a quite bad potential basis for a serious discussion, IMHO.
He asks "Is there another hardware, general-purpose or not, that would fit our needs more precisely while being cheaper to program?"
The answer is a simple "no." The author just doesn't understand how much of everything was invested up to now for him to pay so little for the CPU's he uses:
https://en.wikipedia.org/wiki/List_of_semiconductor_fabricat...
Note just the "plant stat-up costs in billions" column. And that's just a piece in the whole puzzle. There are big gains for those who'd improve a current state, so the humanity as the whole is much more motivated for the real improvements, where they are possible, than the author assumes.
When we remove wrong conclusions after quoting others, the rant can be summed up to just a few claims, one of major being "I'm confronted with different frameworks and libraries, "everybody" solves similar problems, it "sucks" to work this way, maybe the hardware is the main problem." No.
Re: Why does programming suck?
#9Imagine you're a painter and then comes some moron (who is probably not a painter) yelling at you:
- Why are you holding the brush that way? Also, I don't know that brand. - You should make thinner strokes, and always start coloring the surroundings so you don't go over by mistake. - Do not bother with the first brushes until you have a clear pencil sketch. Actually, here, use this one that I paid someone else to make. Limit yourself to add these colors. - The painters at X draw ultra realistic portraits, that doesn't even look like a cow!
Programming sucks because we need to eat.