Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment What We Teach People (Score 1) 291

No one uses everything we teach them in school, but the only way to find out if you're good at something and enjoy doing it is to give it a try. Not everyone who takes a programming class or two will end up being a programmer, but the approaches we take in programming can be applied usefully to a lot of other problems. Of course, we still seem to have absolutely no idea how to teach people things and it seems like pure luck whether anyone actually learns anything useful in school, so maybe we should try to address that problem first.

Comment How many developers are bad? (Score 1) 809

I've only run across two or three who were atrocious, and I mean to the point where I though they were probably running a scam and collecting a fat paycheck until it seemed likely that they would get caught. I mean, these people knew literally nothing about programming and had to have completely misrepresented themselves to obtain a position.

I've met a lot of "meh" ones, who can kind of get the job done but obviously don't care about or enjoy programming. It was just a high paying career that they could get into.

I've met very few people who do it because they really enjoy doing it and are constantly being driven to learn. They usually get bored at a company within two or three years and move on.

I've met a lot of bad interviewers too, who obviously have no idea how to conduct an interview or what they're looking for in a candidate. They tend to jump on the latest interviewing gimmick bandwagon, whatever that happens to be, without really understanding why that gimmick is supposed to get results that are better than random. Most of the interviews I've seen could have just as easily flipped a coin and had an equal chance of getting a good developer.

Comment CIDR addresses (Score 1) 809

You don't really need to be a network guy. An IP(v4) address is just a 32 bit number. Each octet is just 8 bits. The subnet mask is a binary mask that lets you separate your local network portion of the IP address from the public network (Admittedly I've only ever worked with trivial examples.) The /24 indicates how many of the leftmost bits are set to 1. So a /24 would work out to a subnet mask of 255.255.255.0.

Funnily enough, most C standard library address resolvers can handle IP addresses as actual 32 bit numbers without the octects, which is an occasionally fun party trick.

Comment Re:I'll take the wine instead (Score 1) 480

Even so, to get even money on your buy-in, the jackpot would have to be pretty close to a billion dollars. They advertise the jackpot amount, but the sum basically gets cut in half if you elect to take it all at once in a lump sum. Then taxes will basically cut it in half again. And there's always the chance that someone else will also hit the jackpot and you'll have to split it with them. On these big ones, a single winner is pretty rare. Of course that doesn't make all that much difference if the final sum is still enough to retire permanently. For a lot of lotto jackpot winners, it really isn't.

Jon Oliver has a good bit about it.

Comment No! Not At All! (Score 1) 135

They're great for knowing who has publisher dicks in their mouths. So when I know for certain a game is going to be bad and see, oh let's say, completely hypothetically, IGN give it a 9.5/10, I know IGN is sucking cock and is probably going to get a kickback. "God damn fucking IGN get that publisher cock out of your mouth! We all already know better than to buy a $60 game on your say-so already!" is what I would want to say to them when I see them sucking cock like that! Of course this is a completely hypothetical example, and I'm sure that the quality of IGN's integrity, like the quality of their articles, will never actually come into question!

Comment Re:Nonsense (Score 0) 411

Ugh it took me about a year to lose the Java accent when I started doing a lot of C++ stuff about a year ago. Getters and setters seem to indicate that you're planning to do a lot of run-time introspection in your class, and I'm leaning toward run time introspection being bad in most cases. Every time I've seen it used outside of framework code, it's always by some professional programmer who just learned about runtime introspection and is looking for a nail for that hammer. He's also afraid to commit to any functionality in any single object, because then his objects won't be generic enough to dynamically change their behavior to do anything at run time. And I don't mean "anything" in a general sense of things his objects might actually have been programmed to do. I mean "anything" like literally any object could change its behavior to do literally anything at run time. His code is nearly impossible to maintain and is thoroughly obnoxious. I'm actually talking about one specific guy, and I think he knows who he is. If you're reading this, I have a frowny face just for you. >:-(

Ahem.

Anyway, yeah, things shouldn't need to do things with object internals as much as Java programmers seem to think that things will need to do things with their object internals. I'm leaning toward not writing accessors until I actually need them and then asking myself if I need to access specific information elsewhere, does the data actually belong in that class. In java's defense, if you asked most professional programmers about interfaces and design by contract, you'll probably get a pretty blank stare. At least any of the ones I've interviewed in the past...

Slashdot Top Deals

I don't want to be young again, I just don't want to get any older.

Working...