Painting everything a little bit dark, aren't we? Look here's a story: We just had our national holiday in Germany and therefore a long weekend. So I decided to code an update for an iPhone app I have. The app lets the user create funny pictures, so I thought it would be cool to have an online gallery with user-created pictures, where people could vote on the best ones and have a weekly top list. Now this is far from…
The State of the Art is Terrible
61–70 of 242 posts
Re: The State of the Art is Terrible
#62...Sure, your computer can perform 10 billion floating point operations per second. But most of the time it’s not doing anything at all. Just like you... This is a great rant. Nice emotional content, lots of technical details, the author qualifies his credentials, etc. Easily one of the better articles I've read in the past few weeks. One of the things he mentions is the pain of setup -- something I've painfully watc…
Ah, you youngsters. Trust me, it is FAR easier now to get started than any time in computing history. Before GitHub, you installed SVN or CVS on your own. Before that you accidentally overwrote your software once a month. Before Cloudant you installed MySQL on your own. Before that you wrote your own storage system. Before Amazon you bought a server and installed Linux on it. Before that you wrote customer databases…
I'm just not buying into this "oh, life is so hard to set stuff up nowadays" routine...
Re: The State of the Art is Terrible
#63...Sure, your computer can perform 10 billion floating point operations per second. But most of the time it’s not doing anything at all. Just like you... This is a great rant. Nice emotional content, lots of technical details, the author qualifies his credentials, etc. Easily one of the better articles I've read in the past few weeks. One of the things he mentions is the pain of setup -- something I've painfully watc…
Ah, you youngsters. Trust me, it is FAR easier now to get started than any time in computing history. Before GitHub, you installed SVN or CVS on your own. Before that you accidentally overwrote your software once a month. Before Cloudant you installed MySQL on your own. Before that you wrote your own storage system. Before Amazon you bought a server and installed Linux on it. Before that you wrote customer databases…
I'm with you.
Go build a new computer architecture, Zachary Morris. It seems you have the knowledge and the support. Put it on kickstarter and I'll give you money. Godspeed.
Re: The State of the Art is Terrible
#64...Sure, your computer can perform 10 billion floating point operations per second. But most of the time it’s not doing anything at all. Just like you... This is a great rant. Nice emotional content, lots of technical details, the author qualifies his credentials, etc. Easily one of the better articles I've read in the past few weeks. One of the things he mentions is the pain of setup -- something I've painfully watc…
I'm not following you on the pain of setup. I'm finding it easier to setup things these days than I could 10 years ago. - Need a webserver and database setup? Easy, a few clicks on Heroku and I'm good to go. - Need to learn how to program something that you can then deploy to Heroku? Easy, just follow these 13 steps and you're on your way: http://learnpythonthehardway.org/book/ex0.html WTF is so painful about this?
That's a different path entirely, though not necessarily a bad one. The full stack isn't under your control on Heroku.
Re: The State of the Art is Terrible
#65There's much to enjoy, agree with, and debate in this essay. But this is the most important line.
Re: The State of the Art is Terrible
#66It is exactly the reason why I say that Computer Science is still in the Stone Age.
Re: The State of the Art is Terrible
#67...Sure, your computer can perform 10 billion floating point operations per second. But most of the time it’s not doing anything at all. Just like you... This is a great rant. Nice emotional content, lots of technical details, the author qualifies his credentials, etc. Easily one of the better articles I've read in the past few weeks. One of the things he mentions is the pain of setup -- something I've painfully watc…
Re: The State of the Art is Terrible
#68An excerpt from an article[1] I ran across a few weeks ago seems appropriate: "The printer was the first drum printer that I had ever seen. It would print 1500 lines per minute alphanumeric, and 1800 lines per minute when only numeric values were being printed. It cost $243,450. Its reliability was somewhat suspect. I walked through the room that it was kept in every day for a year, and the only time that I ever saw…
Counterpoint: My office has a printer, yes, it's available over the wireless network. However, it cost... somewhere in the neighborhood of $10,000. I'm not entirely sure, we have a five year lease on the thing, and it costs something like $500/month to run. It's an okay printer, as long as you run Windows. There is a postscript module for the printer, but it costs around $1000, so Mac/Linux machines are out of luck,…
Re: The State of the Art is Terrible
#69Re: The State of the Art is Terrible
#70I've been saying a lot of the same things for years. I'm tired of it now; I'm starting to give up, because it's obvious there isn't a programmer out there that gives a damn. You can try telling them that there's something wrong with software -- something fundamental, something in the process itself that has become horribly broken -- but they'd rather tell you why you're wrong rather than really listen to why you're frustrated.
Then if, as a user (or programmer) you complain about something, they say, "So build your own version." What, we're supposed to re-build the world? OK, fine. So you start building your own version of something. Then the response is, "Why are you reinventing the wheel? That's already been done."
But, what the fuck do I know? I spent a couple of hours in a meeting today with a client explaining why upgrading -- er, pardon, "migrating" -- from Joomla 1.5 to 1.7 wasn't going to happen without a lot of money involved. Then I went to another client and we fixed a broken Windows network stack and a handful of other stuff. Then I came home and unboxed the new laptop that I just bought because my old one could no longer run Firefox anymore -- even though it ran it just damn well fine enough a few years ago. Other than the new laptop, this is pretty much my day -- all day, every day. Well, me and the other guy in my shop.
And nobody else seems to think there's anything strange about this stuff. So Samba's documentation is a mess and Samba 4 never got around to implementing allowed_users, which is absolutely necessary in a Windows AD environment? Pfaah, big deal, so what? So Western Digital's backup software interferes with Outlook in funny ways? Psh. Who cares, who's that going to affect? So everybody's decided to abandon sane software versioning altogether and make the support end of things even more nuts? Hah! Get with the program you support idiots, you're supposed to want to spend all day upgrading software and dealing with the inevitable fallout.
Besides, users that don't like upgrades are just morons, they just don't know what they like. As soon as they get used to the new version, they'll like it better, you'll see.
All of this is stuff I've personally heard, or seen in places like HN ... and not just a few times here and there.
Software used to be fun. I remember when it was, when it seemed like most things just worked, even though they didn't look pretty. I remember when it seemed like I could just open something up and start hacking on it without having to hold tens of thousands of lines of code in my head, spread over dozens of files. I remember when looking at someone else's code could actually teach me something, instead of making me want to cry.
I really don't like this industry much anymore. I guess that makes me a bad hacker or something.