Exactly. There is no magic bullet; My brother and I both went to a Montessori elementary school. The educational model worked really well for me, but my brother needed more structure (and he will freely admit this), and didn't do all that well. Once my parents noticed this, and sent him to a more traditional school, he did much better.
I have a huge ego. I freely admit it. I work from home because I can't fit my ego in the office doors.
On a serious note, I prefer code reviews. From the ego-centric side, it has two major benefits: it allows my ego to show off, second it helps the less-experienced/newer developers to learn new techniques, or just learn the code, often in areas they haven't spent a lot of time looking at. That means less time helping them later. It also happens to have the side benefit that their questions can make me think about the problem harder, and not-infrequently uncover typos, thinkos, under-developed (or over-developed) features, or plain bugs. Even for us egomaniacs.
Exactly. When I was the "new guy" at my place of employment, "reviewing" the code of other, more experienced people was very beneficial for me. Not only did it expose me to areas of a very large, complex codebase that I wouldn't have otherwise interacted with, but seeing other (also more experienced) people's comments helped me to understand how many modules interact (or, are supposed to interact) with each other. For the curious, I'm talking about hard drive firmware.
I put reviewing in quotes above because, when I was new, I wasn't able to contribute anything substantial to the review process (we're not talking about c++ syntax issues here).
Can you seriously think of any movie where you'd want to experience every smell?
No, not me personally. But this will give much more hilarity to those Two Girls, One Cup reaction videos! Imagine the reaction when grandma actually gets to smell along!
I recently graduated from college with a BS in computer engineering. My second year, I cooped with a company as a firmware engineer getting paid $19.75/hour.
I went back to the same company upon graduation, and my starting salary was over $60,000 year.
My advice to you is the same that everyone else has given you: Don't pick solely based on compensation. I had to turn down 3 other offers in order to coop where I did, with one of the other positions paying more. I picked it because it was an awesome position at an awesome company, and I don't regret it one bit.
That's just my binary dime
Slashdot Mirror
They'll do it for you.
No, no, no. This isn't Nazi Germany, this is America! We have algorithm czars !
I respectfully apologize, but I am going to invoke Godwin's Law. Please refrain from posting any further comments about this story.
Oh what I would give for mod points right now...
That's where the "random" pat-down comes in to play.
Exactly. There is no magic bullet; My brother and I both went to a Montessori elementary school. The educational model worked really well for me, but my brother needed more structure (and he will freely admit this), and didn't do all that well. Once my parents noticed this, and sent him to a more traditional school, he did much better.
I have a huge ego. I freely admit it. I work from home because I can't fit my ego in the office doors.
On a serious note, I prefer code reviews. From the ego-centric side, it has two major benefits: it allows my ego to show off, second it helps the less-experienced/newer developers to learn new techniques, or just learn the code, often in areas they haven't spent a lot of time looking at. That means less time helping them later. It also happens to have the side benefit that their questions can make me think about the problem harder, and not-infrequently uncover typos, thinkos, under-developed (or over-developed) features, or plain bugs. Even for us egomaniacs.
Exactly. When I was the "new guy" at my place of employment, "reviewing" the code of other, more experienced people was very beneficial for me. Not only did it expose me to areas of a very large, complex codebase that I wouldn't have otherwise interacted with, but seeing other (also more experienced) people's comments helped me to understand how many modules interact (or, are supposed to interact) with each other. For the curious, I'm talking about hard drive firmware. I put reviewing in quotes above because, when I was new, I wasn't able to contribute anything substantial to the review process (we're not talking about c++ syntax issues here).
Can you seriously think of any movie where you'd want to experience every smell?
No, not me personally. But this will give much more hilarity to those Two Girls, One Cup reaction videos! Imagine the reaction when grandma actually gets to smell along!
They already have one, it's called "Two Girls, One Cup". I didn't watch this one, but I expect that it's similar, except without the T&A.
I recently graduated from college with a BS in computer engineering. My second year, I cooped with a company as a firmware engineer getting paid $19.75/hour. I went back to the same company upon graduation, and my starting salary was over $60,000 year. My advice to you is the same that everyone else has given you: Don't pick solely based on compensation. I had to turn down 3 other offers in order to coop where I did, with one of the other positions paying more. I picked it because it was an awesome position at an awesome company, and I don't regret it one bit. That's just my binary dime
You forgot a key step. It should be:
1. be a prof
2. propose theory that must be tested in Greenland
3. ???
4. profit