Shouldn't programmers know how to fix computers?
-
Doesn't that confuse (or at least disappoint) teenage boys a bit?
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Doesn't that confuse (or at least disappoint) teenage boys a bit?
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Does it drive anyone else bonkers when developers keep complaining about their windows PC blue screening? If you know how to program why can't you figure out how to fix your own computer, or at least start researching?
There are only 10 types of people in the world, those who understand binary and those who don't.
-
you ryanb31, are a boob.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011)LOL - Agree :)
-
sock puppet account?
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) -
Does it drive anyone else bonkers when developers keep complaining about their windows PC blue screening? If you know how to program why can't you figure out how to fix your own computer, or at least start researching?
There are only 10 types of people in the world, those who understand binary and those who don't.
Shouldn't drivers know how to fix their cars? (Since I was beat to that statement, replace this with: ) Shouldn't guests in the restaurant know how to cook?
-
Does it drive anyone else bonkers when developers keep complaining about their windows PC blue screening? If you know how to program why can't you figure out how to fix your own computer, or at least start researching?
There are only 10 types of people in the world, those who understand binary and those who don't.
Har-dee-har har...
Let us return now to those thrilling days of yesteryear, when the operating system was delivered as a spool of paper tape, when we toggled in the bootstrap program from memory via the front panel switches, and when we patched everything, including the OS, in hexadecimal. When source-code-aware debuggers were a glint in some atavism’s eye, and “structured programming” was still an absurd new notion of the ivory-tower types. When the men were men, and the sheep slept with one eye open.
C'mon, now. A blue screen almost always means a fault in something:
- That you didn’t produce;
- That you don’t have the source code for;
- That’s poorly documented in some barely-recognizable dialect of English;
- That you understand dimly if at all;
- That some overworked Indian grad student turned out on his lunch hour for a total compensation of fifty bucks and a free copy of Flight Simulator;
- That’s you’d probably get in trouble for meddling with, even if you knew how to fix it, which you don’t.
There are occasional exceptions. If you’re working on a new device driver (whether or not you’re an overworked grad student, Indian or otherwise), you might encounter one of those exceptions. But in the main, contemporary computer systems are far too obscure, and too multifarious in their provenance, to allow us to fix faults outside our own applications. Especially since we aren’t all that good at fixing the faults that occur inside our own applications.
(This message is programming you in ways you cannot detect. Be afraid.)
-
Does it drive anyone else bonkers when developers keep complaining about their windows PC blue screening? If you know how to program why can't you figure out how to fix your own computer, or at least start researching?
There are only 10 types of people in the world, those who understand binary and those who don't.
-
So you expect anyone who programs computers to also be a hardware technician? Most automobiles have many computerized systems in them. Do you expect the mechanic to be a computer technician? Do you expect them to be a materials engineer to determine why the brake pads have worn out?
Failure is not an option; it's the default selection.
I would expect any tradesman to know how to maintain the tools he works with. I wouldn't hire a carpenter with blunt chisels to put in a new kitchen. So why should a programmer be any different? Their PC is the primary tool they need to do their work so they should at least know the basics of how to maintain it.
-
Does it drive anyone else bonkers when developers keep complaining about their windows PC blue screening? If you know how to program why can't you figure out how to fix your own computer, or at least start researching?
There are only 10 types of people in the world, those who understand binary and those who don't.
I assume your are a support tech. Please forgive me if I am wrong. Developers do know how to fix their computers, the competent ones, but it is not cost-efficient to do it. If you are a tech you can probably program in one or two languages. However, a good full-time developer cranks many more lines than you a day. On the other hand, while he is doing that, you fix many more computers. Even though a programmer can fix his computer, he knows, or at least I know that my techs can do it faster than me. I am sorry if you are working with incompetent developers. But, even a good one would not waste his time with fixing a blue screen unless from experience he knows that it is faster to fix it than to call you. The difference between a bad developer and a good one is that the good one will use that time to work, no excuses no complains, and a bad one will go tell the manager that the techs messed it all up and the cat eat his source code. The programmer and the tech should act as a team. The Programmer makes sure the code is as close to perfect as possible within the time constrains, so the company is profitable, and the tech makes sure the programmer can do that without any distraction. It's called team work. I am sorry that you guys have to work with people who don't know what a shortcut is and such. They really need to asses their careers. However, please don't generalize. Respectfully, Di
-
No. That's like saying 'if you know how to drive why can't you figure out how to fix your own car'. Some people are interested enough to research around the whole thing that they work with, but not everyone.
That analogy is not the same. A driver of a car is just a user of the car. I am not asking that users know how to fix computers. Programmers, on the other hand, are the ones writing code that runs on a computer so they better know something about how computers work.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
Shouldn't drivers know how to fix their cars? (Since I was beat to that statement, replace this with: ) Shouldn't guests in the restaurant know how to cook?
A guest of a restaurant is a client of the restaurant. That is the same as the person buying your software, so no, a client of a restaurant does not need to cook. The analogy does not work.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
Har-dee-har har...
Let us return now to those thrilling days of yesteryear, when the operating system was delivered as a spool of paper tape, when we toggled in the bootstrap program from memory via the front panel switches, and when we patched everything, including the OS, in hexadecimal. When source-code-aware debuggers were a glint in some atavism’s eye, and “structured programming” was still an absurd new notion of the ivory-tower types. When the men were men, and the sheep slept with one eye open.
C'mon, now. A blue screen almost always means a fault in something:
- That you didn’t produce;
- That you don’t have the source code for;
- That’s poorly documented in some barely-recognizable dialect of English;
- That you understand dimly if at all;
- That some overworked Indian grad student turned out on his lunch hour for a total compensation of fifty bucks and a free copy of Flight Simulator;
- That’s you’d probably get in trouble for meddling with, even if you knew how to fix it, which you don’t.
There are occasional exceptions. If you’re working on a new device driver (whether or not you’re an overworked grad student, Indian or otherwise), you might encounter one of those exceptions. But in the main, contemporary computer systems are far too obscure, and too multifarious in their provenance, to allow us to fix faults outside our own applications. Especially since we aren’t all that good at fixing the faults that occur inside our own applications.
(This message is programming you in ways you cannot detect. Be afraid.)
-
You mean you know how to fix your pc everytime your screen bsods? wow i just usually just use trial and error through the usual suspects to find a solution to the problem
-
That analogy is not the same. A driver of a car is just a user of the car. I am not asking that users know how to fix computers. Programmers, on the other hand, are the ones writing code that runs on a computer so they better know something about how computers work.
There are only 10 types of people in the world, those who understand binary and those who don't.
This is especially not the same thing on windoze machines. It is possible I could agree with you on a linux box, but not windoze. Writing some code to run on the computer is NOT the same thing at all as using the black box code that RUNS the computer. Even your programs have black boxed code in the case of .net. And by the way, we've spent the day looking up an error code on the windoze server before. Those error codes aren't that great. (note the error codes did not come from BSOD, just error codes that prevented the server from being able to do it's job). From my experience, the msdn site isn't even sure what the error really is. It has a list of things it COULD be, but even they aren't sure. Normally when we solve the problems I've run into it had absolutely nothing to do with what the listed problems for that error code actually was. Not to mention how long that took us away from actually writing software.
If it moves, compile it
-
I assume your are a support tech. Please forgive me if I am wrong. Developers do know how to fix their computers, the competent ones, but it is not cost-efficient to do it. If you are a tech you can probably program in one or two languages. However, a good full-time developer cranks many more lines than you a day. On the other hand, while he is doing that, you fix many more computers. Even though a programmer can fix his computer, he knows, or at least I know that my techs can do it faster than me. I am sorry if you are working with incompetent developers. But, even a good one would not waste his time with fixing a blue screen unless from experience he knows that it is faster to fix it than to call you. The difference between a bad developer and a good one is that the good one will use that time to work, no excuses no complains, and a bad one will go tell the manager that the techs messed it all up and the cat eat his source code. The programmer and the tech should act as a team. The Programmer makes sure the code is as close to perfect as possible within the time constrains, so the company is profitable, and the tech makes sure the programmer can do that without any distraction. It's called team work. I am sorry that you guys have to work with people who don't know what a shortcut is and such. They really need to asses their careers. However, please don't generalize. Respectfully, Di
I am not a support tech. The particular issue that has put me over the top is 2 co-workers who BSOD almost daily. We are a small company and do not have the IT guy readily available. All they do is complain about it, they never even look up the error. But I still stand by my point. The computer is not only a tool we use to develop it is also the platform for which our products are delivered. I don't understand the narrow-mindedness of claiming "I just write code."
There are only 10 types of people in the world, those who understand binary and those who don't.
-
A guest of a restaurant is a client of the restaurant. That is the same as the person buying your software, so no, a client of a restaurant does not need to cook. The analogy does not work.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
A guest of a restaurant is a client of the restaurant. That is the same as the person buying your software, so no, a client of a restaurant does not need to cook. The analogy does not work.
There are only 10 types of people in the world, those who understand binary and those who don't.
I don't quite agree, since a SW developer bought the PC, the OS, the compiler and possibly other tools to be able to program. But yeah, the drivers/cars analogy works better.
-
I am not a support tech. The particular issue that has put me over the top is 2 co-workers who BSOD almost daily. We are a small company and do not have the IT guy readily available. All they do is complain about it, they never even look up the error. But I still stand by my point. The computer is not only a tool we use to develop it is also the platform for which our products are delivered. I don't understand the narrow-mindedness of claiming "I just write code."
There are only 10 types of people in the world, those who understand binary and those who don't.
As soon as the source code for m$ is released so that I can alter and recompile it, I will not complain anymore :P Seriously though. I get very frustrated with windoze because it's not my platform. The guy who teaches me windoze at work does not get all upset over it, he even makes jokes with me about it to lift my spirits sometimes. I'm not trying to dodge work, or even keep from learning how to fix it. I actually consider it to be a big mess most of the time. However, I'm learning quickly how to operate in it, trouble shoot it, etc. That will not stop me from needing to vent when something goes wrong in a situation where I'm already confused. I vent, we work together to figure out how to fix it and move on. Some times i remember the solution, sometimes I don't. None of that takes away from my ability to write good software. A BSOD that stops me does not have anything to do with my ability to write code.
If it moves, compile it
-
m$ programmers are just users of m$ software. It's black boxed software, so it's not like we have much other choice. The fact that we are power users does not mean that we are not still users.
If it moves, compile it
