Ask Slashdot: What Are the Hardest Things Programmers Have To Do?
itwbennett writes "Software development isn't a cakewalk of a job, but to hear programmers tell it (or at least those willing to grouse about their jobs on Quora and Ubuntu Forums), what makes programming hard has little to do with writing code. In fact, if the list compiled by ITworld's Phil Johnson has it right, the single hardest thing developers do is name things. Are you a software developer? What's the hardest part of your job?"
Apparently where I work, it's documentation. It's so hard, we don't have any.
Their laundry
I name all of my classes and variables "George." Problem solved.
How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
That was hard. I loved that dog.
Use of the words "good", "bad" or "evil" is almost invariably the result of oversimplification.
There are only two hard problems in Software Development. Naming things, cache invalidation, and off-by-one errors.
Why not quadruple and add four instead? Oh, right, you learned this from an assembly programmer.
What a fool believes, he sees, no wise man has the power to reason away.
"there are two hard things in computer science: cache invalidation, naming things, and off-by-one errors"
I suppose its better if 100,000 people from each side ran at other with swords until one side is dead?
“You mean, you'll put down your rock and I'll put down my sword and we'll try and kill each other like civilized people?”
They can take my LifeAlert pendant when they pry it from my cold dead fingers.
I actually agree with that list.
I don't.
The most difficult task for a programmer is Personal Grooming, followed closely by eating Healthy and getting enough Exercise.
Yeah. I had a boss that after watching Independence Day couldn't figure out why we couldn't just wirelessly connect to anything without any setup or passwords like they do on the movie. And when we told him it was impossible, he thought we were just being difficult. I hate that movie.
Peter predicted that you would "deliberately forget" creation 2000 years ago...
Yeah. I had a boss that after watching Independence Day couldn't figure out why we couldn't just wirelessly connect to anything without any setup or passwords like they do on the movie. And when we told him it was impossible, he thought we were just being difficult. I hate that movie.
Oh, but it is very possible, but security doesn't permit it for one obvious reason: so our primitive enemies can't connect to our space age equipment and turn off whatever vital systems keep them from blowing up our space ships or other valuable infrastructure.
But if he ignore the lessons that could have been learned from the villain's mistakes, then you can still use it to your advantage. Explain that what they did in the movie is commonly termed "infiltration and hacking," and if he wants me to fly into our rival competitor's headquarters and install viruses on their computers; well, that's not my specialty and is illegal, but I'm pretty sure I could do that faster and derive more excitement from it than converting the tabbed based interface we have to whatever interface paradigm was in vogue this morning that you'll change your mind about this afternoon.