Hypothetically, the air conditioning in my VW needed to be replaced (about $1,200), and my mechanic had a piece of software that he wished to "evaluate" (forever). After 10 minutes of hex editing (and cursing) I got the parts at cost and free labor ($800), and my mechanic is still "evaluating" away...
After the university I subsisted during my career search by doing computing odd jobs (installs, virus removal, general end user support). Now five years into my career I only support one of these original "clients", the wine distributor. He is a fairly knowledgeable guy that wants to learn, never asks the same question twice, and understands when you are busy. The best part about this client is the small vintage boutique wines that are tendered as payment.
Executive Summary - Non-PITA user that pays in ultra high end booze.
You get what you pay for?
Examples: SCO UNIXWARE, Windows, MS-DNS, IIS, bea weblogix, etc..
Realization: I paid for crap!!!
You get MORE THAN what you pay for!
Examples: Linux, *BSD's, BIND, Apache, gcc, etc.
Realization: Why did I pay for that crap???
The code from Diebold was closed, and how secure was it? Windows code is closed and I had to install a server just to keep the hoard of daily patches up to date. I think that the key to secure code is not a debate of open v. closed it is about having a programmer/company that cares about security and knows what they are doing. Hell NetBSD is open and very secure (read:unusable).
This guy is a moron.
I think it is all in the presentation. When I was looking for work I stacked the side work into the employment section, and the ones that I couldn't fit (my first resume had to be 1 page) I got to write rec. letters. All in all, I think small jobs do count and at least show that you are trying.
I was in a MIS program a few years ago as a moderately experienced low level network technician. As a student, I wanted to learn real world practical, applicable, specific skills that I could easily transfer to a job/the-real-world.
Instead the college they taught me broad concepts, theories, structures, and abstract ideas to instill knowledge of different fields of IS. I was introduced to multiple programming languages, not to teach me these languages, but to try to make me a developer (and to teach me the mindset and background that I would need to have to actually learn a language). I was taught the relational data-model, the theories of good design, and how to create a logical, practical DB on paper (sure we built projects in Oracle, but we had to learn O development ourselves). The rest of my time was spent learning about things that I saw as a complete waste of time (statistics, accounting, finance, management, marketing, etc.).
While I was in school I was surrounded by people that were getting an MI$ degree, they were just looking for the path of least resistance and the highest paycheck. My program left me as a jack of all trades, and far from a master of anything. I considered my time at the University a complete waste of time. As I entered the job market late in 2000 I also realized that the well had run dry and most of the jobs were gone, and the money was nowhere to be found.
I finally found a job, and believe me it was a humbling experience. My previous on-college-related experience landed me the position, but the degree must have looked good on paper (but I knew difference). Over the past few years I have climbed the ranks and have attained the goals of my five year plan way ahead of schedule, and the funny thing is that I now realize that my hard earned experience was useful for about a week. My degree, and the concepts that it taught me have paid off daily (and will for the long haul).
Your program looks more like a vocational/technical program than a college curriculum. This would be a great resume builder, and short term payoff for students, but learning vendor/brand specific training is no substitute for an education. It is harder to design a network than to configure a router, it is easier to learn C++ than it is to learn how to program, it is harder to learn relational data modeling than it is to learn how to develop an Oracle database. Odds are, the program you and your peers want to re-design probably serves you best (in the long run).
But that is just my $.02 (but at my hourly rate is would actually be about ~$50.00).
My advice is to consider these points; 1. You are a student so experience and resume are paramount (pay is good as well). 2. Establish ownership of your code and control of your project. It is easier to work on a ship that you steer, and hard to work on a ship that has been taken over by pirates. If they own your work they must pay you more (for you to put up with them). If they let you keep it and are a "partner" that keeps you financed in "your" project you can discount a bit. 3. Getting paid by the project makes most companies feel like they can bother you for years without ever paying you again. If you are not hourly/salary you need to have a clear systems analysis and design from the outset. Settle on the features (make them sign something) and do not accept changes without change orders (establish a cost for change orders when they lock the features, and make it $hurt$). They might give you compensation based on milestones, but you need to make them sign something once they are completed. Upon completion have them sign something affirming completion (give them some time to test and tweak). After that, go hourly for maintenance (and stick to your guns)! 4. Finding a company that will pay you by the hour is golden, but they are few and far between. If the company agrees to this, make sure not to take advantage of them. 5. As for hourly rates, as a student I would start the negotiation at $50USD/Hr and go down to $20. The risk you take is saying $50/Hr and them agreeing and chuckling under their breath. If you are in a college town and CompSci geeks are a dime a dozen I would start at $30 and work down to $15.
Good luck, and remember this is just advice from someone on the Internet...
Modification makes things better, this is gonna be much better. -jesse james
Yes, as I sit here reading with my ice cold, refreshing Coca-Cola, I think that you are correct. The only way to get this to stop is by signing the Adobe Acrobat PDF petition.
Parent, You miss the point the existing rules are opt-out, and they get 2 more chances to call you before there is a penalty (in my state). Opt-out is like having to wait to get shot to buy a bullet proof vest...
Reasons telemarketers should get no leniency; 1. Auto-dialers that ask you to hold. 2. Auto-dialers that hang up on you because no real telemarketer is available. 3. Auto-dialers that hang up on people (and look for answering machines/VM). 4. Telemarketers that will not tell you the company they are with when you ask to be removed from the list. 5. Rude telemarketers. 6. Telemarketers that call back when you hang up on them. 7. Telemarketers that will not listen to your sales pitch when they call (when you claim to be a fellow telemarketer).
I think the biggest point of the lawsuits is to try to gain something, anything, from a company that is as technically irrelevant as a 5 ¼ floppy disk manufacturer. Whether they get a multi-billion dollar cash injection, or just get free advertising on/. everyday for several months, they have succeeded on some level; Geeks are talking about SCO, and I haven't said anything about SCO (sans "I hate @#%^ing UNIXWARE" as I stumble through their arcane product) in years.
I guess what I am saying is that the old adage is true, there is no such thing as bad publicity. However much animosity they generate, everyone "in the know" now knows that SCO owns UNIX (somewhat) and is now elevated to a major player in the game. If they get a cash settlement it could be used to develop a viable product, if they just piss people off they get better name recognition and possibly a more expensive company to sell.
Step 1. Run company into ground Step 2. File frivolous lawsuits that enrage the entire computing community (even mac users). Step 3.... Step 4. Profit!
You forget that the Pentium (1) MMX processors doubled the L1 cache in the chip (16K to 32K I think), so even without MMX instructions in the software there was a good performance gain. As for the heat, they were still cooler than the Cyrix and AMD chips (only PowerPC's were running "cool" that year).
Slashdot Mirror
Hypothetically, the air conditioning in my VW needed to be replaced (about $1,200), and my mechanic had a piece of software that he wished to "evaluate" (forever). After 10 minutes of hex editing (and cursing) I got the parts at cost and free labor ($800), and my mechanic is still "evaluating" away...
Cubs playoff tickets? You would never get paid...
After the university I subsisted during my career search by doing computing odd jobs (installs, virus removal, general end user support). Now five years into my career I only support one of these original "clients", the wine distributor. He is a fairly knowledgeable guy that wants to learn, never asks the same question twice, and understands when you are busy. The best part about this client is the small vintage boutique wines that are tendered as payment. Executive Summary - Non-PITA user that pays in ultra high end booze.
You get what you pay for? Examples: SCO UNIXWARE, Windows, MS-DNS, IIS, bea weblogix, etc.. Realization: I paid for crap!!! You get MORE THAN what you pay for! Examples: Linux, *BSD's, BIND, Apache, gcc, etc. Realization: Why did I pay for that crap??? The code from Diebold was closed, and how secure was it? Windows code is closed and I had to install a server just to keep the hoard of daily patches up to date. I think that the key to secure code is not a debate of open v. closed it is about having a programmer/company that cares about security and knows what they are doing. Hell NetBSD is open and very secure (read:unusable). This guy is a moron.
There should be a class action lawsuit for anyone that bought a UNIXWARE linux license.
If Comcast is the cable provider, go DSS. They are the worst cable company I have ever seen.
This could actually be dangerous. Whenever I hide something I seem to inevitably lose it...
I wonder if you would get sued for creating a program skip feature on a PVR?
I think it is all in the presentation. When I was looking for work I stacked the side work into the employment section, and the ones that I couldn't fit (my first resume had to be 1 page) I got to write rec. letters. All in all, I think small jobs do count and at least show that you are trying.
The next catch-22 would be the "paper certification". Without appropriate experience the professional certifications seem not to count.
I was in a MIS program a few years ago as a moderately experienced low level network technician. As a student, I wanted to learn real world practical, applicable, specific skills that I could easily transfer to a job/the-real-world.
Instead the college they taught me broad concepts, theories, structures, and abstract ideas to instill knowledge of different fields of IS. I was introduced to multiple programming languages, not to teach me these languages, but to try to make me a developer (and to teach me the mindset and background that I would need to have to actually learn a language). I was taught the relational data-model, the theories of good design, and how to create a logical, practical DB on paper (sure we built projects in Oracle, but we had to learn O development ourselves). The rest of my time was spent learning about things that I saw as a complete waste of time (statistics, accounting, finance, management, marketing, etc.).
While I was in school I was surrounded by people that were getting an MI$ degree, they were just looking for the path of least resistance and the highest paycheck. My program left me as a jack of all trades, and far from a master of anything. I considered my time at the University a complete waste of time. As I entered the job market late in 2000 I also realized that the well had run dry and most of the jobs were gone, and the money was nowhere to be found.
I finally found a job, and believe me it was a humbling experience. My previous on-college-related experience landed me the position, but the degree must have looked good on paper (but I knew difference). Over the past few years I have climbed the ranks and have attained the goals of my five year plan way ahead of schedule, and the funny thing is that I now realize that my hard earned experience was useful for about a week. My degree, and the concepts that it taught me have paid off daily (and will for the long haul).
Your program looks more like a vocational/technical program than a college curriculum. This would be a great resume builder, and short term payoff for students, but learning vendor/brand specific training is no substitute for an education. It is harder to design a network than to configure a router, it is easier to learn C++ than it is to learn how to program, it is harder to learn relational data modeling than it is to learn how to develop an Oracle database. Odds are, the program you and your peers want to re-design probably serves you best (in the long run).
But that is just my $.02 (but at my hourly rate is would actually be about ~$50.00).
Give them to teens outside of a movie theater, and wait for the fun/pissed off adults to ensue.
My advice is to consider these points;
1. You are a student so experience and resume are paramount (pay is good as well).
2. Establish ownership of your code and control of your project. It is easier to work on a ship that you steer, and hard to work on a ship that has been taken over by pirates. If they own your work they must pay you more (for you to put up with them). If they let you keep it and are a "partner" that keeps you financed in "your" project you can discount a bit.
3. Getting paid by the project makes most companies feel like they can bother you for years without ever paying you again. If you are not hourly/salary you need to have a clear systems analysis and design from the outset. Settle on the features (make them sign something) and do not accept changes without change orders (establish a cost for change orders when they lock the features, and make it $hurt$). They might give you compensation based on milestones, but you need to make them sign something once they are completed. Upon completion have them sign something affirming completion (give them some time to test and tweak). After that, go hourly for maintenance (and stick to your guns)!
4. Finding a company that will pay you by the hour is golden, but they are few and far between. If the company agrees to this, make sure not to take advantage of them.
5. As for hourly rates, as a student I would start the negotiation at $50USD/Hr and go down to $20. The risk you take is saying $50/Hr and them agreeing and chuckling under their breath. If you are in a college town and CompSci geeks are a dime a dozen I would start at $30 and work down to $15.
Good luck, and remember this is just advice from someone on the Internet...
Modification makes things better, this is gonna be much better. -jesse james
Cisco = reliable
Cisco != fast
Yes, as I sit here reading with my ice cold, refreshing Coca-Cola, I think that you are correct. The only way to get this to stop is by signing the Adobe Acrobat PDF petition.
Contextually your reply does not negate your previous error (it could even make it worse).
I hear they aren't really going, they are just using the USA's sound stage from the last "missions".
--replacning tin foil hat.
Go to the register.com, and read some of the BOFH diaries. I base my career on the teachings of Simon.
--PFY
Does this mean that eBay will be flooded with stolen Opterons?
Parent,
You miss the point the existing rules are opt-out, and they get 2 more chances to call you before there is a penalty (in my state). Opt-out is like having to wait to get shot to buy a bullet proof vest...
Reasons telemarketers should get no leniency;
1. Auto-dialers that ask you to hold.
2. Auto-dialers that hang up on you because no real telemarketer is available.
3. Auto-dialers that hang up on people (and look for answering machines/VM).
4. Telemarketers that will not tell you the company they are with when you ask to be removed from the list.
5. Rude telemarketers.
6. Telemarketers that call back when you hang up on them.
7. Telemarketers that will not listen to your sales pitch when they call (when you claim to be a fellow telemarketer).
I think the biggest point of the lawsuits is to try to gain something, anything, from a company that is as technically irrelevant as a 5 ¼ floppy disk manufacturer. Whether they get a multi-billion dollar cash injection, or just get free advertising on /. everyday for several months, they have succeeded on some level; Geeks are talking about SCO, and I haven't said anything about SCO (sans "I hate @#%^ing UNIXWARE" as I stumble through their arcane product) in years.
I guess what I am saying is that the old adage is true, there is no such thing as bad publicity. However much animosity they generate, everyone "in the know" now knows that SCO owns UNIX (somewhat) and is now elevated to a major player in the game. If they get a cash settlement it could be used to develop a viable product, if they just piss people off they get better name recognition and possibly a more expensive company to sell.
Just my $0.02...
Step 1. Run company into ground ...
Step 2. File frivolous lawsuits that enrage the entire computing community (even mac users).
Step 3.
Step 4. Profit!
maybe start iLoveTheScoInformationMinister.com???
Didn't SCO patent the lame @$$ OS that nobody likes concept?
Datacenter Scoreboard:
----------------------
Linux ~20 servers
HP-UX 3 servers
AIX 1 server
SCO 1 server
You forget that the Pentium (1) MMX processors doubled the L1 cache in the chip (16K to 32K I think), so even without MMX instructions in the software there was a good performance gain. As for the heat, they were still cooler than the Cyrix and AMD chips (only PowerPC's were running "cool" that year).