I think it's a bit early to say that when all you have is the figment of an imagination of a glimmer of what could be something akin to a possible shimmer of a glimpse of light in a sea of pitch black darkness.
You mean the parts that I bought like 3 hardware generations ago that I still use? Why, do you figure in the TV price every time you buy a new console?
By the time you go for the 4th decade of your life, you should have an idea what direction you want to go. You will not be a programmer with 45. Because there are younger people who are just as good as you but more willing to put up with the shit the company will dump on them. And they are probably cheaper too.
With 40, you should have expanded your skill set. Being a great programmer is one thing, but you should become more, like the senior tech and go-to guy for bugs that can't be caught and problems that can't be solved. By that time, you should be more than just the guy that can write good code.
Whether you're the person that can find every bug, the guy that can put a derailed project back on track and time, the guy that is the only one that still understands the databases' ins and outs and the quirks of the core program, that's up to you, but by the time you're 40, you should be more than yet another code writer.
Do I care? I care for the 300k a year and the chance to retire before I am burned out so I eventually have the time and money to do projects that I love.
They learned a valuable lesson for life: Study something that you're interested in, because if you don't, the field will crush you with its weight. If you're not interested in what you're trying to study, you're in for a life of hurt. First, it will be painful to get the degree and even if you get one, you'll have a degree that enables you to do for the rest of your productive life something you do not want to do.
Studying something because "this is where the money is" is pointless. Because the only ones that WILL make "that money" are the ones that actually WANT to do it, that are willing and able to go beyond the bare minimum that someone who loathes the whole shit is willing and able to put into it. If anything, you'll be mediocre AND miserable.
It's just that a closing apostrophe looks odd to us. Or an opening one. I mean, look at the first sentence. Everything after "It" is in an open string that just begs to be closed. But this odd thing called human language won't grant us that unless I deliberately (as in this sentence) include another word that needs an apostrophe. But tell me, what kind of sentence is
's just that a closing apostrophe looks odd to us. Or an opening one. I mean, look at the first sentence. Everything after "It" is in an open string that just begs to be closed. But this odd thing called human language won'
If the procedure he's used to includes punishment for doing something, expecting him to do just that is probably understandably going to be met with doubt at first.
A CS degree doesn't make you a programmer. You better are one already when you try to get a CS degree.
I find it highly amusing to see people enter CS with the idea that you'd learn programming there. That's like entering an arts college and expecting them to teach you how to paint. And I don't mean "show you how to become a better painter", but that people go there who never touched a brush in their life and expect to be turned into the next Dali or Picasso.
What a CS degree can do is give you the theoretic background to become a better programmer. It can allow you to identify flaws in your code, it may even give you the tools to program more efficiently, but it's not a coding class where you learn the basics of control structures and functions. That's not their job. That's yours. Learn that and return to college when you can do that. Then we'll build on top of that, teach you information theory, teach you the importance of runtime optimization, teach you how to identify bottlenecks, race conditions and the more elusive problems that you will run into.
This. Once they find out that the first 2-3 years of CS is actually math, math, math, math and a little bit of information theory, they'll quit.
And sorry, no, we don't teach you programming and how to make an iPhone app that sells more than a billion units so you don't have to work anymore. We expect you to know how to program when you enter here. At least that was the case with my university. It was pretty much expected that you know at least one imperative language. There was a token introduction course but if that's all you had for "me learn computer now", you were hopelessly lost.
Dear BA major: Just because in your degree it's completely irrelevant whether you actually understand any of the garbage you're required to soak up, spill onto the test and forget afterwards, that doesn't mean it is that way in other venues, too. Unfortunately to be successful in CS, you not only have to swallow a book from back to back, you have to actually understand because you have to build onto that what's inside that book and go beyond it to actually solve the problems presented to you.
Yes, we do actually have to think for ourselves. I know that concept is alien to you and I don't expect you to understand (actually, I don't expect BAs to understand anything, that's simply not something they're required to do and I can only imagine that understanding that bullshit would actually make you go nuts), just do what you do with the crap you had to learn: Accept it as true.
The difference is that there is no test this time where you can dump it and forget it.
Best thing I ever read was "Despite best effort from our management team the project was finished on time".
Priceless. Of course it was a "typo" and was later corrected, but... well, let this be a lesson, manager, you can slack all you want and let the techs pick up your slack, but never ever let the tech write your project summary statement.
Are you nuts? Of course we want casualties. Do you know what it costs to feed and house soldiers? And with the amount of people dropping out of school every year they get more and more, and what are we going to do if we can't stuff those duds into the army and... reduce their number that way? You can't simply go, round up the idiots and shoot them yourself, ya know? That's not something that gets you reelected.
Slashdot Mirror
Shhh... Not so loud, lest you wake Michael Bay and he makes a movie about them.
Why wouldn't an object cast a shadow in the vacuum of space?
I think it's a bit early to say that when all you have is the figment of an imagination of a glimmer of what could be something akin to a possible shimmer of a glimpse of light in a sea of pitch black darkness.
They also increase the danger of a rogue government.
Nah, we'll just shoot whoever wins and then go on with our lives.
You mean the parts that I bought like 3 hardware generations ago that I still use? Why, do you figure in the TV price every time you buy a new console?
Telling an engineer joke to a BA major is like explaining nuclear physics to a pig. It wastes your time and makes the pig annoyed.
By the time you go for the 4th decade of your life, you should have an idea what direction you want to go. You will not be a programmer with 45. Because there are younger people who are just as good as you but more willing to put up with the shit the company will dump on them. And they are probably cheaper too.
With 40, you should have expanded your skill set. Being a great programmer is one thing, but you should become more, like the senior tech and go-to guy for bugs that can't be caught and problems that can't be solved. By that time, you should be more than just the guy that can write good code.
Whether you're the person that can find every bug, the guy that can put a derailed project back on track and time, the guy that is the only one that still understands the databases' ins and outs and the quirks of the core program, that's up to you, but by the time you're 40, you should be more than yet another code writer.
Do I care? I care for the 300k a year and the chance to retire before I am burned out so I eventually have the time and money to do projects that I love.
They learned a valuable lesson for life: Study something that you're interested in, because if you don't, the field will crush you with its weight. If you're not interested in what you're trying to study, you're in for a life of hurt. First, it will be painful to get the degree and even if you get one, you'll have a degree that enables you to do for the rest of your productive life something you do not want to do.
Studying something because "this is where the money is" is pointless. Because the only ones that WILL make "that money" are the ones that actually WANT to do it, that are willing and able to go beyond the bare minimum that someone who loathes the whole shit is willing and able to put into it. If anything, you'll be mediocre AND miserable.
Is that what you want for your life?
It's just that a closing apostrophe looks odd to us. Or an opening one. I mean, look at the first sentence. Everything after "It" is in an open string that just begs to be closed. But this odd thing called human language won't grant us that unless I deliberately (as in this sentence) include another word that needs an apostrophe. But tell me, what kind of sentence is
's just that a closing apostrophe looks odd to us. Or an opening one. I mean, look at the first sentence. Everything after "It" is in an open string that just begs to be closed. But this odd thing called human language won'
That just makes NO sense at all, does it?
If the procedure he's used to includes punishment for doing something, expecting him to do just that is probably understandably going to be met with doubt at first.
A CS degree doesn't make you a programmer. You better are one already when you try to get a CS degree.
I find it highly amusing to see people enter CS with the idea that you'd learn programming there. That's like entering an arts college and expecting them to teach you how to paint. And I don't mean "show you how to become a better painter", but that people go there who never touched a brush in their life and expect to be turned into the next Dali or Picasso.
What a CS degree can do is give you the theoretic background to become a better programmer. It can allow you to identify flaws in your code, it may even give you the tools to program more efficiently, but it's not a coding class where you learn the basics of control structures and functions. That's not their job. That's yours. Learn that and return to college when you can do that. Then we'll build on top of that, teach you information theory, teach you the importance of runtime optimization, teach you how to identify bottlenecks, race conditions and the more elusive problems that you will run into.
CS doesn't stand for Coding School, dammit!
This. Once they find out that the first 2-3 years of CS is actually math, math, math, math and a little bit of information theory, they'll quit.
And sorry, no, we don't teach you programming and how to make an iPhone app that sells more than a billion units so you don't have to work anymore. We expect you to know how to program when you enter here. At least that was the case with my university. It was pretty much expected that you know at least one imperative language. There was a token introduction course but if that's all you had for "me learn computer now", you were hopelessly lost.
Dear BA major: Just because in your degree it's completely irrelevant whether you actually understand any of the garbage you're required to soak up, spill onto the test and forget afterwards, that doesn't mean it is that way in other venues, too. Unfortunately to be successful in CS, you not only have to swallow a book from back to back, you have to actually understand because you have to build onto that what's inside that book and go beyond it to actually solve the problems presented to you.
Yes, we do actually have to think for ourselves. I know that concept is alien to you and I don't expect you to understand (actually, I don't expect BAs to understand anything, that's simply not something they're required to do and I can only imagine that understanding that bullshit would actually make you go nuts), just do what you do with the crap you had to learn: Accept it as true.
The difference is that there is no test this time where you can dump it and forget it.
Best thing I ever read was "Despite best effort from our management team the project was finished on time".
Priceless. Of course it was a "typo" and was later corrected, but ... well, let this be a lesson, manager, you can slack all you want and let the techs pick up your slack, but never ever let the tech write your project summary statement.
Unfortunately the truth is closer to hexadecimal...
It's sad that even fewer understand how Halloween can be on Christmas Eve.
A metric ton or two. Delivered in handy 250lbs packages.
Not only that, but why not use nukes if neither side has humans on the battlefield anyway?
And the 'u' is for "useful".
A strange game. The only winning move is not to play. How about a nice game of Hearts of Iron?
Given the average obesity level in the US: Why again are they the nation that waged the most wars in the past half century?
Coming to a theater near you, the next installment: "The people shrugged".
You might want to watch it early, it's not a given it will play for long.
Are you nuts? Of course we want casualties. Do you know what it costs to feed and house soldiers? And with the amount of people dropping out of school every year they get more and more, and what are we going to do if we can't stuff those duds into the army and ... reduce their number that way? You can't simply go, round up the idiots and shoot them yourself, ya know? That's not something that gets you reelected.