Yeah, as long as it is cash, no id needed. A password is enough. Just as he described. I send money to my just-out-of-jail relative this way, since he has no driver's license or other acceptable picture id. Been doing it for at least a year.
I did the co-op thing in college for the phone company. The people I reported to were bordering on incompetent and I had full access within a week of coming on board. I successfully wrecked havoc for a full semester but learned a hell of a lot. They paid me as an entry-level engineer as a junior in college (30,000/yr in the early 90's). I loved it and learned a lot.
Fast forward, summer of 2001. I am the director of development for a huge corporation. I am in charge of bringing in the interns for "cheap tech labor" in the words of my boss. I got a mix of high school and college students. I gave them all projects that they did not know how to do. "Write me an internal web page that displays the following calculations. Here's the server's ftp info, the database logon and a computer with all the software a geek could want with unlimited internet access." Not a single one failed me all summer. I didn't ask them to launch the space shuttle, only do what a programmer with a little experience should be able to do.
I don't know what the circumstances are at your company but likely, the people in charge don't know how to utilize you. Our society expects little to nothing from our youth (as a 30 something geezer) and that is our mistake/loss. This co-op is just an extension of that.
So, in answer to the question: A successful internship program pushes the limits of the intern's potential (resulting in cheap labor, granted) but is challenging and rewarding enough to make the trade off worth it for the intern.
Didn't/. post something from an old guy (I mean like 45 or something) complaining about the same damn thing 3 months ago? I didn't realize this guy was a teenager until he revealed his age a couple lines in.
I have been denied jobs because of my age and years of "professional" experience. Never mind that I have been programming since the vic 20 was using a tape deck for storage. I just never did it professionally until 3 years ago. These companies want 5-10 years experience to be in any kind of leadership position (i.e., someone they have to listen to). What it sounds like you have is knowledge developed outside of your resume. In other words, you spend your off-time tearing stuff apart and know more than some MCSE flunky who has been scraping by for 10 years. Don't lose your bite. If you know something should be done a certain way and someone won't listen to you, screw them. Don't be mean and nasty about it just realize that the old way of doing business meant more about your years in a job or field than about talent. If your company doesn't see that, then look elsewhere or suck it up until you have enough experience to look elsewhere.
Shawn Fanning and Sean Parker could come lecture me about file sharing when they were 15 and I would have listened.
Basically they are going to make Scour conform to the MPAA, which means somebody has to be reimbursed. So, there will be subscription charges or point of sale charges soon. I hate companies like these Centerspan clowns. They are taking an idea/technology they did not invent and try to convert it some thing they can cash in on by playing nice with the industry the technology threatened in its original form. Screw them! I am not paying to download stuff from them.
Just Let Me Vent Here for a Minute
on
Geek Charities?
·
· Score: 1
I asked this same question a month ago and it was declined. I suppose I should feel vindicated but I don't. I already blew the inheritance on stuff I don't care about as much. Ugh.
If you don't work for them any longer then you don't have to sign anything period. You signed a contract at the start of your tenure with them and that covers this, you are under no obligation to continue to sign agreements. Either your initial agreement covers it or it doesn't. They need your signature to add validity to their patent application and you don't have to give it to them.
I asked if you know any lawyers because they will confirm what I have just said. Call your cousin, ex-roommate's brother, whomever. This is basic contract stuff.
I think 2) here is right on the money. I have been swapping good books with friends and family since high school. It just sounds like the beginning of another way for copyright fanatics to control who reads what and who gets paid for each read.
Dude those questions are just plain unanswerable except maybe in multiple choice format.
You know what would be an awesome interview? If they left you in a room with a computer, internet access and told you to complete some task. Set up the domain, install some hardware, update the logon scripts for this user, etc. Now, that would be an interview. No arcane questions and even if they asked you to do something you didn't know how to do, you could get the answer off the net and complete the task.
Agreed on both points-WebObjects rules and no Specs is usually a bad thing. Unfortunately, in this case the firm was hired with the knowledge that they would have original, working source code but no specs. (The site was live already just on another platform.) For myself, if someone told me take a site running PERL and make it act exactly the same using WebObjects, I could make it so without specs. That's just me.
We are a small group in a larger organization but we are WebObjects programmers, so yes we could have feasibly done it but at a cost to the other projects being managed.
Decisions were made at a higher level and we were stuck because the outsource decision had been made, agreements finalized and we just had to make it work.
Your company may be organized differently than ours. PM's in our organization report to the Director of Technical Development who reports to the CTO. The PM in question, while a nice guy, was not technical and was being asked his technical opinion by this company. He was way too far down the totem pole to be used as a second opinion. It was pretty clear to me that they did not want to take direction from the woman ultimately in charge of the project. If the CTO tells you to do something, you do it.
1. Difficult to get in touch with people because of the time difference (something like 12 hours ahead over there.) My cell phone wouldn't take incoming foreign calls nor could I make outgoing foreign calls (didn't want to pay for them anyway). This left me chained to my desk for 7:30 AM phone calls.
2. The calls and faxes will get expensive b/c all meetings must be conducted over the phone, not in person.
3. The company I dealt with made a lot of promises and did not deliver. They were given a site to reverse-engineer using a new technology (went from ASP to WebObjects). Even with source code and complete access to the server's configuration they were unable to complete the task without my team writing 80 pages of technical and functional specifications for them.
4. The time it took us to right the specs, we could have coded the site ourselves.
5. Certain foreign companies don't like women, it is a cultural thing. If the CTO (a woman) gave them instructions, they waited to confirm with the Project Manager (a man). This was problem for us. It may not be a problem for you.
6. The final code was mediocre and completely undocumented due to the language barrier.
7. If you go forward get a fixed price agreement for the complete project. Don't do any weekly rates or billing system that allows them to report hours. We were over budget by 25% because they took longer than promised.
8. Suffice to say, I would never do it again.
9. Good luck.
Yikes. Where was this? We should compile a list of sites and their procedure for storing data as reported anonymously by the programmers and admins who work there. Now that would be a list worth reading.
How does someone go about getting these one time only cards? Do you input your AmEx number online to be issued the new number? Do you call on the phone and customer service type gives it to you? How about mailing it to you (email or snailmail)? The process to procure the numbers would determine whether or not to use the service.
The one hands down benefit is the inability for the business you bought something from to store your *valid* credit card number and expiration in their clear-text SQL Server database.
I have met many a programmer coming out of Harvey Mudd (and MIT or State U.) class of ~1990 who couldn't find a job in their field. Us younger techies don't appreciate what anyone over 28 already does, the economy has peaks and valleys. We are in a peak and no one can say for sure when the next valley will come. Take the opportunities while they are still around to be had.
I'd hire you. The reason is that the word Banyan means something to me. Most HR flunkies can't say the same thing. That is why companies need to get a clue and start having technically informed people contribute to the hiring process. It is not a fun job but programmers, particularly tech leads, should sift through resumes an hour a week or month as well as interview prospects. (Or better yet get a decent CTO to help hire.) If not that, HR reps should be instructed to speak with a seasoned techie before they discard resumes with acronyms and names they don't recognize as well as go into interviews with a list of questions prepared by techies. If you left hiring up to HR, Zimmerman couldn't get a job in internet security.
I am the director of development (which means little, I program and sys admin all day) for a large, well-respected company and are responsible for the hiring of my team. I am 2 years out of school with a CS degree making well into the six figures. I make that because I know what the heck I am doing and would classify myself as a COMPETENT ENGINEER. 9 out of 10 engineers I interview state-side are not competent. So, I look abroad and have enlarged my pool of engineers. H1B's make only slightly less than their American counterparts. My office knows about the 90% rule and complies fully with it. As a matter of fact we are closer to 100%. The US has the lowest unemployment rate in 30 years. It is not my responsibility or moral obligation to hire unqualified IT personnel because their ancestors made the choice to immigrate here and a qualified candidate's ancestors did not.
He most certainly should give credit on this page. However, clearly copyrighting site design is a slippery slope that should be avoided at all costs. (Think "one click shopping" folks.) I think the outrage factor works wonders here. No business would risk the backlash associated with pulling this stunt. The public censure associated with the uncredited copying of work is enough in my opinion. It relegates these unashamed creative thieves to posting to geocities' homepages or their college's student pages.
Post it!
Yeah, as long as it is cash, no id needed. A password is enough. Just as he described. I send money to my just-out-of-jail relative this way, since he has no driver's license or other acceptable picture id. Been doing it for at least a year.
Damn! I've been sending out "man RTFM" in morse code into space for years in my search for intelligent life.
I did the co-op thing in college for the phone company. The people I reported to were bordering on incompetent and I had full access within a week of coming on board. I successfully wrecked havoc for a full semester but learned a hell of a lot. They paid me as an entry-level engineer as a junior in college (30,000/yr in the early 90's). I loved it and learned a lot.
Fast forward, summer of 2001. I am the director of development for a huge corporation. I am in charge of bringing in the interns for "cheap tech labor" in the words of my boss. I got a mix of high school and college students. I gave them all projects that they did not know how to do. "Write me an internal web page that displays the following calculations. Here's the server's ftp info, the database logon and a computer with all the software a geek could want with unlimited internet access." Not a single one failed me all summer. I didn't ask them to launch the space shuttle, only do what a programmer with a little experience should be able to do.
I don't know what the circumstances are at your company but likely, the people in charge don't know how to utilize you. Our society expects little to nothing from our youth (as a 30 something geezer) and that is our mistake/loss. This co-op is just an extension of that.
So, in answer to the question: A successful internship program pushes the limits of the intern's potential (resulting in cheap labor, granted) but is challenging and rewarding enough to make the trade off worth it for the intern.
Didn't /. post something from an old guy (I mean like 45 or something) complaining about the same damn thing 3 months ago? I didn't realize this guy was a teenager until he revealed his age a couple lines in.
I have been denied jobs because of my age and years of "professional" experience. Never mind that I have been programming since the vic 20 was using a tape deck for storage. I just never did it professionally until 3 years ago. These companies want 5-10 years experience to be in any kind of leadership position (i.e., someone they have to listen to). What it sounds like you have is knowledge developed outside of your resume. In other words, you spend your off-time tearing stuff apart and know more than some MCSE flunky who has been scraping by for 10 years. Don't lose your bite. If you know something should be done a certain way and someone won't listen to you, screw them. Don't be mean and nasty about it just realize that the old way of doing business meant more about your years in a job or field than about talent. If your company doesn't see that, then look elsewhere or suck it up until you have enough experience to look elsewhere.
Shawn Fanning and Sean Parker could come lecture me about file sharing when they were 15 and I would have listened.
Basically they are going to make Scour conform to the MPAA, which means somebody has to be reimbursed. So, there will be subscription charges or point of sale charges soon. I hate companies like these Centerspan clowns. They are taking an idea/technology they did not invent and try to convert it some thing they can cash in on by playing nice with the industry the technology threatened in its original form. Screw them! I am not paying to download stuff from them.
I asked this same question a month ago and it was declined. I suppose I should feel vindicated but I don't. I already blew the inheritance on stuff I don't care about as much. Ugh.
Got it.
I think being anti-patent and anti-government is exactly the opposite of socialist. It's called libertarian.
If you don't work for them any longer then you don't have to sign anything period. You signed a contract at the start of your tenure with them and that covers this, you are under no obligation to continue to sign agreements. Either your initial agreement covers it or it doesn't. They need your signature to add validity to their patent application and you don't have to give it to them.
I asked if you know any lawyers because they will confirm what I have just said. Call your cousin, ex-roommate's brother, whomever. This is basic contract stuff.
I think 2) here is right on the money. I have been swapping good books with friends and family since high school. It just sounds like the beginning of another way for copyright fanatics to control who reads what and who gets paid for each read.
I just hope you are right and this fails.
Dude those questions are just plain unanswerable except maybe in multiple choice format.
You know what would be an awesome interview? If they left you in a room with a computer, internet access and told you to complete some task. Set up the domain, install some hardware, update the logon scripts for this user, etc. Now, that would be an interview. No arcane questions and even if they asked you to do something you didn't know how to do, you could get the answer off the net and complete the task.
Agreed on both points-WebObjects rules and no Specs is usually a bad thing. Unfortunately, in this case the firm was hired with the knowledge that they would have original, working source code but no specs. (The site was live already just on another platform.) For myself, if someone told me take a site running PERL and make it act exactly the same using WebObjects, I could make it so without specs. That's just me.
We are a small group in a larger organization but we are WebObjects programmers, so yes we could have feasibly done it but at a cost to the other projects being managed.
Decisions were made at a higher level and we were stuck because the outsource decision had been made, agreements finalized and we just had to make it work.
PM's are not CEO's. This company did not call the CEO for a second opinion. They called the only man they knew on the project, a Project Manager.
Your company may be organized differently than ours. PM's in our organization report to the Director of Technical Development who reports to the CTO. The PM in question, while a nice guy, was not technical and was being asked his technical opinion by this company. He was way too far down the totem pole to be used as a second opinion. It was pretty clear to me that they did not want to take direction from the woman ultimately in charge of the project. If the CTO tells you to do something, you do it.
This was my experience with a company in India:
1. Difficult to get in touch with people because of the time difference (something like 12 hours ahead over there.) My cell phone wouldn't take incoming foreign calls nor could I make outgoing foreign calls (didn't want to pay for them anyway). This left me chained to my desk for 7:30 AM phone calls.
2. The calls and faxes will get expensive b/c all meetings must be conducted over the phone, not in person.
3. The company I dealt with made a lot of promises and did not deliver. They were given a site to reverse-engineer using a new technology (went from ASP to WebObjects). Even with source code and complete access to the server's configuration they were unable to complete the task without my team writing 80 pages of technical and functional specifications for them.
4. The time it took us to right the specs, we could have coded the site ourselves.
5. Certain foreign companies don't like women, it is a cultural thing. If the CTO (a woman) gave them instructions, they waited to confirm with the Project Manager (a man). This was problem for us. It may not be a problem for you.
6. The final code was mediocre and completely undocumented due to the language barrier.
7. If you go forward get a fixed price agreement for the complete project. Don't do any weekly rates or billing system that allows them to report hours. We were over budget by 25% because they took longer than promised.
8. Suffice to say, I would never do it again.
9. Good luck.
Yikes. Where was this? We should compile a list of sites and their procedure for storing data as reported anonymously by the programmers and admins who work there. Now that would be a list worth reading.
How does someone go about getting these one time only cards? Do you input your AmEx number online to be issued the new number? Do you call on the phone and customer service type gives it to you? How about mailing it to you (email or snailmail)? The process to procure the numbers would determine whether or not to use the service.
The one hands down benefit is the inability for the business you bought something from to store your *valid* credit card number and expiration in their clear-text SQL Server database.
I have met many a programmer coming out of Harvey Mudd (and MIT or State U.) class of ~1990 who couldn't find a job in their field. Us younger techies don't appreciate what anyone over 28 already does, the economy has peaks and valleys. We are in a peak and no one can say for sure when the next valley will come. Take the opportunities while they are still around to be had.
I'd hire you. The reason is that the word Banyan means something to me. Most HR flunkies can't say the same thing. That is why companies need to get a clue and start having technically informed people contribute to the hiring process. It is not a fun job but programmers, particularly tech leads, should sift through resumes an hour a week or month as well as interview prospects. (Or better yet get a decent CTO to help hire.) If not that, HR reps should be instructed to speak with a seasoned techie before they discard resumes with acronyms and names they don't recognize as well as go into interviews with a list of questions prepared by techies. If you left hiring up to HR, Zimmerman couldn't get a job in internet security.
I am the director of development (which means little, I program and sys admin all day) for a large, well-respected company and are responsible for the hiring of my team. I am 2 years out of school with a CS degree making well into the six figures. I make that because I know what the heck I am doing and would classify myself as a COMPETENT ENGINEER. 9 out of 10 engineers I interview state-side are not competent. So, I look abroad and have enlarged my pool of engineers. H1B's make only slightly less than their American counterparts. My office knows about the 90% rule and complies fully with it. As a matter of fact we are closer to 100%. The US has the lowest unemployment rate in 30 years. It is not my responsibility or moral obligation to hire unqualified IT personnel because their ancestors made the choice to immigrate here and a qualified candidate's ancestors did not.
He most certainly should give credit on this page. However, clearly copyrighting site design is a slippery slope that should be avoided at all costs. (Think "one click shopping" folks.) I think the outrage factor works wonders here. No business would risk the backlash associated with pulling this stunt. The public censure associated with the uncredited copying of work is enough in my opinion. It relegates these unashamed creative thieves to posting to geocities' homepages or their college's student pages.