The problem is that taking C and just adding classes and objects would have been nice, but the changes in C++ go so far beyond that they can reach a perl-like level of syntax confusion.
You still have that option. Just take the basic OOP parts and don't use the crazy stuff at all.:)
That's a good idea when you're the one writing it. It's not always in your control when you're maintaining.
A person is a genius if he knows every nook and cranny of C++. But no one is expected to. Even just classes and objects are a fantastic addition over C, so there is really no reason to shun C++.
The problem is that taking C and just adding classes and objects would have been nice, but the changes in C++ go so far beyond that they can reach a perl-like level of syntax confusion.
For me, if I can't understand code written by someone else (which happens much more frequently than I care to admit), I'll do a spike and I'll try to rewrite the core functionality from scratch. Now don't get me wrong. This doesn't mean that my code will be half as good as the original implementation, in fact, it won't be for sure, since I won't spend much time on it. For me, that exercise is just a way for me to initially orient myself (and I do not keep the code I write during that phase).
This is especially helpful in understanding some of the "Why the hell did he do it like THAT?" questions you get when reading someone else's code. Sometimes it's because the original developer was an idiot, but very often it's because you haven't fully grasped part of the problem yet. Or as I like to put in when I need to communicate in cliche-esque speak, "It's a lot easier to appreciate a round wheel when you've built a square one."
Also, vowels apparently used to be very expensive in C variable names "back in the day."
Certain early C implementations would only use the first 8 characters of a variable name. At that point, the vowels are usually the most expendable when coming up with names.
In reality, the success of the campaign was most likely the outcome of a mostly arbitrary and random process that required a lot of luck
1. Someone shows Nissan and other major advertisers how advertisements for their products were showing up on pages advocating/glorifying rape. 2. Nissan (and other) execs pretty much instantly say "Holy Shit I don't want us associated with that" and pull ads from FB, COSTING FACEBOOK HUGE GOBS OF MONEY. 3. Facebook starts addressing the problem.
#fbrape hit them in the wallet. There's nothing random or lucky about it.
Also - copyright terminates when the author(s) die. None of this life-plus-eleventy-thousand-years crap. When you kick, your works revert into the public domain... we *all* benefit from that.
I'd rather just a straight up term of 30 years (or whatever number is most reasonable), regardless of whether or not the author is still alive.
The unanimous part was the weird bit for me. Partly because they all agreed, and partly because I thought the kind of cases that would have unanimous decisions usually didn't make it to the SCOTUS.
You have a job where you can see times square from your desk and you say it sucks? I would trade your view for mine of a black topped parking lot and a building on the other side of it for yours any day of the week, so would millions of others who don't get to see times square of all places.
You need to appreciate what you have.
And you what you have. I would take you up on that trade in a heartbeat.
The only plus is that I moved to the opposite side of the building so I'm not facing the giant flashing Nasdaq billboard all day long. There are flashing lights everywhere, it's very crowded, and the food is mediocre and expensive. I've worked in a few different parts of Manhattan and this is by far the shittiest.
Slashdot Mirror
Most of the younger /. readers never heard of the PDP-11
I was about to complain about the accuracy of that statement... and then I realized I'm not one of the younger readers any more.
/me cries.
The problem is that taking C and just adding classes and objects would have been nice, but the changes in C++ go so far beyond that they can reach a perl-like level of syntax confusion.
You still have that option. Just take the basic OOP parts and don't use the crazy stuff at all. :)
That's a good idea when you're the one writing it. It's not always in your control when you're maintaining.
A person is a genius if he knows every nook and cranny of C++. But no one is expected to. Even just classes and objects are a fantastic addition over C, so there is really no reason to shun C++.
The problem is that taking C and just adding classes and objects would have been nice, but the changes in C++ go so far beyond that they can reach a perl-like level of syntax confusion.
For me, if I can't understand code written by someone else (which happens much more frequently than I care to admit), I'll do a spike and I'll try to rewrite the core functionality from scratch. Now don't get me wrong. This doesn't mean that my code will be half as good as the original implementation, in fact, it won't be for sure, since I won't spend much time on it. For me, that exercise is just a way for me to initially orient myself (and I do not keep the code I write during that phase).
This is especially helpful in understanding some of the "Why the hell did he do it like THAT?" questions you get when reading someone else's code. Sometimes it's because the original developer was an idiot, but very often it's because you haven't fully grasped part of the problem yet. Or as I like to put in when I need to communicate in cliche-esque speak, "It's a lot easier to appreciate a round wheel when you've built a square one."
Also, vowels apparently used to be very expensive in C variable names "back in the day."
Certain early C implementations would only use the first 8 characters of a variable name. At that point, the vowels are usually the most expendable when coming up with names.
Should be "an anonymizing". Not because it's grammatically correct (though it is), but because it's more fun to say.
In reality, the success of the campaign was most likely the outcome of a mostly arbitrary and random process that required a lot of luck
Forgot to mention, that sentence needs to be taken out and shot.
In reality, the success of the campaign was most likely the outcome of a mostly arbitrary and random process that required a lot of luck
1. Someone shows Nissan and other major advertisers how advertisements for their products were showing up on pages advocating/glorifying rape.
2. Nissan (and other) execs pretty much instantly say "Holy Shit I don't want us associated with that" and pull ads from FB, COSTING FACEBOOK HUGE GOBS OF MONEY.
3. Facebook starts addressing the problem.
#fbrape hit them in the wallet. There's nothing random or lucky about it.
Also - copyright terminates when the author(s) die. None of this life-plus-eleventy-thousand-years crap. When you kick, your works revert into the public domain ... we *all* benefit from that.
I'd rather just a straight up term of 30 years (or whatever number is most reasonable), regardless of whether or not the author is still alive.
http://en.wikipedia.org/wiki/Congressman#United_States
Congressman, while generic, usually refers to members of the House. Schumer is a senator.
The unanimous part was the weird bit for me. Partly because they all agreed, and partly because I thought the kind of cases that would have unanimous decisions usually didn't make it to the SCOTUS.
She ain't getting any younger.
I think I could of done better.
Man, you just literally kicked his ass!
And, as it turns out, team communication is the heaviest dependency of all.
That's pure brilliance. Groundbreaking stuff.
I was wondering what this 'SkyNet' thing was, but thankfully the summary and the super helpful wikipedia link made it all clear to me.
The best offices I've seen are around Chelsea and the West Village, and any place that overlooks the park.
We only moved to Times Square about 6 months ago. We were in Chelsea before that, and I absolutely miss that office.
You have a job where you can see times square from your desk and you say it sucks? I would trade your view for mine of a black topped parking lot and a building on the other side of it for yours any day of the week, so would millions of others who don't get to see times square of all places.
You need to appreciate what you have.
And you what you have. I would take you up on that trade in a heartbeat.
The only plus is that I moved to the opposite side of the building so I'm not facing the giant flashing Nasdaq billboard all day long. There are flashing lights everywhere, it's very crowded, and the food is mediocre and expensive. I've worked in a few different parts of Manhattan and this is by far the shittiest.
Dunno what counts for you, but here's a few:
Cnet
gizmodo
Starwars.com
It's in Times Square. Not exactly an obscure location.
Also, totally visible from my desk, which for once made having offices in Times Square not suck.
First thing in my mind too was that this was a "grown-up" version, but I think you and I mean different things by that.
It's possible, but nothing else on the poster implied that they thought there was a joke going on.
An amusing modern example is the group of armed rebels in the Phillipines that go under the name of MILF.
When I was in college, I often saw posters for the Student Organization of Latinos, or as they preferred to call themselves, S.O.L.
This inevitably made me laugh.
Forseveralcenturiesitdidnotusespaceseither.