Are we REALLY sure this nut isn't part of the marketing arm of Take-Two? I mean come on, what better way to promote your videogame "Bully" than to launch a right-wing nut who uses "Bully Tactics" to try to get himself a free copy of your game.
It's a more logical explaination than thinking he takes himself seriously...
I didn't invent this expectation that the gov't won't collect information on me unless certian standards are met. The Privacy Act of 1974 REQUIRES the gov't to take very specific steps before they collect information on individuals.
That wasn't Jobs that said that. That line has been passed around for so long, people have forgetten that it was one (Gill Amerio? or was it that ex-pepsi-guy?) of the interim apple presidents during the period when jobs was kicked out of the company. Jobs DID say that the Mac was an "appliance".
For people who think that a mac with bootcamp isn't for them: It's not for you.
I tend to spend just as much on CD's even though I listen to a lot of P2P shared music. What changes is I might download the latest U2 albulm, but I then spend the money on less known bands, some of which I learn about through P2P.
The whole concept is hear to stay, whether or not PB does or not. Music companies have to stop feeling entitled to our dollars and get back into the business of finding and shaping great talent. Once they became a distribution and promotion medium, not a incubator of talent, they lost their focus.
Cisco has no idea how to research, design, build and mart consumer focused electronics. It's not as easy as having a bunch of pocket protectors and a corporate sales force.
They would be better off coming up with their own brand of soda.
... I really don't use job sites, but I've poked around a bit.
1) ban recruiters 2) manditory salary ranges 3) must include company name so I can do research 4) use a good set of standard tags (travel, COBOL, PMI, etc) 5) list when you're deciding to award the job
Beaujolais Nouveau is SUPPOSED to be drank fresh
on
Fast Track to Fine Wine?
·
· Score: 5, Informative
Beaujolais Nouveau is SUPPOSED to be drank right after a short fermentation process. It tastes like CRAP if it's allowed to age more than 6 months.
In france they have festivals mid-november, when the year's Beaujolais Nouveau's are officially allowed to be drank.
I'm sorry, but I think you might have the wrong priorities here. Coming up with standard coding practices should only be your first concern if bad coding practices led to the creation of you new position. Still then, I wouldn't start there.
You've got to realize that your company just added a layer of management, and therefore, complexity, to every in-house project. You should be most concerned with not doing anything that overly complicates the internal development process. Like a doctor, your motto should be "do no harm".
Second you've got to find out what the real problems are (and I will bet you real money, it's not a lack of comments in code, although, they are important, yes). Is the real problem that management can't get realistic information about active projects? Is it that the company is spending too much on maintaining proprietary stuff when they can buy an off the shelf solution? Is it that they're spending too much on off the shelf solutions when they could be developing better solutions in-house?
These are the question you should be asking first, not looking at coding standards.
Skip all the "advice" here and go for more money, rather than intellectual rights. If you really think you're doing something that hasn't been done a thousand times, start a company on the side to own your code and keep it away from your employer until it's more mature.
That most off-the-shelf software products start their life as successful custom apps?
From what I've seen, the life cycle goes like this:
1) build something to solve a specific problem 2) modify to solve a few problems 3) modify to solve similar problems for a few different clients 4) try to modify to make generic enough to sell 5) lauch "off the shelf" package
Of course most project die somewhere before hitting the 5th step, mostly for all the reasons already mentioned. I've worked on projects that have stopped at every stage, and also some that have made it to commercial success.
I don't think I can recall a good product that started life as a commercial package that's been started in the past 5 years. Can you?
I've worked on several campaigns over the past few years, and in my opinion, Dean realized something that others haven't yet caught onto, including bush &co.
The old thinking is that you use a) volunteers, to promote that candidate with b) rich donors, who give you money for your promotions, making you popular with c) voters.
What dean realized is that a) volunteers, b) donors, and c) voters can all be the same people.
Has there ever been a case whwere one company sued the other over IP rights or anything else, then REFUSED to give the "infringing" company enough information to resolve the problem?
Seems it's funny that SCO won't go the Cease and Desist route, because it would have to offer up dome specific proof. Any problems they identify would be resolved in a short amount of time in the next releases...
I see two reasons why this wouldn't work well:
1) IT people like to get their hands dirty, they don't like to manage (in general).
2) IT people don't like to understand problems from a business sense, they like they translated into computer problems first. This inhibits taking a unique idea and solving it via software, as you have to understand the customer/business side first.
3) IT people are bad marketers. They tend to give too much detail and be too honest with shortcomings.
By the way, I started my own software company 6 years ago after being laid off after a merger. I do think it's the way to go, but there's a lot more business to it than most IT people would like.
Also, we just submitted a proposal for a DOD gov't grant to do some custom software development. There's a grant program just for small businesses called SBIR (Small Business Initiative Research).
Slashdot Mirror
Are we REALLY sure this nut isn't part of the marketing arm of Take-Two? I mean come on, what better way to promote your videogame "Bully" than to launch a right-wing nut who uses "Bully Tactics" to try to get himself a free copy of your game.
It's a more logical explaination than thinking he takes himself seriously...
I didn't invent this expectation that the gov't won't collect information on me unless certian standards are met. The Privacy Act of 1974 REQUIRES the gov't to take very specific steps before they collect information on individuals.
That wasn't Jobs that said that. That line has been passed around for so long, people have forgetten that it was one (Gill Amerio? or was it that ex-pepsi-guy?) of the interim apple presidents during the period when jobs was kicked out of the company. Jobs DID say that the Mac was an "appliance".
For people who think that a mac with bootcamp isn't for them: It's not for you.
It's for people like me.
I tend to spend just as much on CD's even though I listen to a lot of P2P shared music. What changes is I might download the latest U2 albulm, but I then spend the money on less known bands, some of which I learn about through P2P.
The whole concept is hear to stay, whether or not PB does or not. Music companies have to stop feeling entitled to our dollars and get back into the business of finding and shaping great talent. Once they became a distribution and promotion medium, not a incubator of talent, they lost their focus.
Cisco has no idea how to research, design, build and mart consumer focused electronics. It's not as easy as having a bunch of pocket protectors and a corporate sales force.
They would be better off coming up with their own brand of soda.
eom.
... I really don't use job sites, but I've poked around a bit.
1) ban recruiters
2) manditory salary ranges
3) must include company name so I can do research
4) use a good set of standard tags (travel, COBOL, PMI, etc)
5) list when you're deciding to award the job
Beaujolais Nouveau is SUPPOSED to be drank right after a short fermentation process. It tastes like CRAP if it's allowed to age more than 6 months.
In france they have festivals mid-november, when the year's Beaujolais Nouveau's are officially allowed to be drank.
I'm sorry, but I think you might have the wrong priorities here. Coming up with standard coding practices should only be your first concern if bad coding practices led to the creation of you new position. Still then, I wouldn't start there.
You've got to realize that your company just added a layer of management, and therefore, complexity, to every in-house project. You should be most concerned with not doing anything that overly complicates the internal development process. Like a doctor, your motto should be "do no harm".
Second you've got to find out what the real problems are (and I will bet you real money, it's not a lack of comments in code, although, they are important, yes). Is the real problem that management can't get realistic information about active projects? Is it that the company is spending too much on maintaining proprietary stuff when they can buy an off the shelf solution? Is it that they're spending too much on off the shelf solutions when they could be developing better solutions in-house?
These are the question you should be asking first, not looking at coding standards.
Skip all the "advice" here and go for more money, rather than intellectual rights. If you really think you're doing something that hasn't been done a thousand times, start a company on the side to own your code and keep it away from your employer until it's more mature.
That most off-the-shelf software products start their life as successful custom apps?
From what I've seen, the life cycle goes like this:
1) build something to solve a specific problem
2) modify to solve a few problems
3) modify to solve similar problems for a few different clients
4) try to modify to make generic enough to sell
5) lauch "off the shelf" package
Of course most project die somewhere before hitting the 5th step, mostly for all the reasons already mentioned. I've worked on projects that have stopped at every stage, and also some that have made it to commercial success.
I don't think I can recall a good product that started life as a commercial package that's been started in the past 5 years. Can you?
Perhaps if they could get the display lag to equal the audio lag, the problems would cancel each other out!
Now all we need is a simple to learn language built to be compiled for threaded servers, and we're all set!
I agree with the artile completely. I have just one exception to the rule:
MySQL.
Well built for what it does, great documentation, user interface via SQL and MYSQL on par with or better than similar products.
Of course the level of UI needed for those types of products is pretty low, but still it's well done, as is the documentation and the book by DuBois.
I've worked on several campaigns over the past few years, and in my opinion, Dean realized something that others haven't yet caught onto, including bush &co.
The old thinking is that you use a) volunteers, to promote that candidate with b) rich donors, who give you money for your promotions, making you popular with c) voters.
What dean realized is that a) volunteers, b) donors, and c) voters can all be the same people.
Jay
Proudliberals.com
Has there ever been a case whwere one company sued the other over IP rights or anything else, then REFUSED to give the "infringing" company enough information to resolve the problem?
Seems it's funny that SCO won't go the Cease and Desist route, because it would have to offer up dome specific proof. Any problems they identify would be resolved in a short amount of time in the next releases...
I see two reasons why this wouldn't work well: 1) IT people like to get their hands dirty, they don't like to manage (in general). 2) IT people don't like to understand problems from a business sense, they like they translated into computer problems first. This inhibits taking a unique idea and solving it via software, as you have to understand the customer/business side first. 3) IT people are bad marketers. They tend to give too much detail and be too honest with shortcomings. By the way, I started my own software company 6 years ago after being laid off after a merger. I do think it's the way to go, but there's a lot more business to it than most IT people would like. Also, we just submitted a proposal for a DOD gov't grant to do some custom software development. There's a grant program just for small businesses called SBIR (Small Business Initiative Research).