Comment Re:Server 2012 already looks like Windows 8. (Score 1) 322
I always thought "hipster" was used to describe someone who does something in an inferior way just to be different.
I always thought "hipster" was used to describe someone who does something in an inferior way just to be different.
You mean "7 years experience in Windows Server 2012."
If companies gave a rat's ass about hiring competent workers, job recruiters would speak English.
That doesn't matter. He's saying that if the "EC Econoboxes" were driven like US cars are, the fatalities would be much worse. Around here, a lot of people commute on the Washington Beltway, which is a pretty crazy road to commute on. I once had someone pass me on the left when I was in the left lane. In other words, I was doing 60-ish mph in the left lane approaching a left exit and someone was so impatient he passed me on the shoulder. Do as many people in the UK drive on these massive and complicated interstate-style highways? That would make a difference. If I'm driving 1000 km back and forth to the market, it's probably going be less dangerous than 200 km in 120-kph rush hour traffic and rampant road rage.
I'm not saying he's necessarily right, but he didn't disprove him own point. Maybe the UK just has much, much safer drivers and cars than the rest of Europe (since most of the worst countries listed are in Europe). Maybe it's driving on the left. Maybe it's the better beer. [shrug]
having a generation of students that don't know how to use pointers seems, rather scary to me.
We've managed to get along with the first one, so another one won't be much worse.
You know, for things like memory allocation, pointers, and so on?
Compared to Java? I think it would hold its own.
I think there are good arguments for being exposed to C early, but I wouldn't say it necessarily should be a first language.
For example, when adding some new code I will often put it at the beginning of the line (ie with no indent) so I can see it more clearly whilst coding (usually this is for temporary tracing lines), and only indent it before commit.
I do that in C++ all the time, especially when it's something I don't intend to keep. This is definitely something that you can't do in Python, but that doesn't keep me from liking it.
With Python, on the other hand, I'm actually more likely to have an error in the indenting, because there's no easy way to see how many blocks I'm terminating when I outdent by an arbitrary amount.
I've never really had that problem, but then I always break up code into reasonable sized functions so the nesting doesn't get too deep. Perhaps that's what you need to change.
I thought the whole whitespace-dependent thing was a crock too, coming from 20 years of mostly C++, but since I'm already obsessive about code formatting, I found it very natural and comfortable once I started using Python.
I used Pascal for almost all of my CS courses (but this was in the mid 80s). I got my first job as a C programmer with no formal C experience, but that wasn't a problem, and I never had any problems adapting to new languages during my career as needed. I like some languages more than others, but I can get the job done in anything needed with a short learning curve. I've done mostly C++, which I enjoy, and picked up Python on my own a couple years ago, which I love. I wouldn't call myself a Python expert by any stretch, but I could become one in short order if the need arose. It's all about the programming: Thinking logically, breaking tasks down in discrete steps that do the right thing, knowing what can go wrong. The language is just syntax. It might make some things easier and some things harder, but they're all doable.
Because if we knew Esperanto, we could follow that Esperanto movie William Shatner starred in in 1965. That's pretty useful.
Always draw your curves, then plot your reading.
