Are most programmers pussies?
In a recent thread on JoS:
the OP was told (even though he didn't even ask) that he should obey his boss. One of the responses even mentioned the building of the pyramids as an example of team work.
C'mon guys - somebody is trying to blow off some steam in an anonymous forum and is being told to shut up and listen to his boss by his peers.
I guess we try to fancy ourselves like an Ayn Rand following intellectuals but it looks like we have the mentality of factory workers. At least some of the factory workers have the spine to organize themselves in unions.
I say - fuck the Code Nazi that tels somebody to use "static public" instead of the standard "public static".
I feel much fucking better now
July 15th, 2007 12:27am
Just the best ones.
son of parnas
July 15th, 2007 12:30am
When you work for other people you have to put up with stupid shit. Anywhere. Any job.
Oh, and "Ayn Rand following intellectuals" is an oxymoron.
July 15th, 2007 12:35am
There's a minor risk that whoever reads the code could misinterpret it (since he was doing it a different way to everybody else), so if it was an offhand comment then no big deal.
However, any company that spends more than a couple of seconds on these sorts of "issues" needs to seriously reevaluate their priorities.
July 15th, 2007 12:46am
Having standards for arbitrary things is not stupid, it's smart. Stupid is letting the coders spend all day arguing "which is better vi or emacs" and "tabs should be 4 spaces not 8" back and forth when there is a deadline due.
July 15th, 2007 12:55am
Having policies CAUSES those arguments, as this example illustrates.
July 15th, 2007 12:59am
You know why they have an international standard for the length of a meter? Because it's completely arbitrary. A meter could be 1/10,000,000 of the distance from the equator to the north pole through Paris, or it could be the distance travelled by light in absolute vacuum in 1/299,792,458 of a second. It really doesn't make fuck-all difference, there is no argument for one or the other, all that matters is that everybody uses the same meter. So we standardize and we say that's it, that's how it will be. Then, when some smart ass fresh out of college comes into our fucking physics lab and says that a meter should be 1,650,763.73 wavelengths of the orange-red emission line in the electromagnetic spectrum of the krypton-86 atom in a vacuum and everybody should switch to his personal definition, then we cut off his balls and stuff them in his mouth because if we let the little fucker start in with this shit he'll never do a day's work in his life.
July 15th, 2007 1:01am
>You know why they have an international standard for
>the length of a meter
Yes. For a completely different reason.
July 15th, 2007 1:02am
> >You know why they have an international standard for
>the length of a meter
Otherwise they would all be different heights and they would look funny all aligned down the street.
son of parnas
July 15th, 2007 1:04am
The only standard I've come across is zero based arrays (which just makes good sense anyhow). OTW, they just want me to use whatever I'm comfortable with; makes total sense.
What I really want to say is "that is totally gay, changing each others code and back again". but since this is a semi bi- board, I _should_ at least rephrase it. Usually, for me, a superior programmer wrote the code in the first place, and they know the particularities - change/requests - placed into the code.
When I first started writing code, I was using hungarian and all that other happy-horsepuckey, even though everyone told me I was a dumb@ss for doing it.
Now I think they were right, as long as it looks pro and works, it's okay, but no hungarian, pleas. ;-) Give the variables meaningful names instead.
Honestly, provided the coders leave good comments (mostly for the why rather than the what), indent (legibility is all that matters here, not consistency), have descriptive variable and method names, structure the code well and it *works* then who really gives a shit?
July 15th, 2007 4:12am
If you get distracted by the little stuff, maybe the big stuff is either flying overhead, or your are tired, on a tangent, or not interested enough in what the code is actually doing.
The reason for standards on these little programming things is different for a meter.
For a meter it matters we all use the same.
For these little programming things it doesn't usually matter that we all use the same -- except -- when you look at somebody else's code, or you write new code, you want all your brain power focused on how the code works, and not all those little details.
My personal favorite: Don't use plurals for variable names (collective nouns are okay).
For example, a lot of programmers would use something like "items" for an array variable, and "item" for an individual element in the array. Which sounds fine the simple case, but when you have half a dozen of these variables, and it's not always clear-cut which is a plural and which isn't, then you spend half your time just looking up variable names to figure out if they should be pluralized. Much simpler to just write "item" (individual item) and "itemList" (array) or something like that, if you want to be easy to remember.
July 15th, 2007 5:13am
you ever tried working out the change history of a file that every fucker in the team has opened with their personal favourite editor, pressed "auto-reindent" on, edited two lines and then committed?
July 15th, 2007 5:14am
A pox on both houses. There're lots of more important things for the boss to concentrate on, and the programmer should just suck this little thing up, there'll be lots more shit to eat in the future.
July 15th, 2007 7:14am
Yes, I am also not a pussy.
July 15th, 2007 1:01pm
Boy - that was a classic :-)
July 15th, 2007 5:29pm