It's a mistake to think that those two people needed the games to waste time or would have worked if they couldn't play. I think the OP is overshooting a little with giving everyone their own console but still monitoring their play time. I'd set it up in communal area and judge peoples productivity by their output. If somebody pulls their weight while playing quake 6 hours a day why should anyone care.
yes, get back to me when your precious commodore supports LAN, WLAN, 3D graphics, hundreds of input and output peripherals and the literal million things that a modern PC can do. There is a reason for this "sloppyness": hardware is cheap while developer time is not.
My knowledge about the justice system isn't great but at least I know that there is a difference between assault and robbery... In germany you can get away with 6 month for assault but can expect a minimum sentence of 1 years for robbery.
why do you even bother? Anyone who tried out automated testing knows that there are real benefits. Of course, it's not possible to do in every situation but if you never thought to yourself "man, it sure would be nice to verify that my code still does all of what I think it should do after I completely rewrote one part" you've never written and maintained anything worthwhile.
I don't need to account for complex code. Complexity is itself a metric and has no obvious relationship to lines of code. In fact, many software techniques aim specifically at reducing complexity such as encapsulation, design by contract, inheritance and the patterns pattern. Metrics are garbage if you try to interpret or derive to much from them because they suffer from that which all reporting suffers from: you get what you meassure. However, if you want to know the relative size of the codebase of two operating systems it's valid to count the lines of code. Lines of codes equals project size is almost a tautology just as number of centimeters from the ground equals height is...
I'm not attacking the OPs character either, instead I'm mocking that he tried to back up a blatantly wrong statement with an appeal to authority.
Lines of code is not a metric of perfomance at all. It IS a (the) metric of project size and can also give you estimates on the number of bugs in the code. Maybe you should finish your classes before talking about them?
I don't understand what's keeping you from going to a LAN when you are subscriped to an MMO. Maybe the problem has more to do with reliable, affordable high-speed internet then online games although the prevalence of the former sure had a huge effect on the sucess of the later.
We use CVS at work mainly because eclipse had support for it inbuild for quite sometime and the only thing that *really* bothers me is that it doesn't handle deletion in terms of versioning. Aside from that I don't even know why I might need other source control...
Their economic function is to spread risk, not avoid it.
RISK is the operating word. If you are already sick it's not a risk, it's a certainty. You can not insure against something that already happened or has a chance of 100% of happening.
I'm sorry for your condition but in market terms insurance is by definition not something you can buy for a certainty. Even if you could, the premium costs would by higher then that of treatment for the simple reason that insurers want to make money. In other words, you need to have health insurance before you get sick in the same way that you need to insure your house before it burns down. I sincerely feel sorry for your situation but it's misleading to say that the free market has failed you.
Compromise and ask marketing to call it "Captian Placeholder 2009". This way nobody lies to anybody but can still give the impression that your product is modern and fresh while providing versioning in case of later releases. Somebody seriously considering giving you so much money for software will have found out that there where no prior releases anyway and if that doesn't turn them away they probably ask themselves why you feel the need to lie to them right from the get go or how in the hell you need 6 releases to have something you are willing to actually sell.
Another route to go is to use version numbers that are not obviously in sequence [1.0... X] like SAP does with their netweaver family. Their first app server was "SAP Netweaver [snip] 620" and 620 can mean anything they like here.
I fully approve of charging people, who are not able to press the correct button, money for fixing their mistakes. Appearance change, seriously? It's not as if you aren't able to level a new character on an other realm for free...
Interesting how "Hayek Fanbois" predicted every major recession in the last hundred years and how they have a very consitent framework for explaining exactly the causes. This is a SHITLOAD more than any other econ theory can provide. Hell, even Krugman thought the techbubble would never crunch... As for DEM v REP I don't think you'll find much love for either in the austrian school. In fact, Hayek even wrote an essay entitled "Why I'm not a conservative". But here is some food for thought: Do you really think that the current economic situation is wholely and completely caused by policies enacted during the last 8 years? 16? 32? Do you really believe that the economy works in year cycles that are multiples of four? Maybe it has more to do with this: http://en.wikipedia.org/wiki/Image:Components_of_the_United_States_money_supply2.svg
I think energy efficiency is the lowest priority benchmark for an IT landscape. Scalability is a much larger issue and distributed beats out central there by a very large margin.
Yes, welcome to 2000, 1990, 1980 and 1970! Look, here is the deal: centralization has massive problems itself. First of all you can't glue together 10000 cpus, 10000 hdds and 10000 ram banks and have the same performance as 10000 PCs. Secondly there is no unified preference / customization management for applications. We use eclipse on windows terminal server and setting it up so that every user has their own workspace and correct dependencies was such a nightmare that IT coded their own eclipse launcher. Now do that for each application that has something similar. Third, a massively centralized installation becomes unmaintainable because the installation is super critical in the business sense and any downtime leads to thousands of manhours wasted.
There is a reason neither thin nor thick client has won decisively the last N-times this battle was fought: the best solution depends on your circumstances.
Really? How about the "bad connection" issue where the database server due to no reason obvious to the developer will count to ten and then just refuse new connections? How about when MySQL trips over itself and locks it's own tempfile? How about the admin gui that pretends to let you change parameters but really doesn't? How about MySQLs abmyssal speed once it has to deal with larger tables? How about introducing new keywords that are common words like 'release' and thus making a DB upgrade much more painfull then it needs to be? Overall I like MySQL, grew up with it even, but there is no use in pretending like there aren't any problems...
I'm sure the real laws of physics are consistent. The crude approximation we have though, I'm not so sure. To me as a layman it seems that the existence of blackholes are a huge problem in the "divide by zero/infinity" dept and the only "solution" is "well, I guess as long as we can't see impossible stuff happening it'll be alright". Physics the ostrich way... please enlighten me if any physicists are reading this.
It's simple, as long as we are all living in an environment of scarcity meaning that there are no opensource super markets you'll have to participate in trade to keep from starving (Econ 000).
On the other hand the non-compete clause is draconian. I can fully understand why they want you to sign it because without it there is a chance that you'd replicate your developments for them (especially if they've got some good ideas) as open source and thereby voiding their investment. However from your point of view they'd be buying an obligation from you that extends maybe for the next 50 years and applies to your private and professional conduct. For me, that would take a huge load of dough certainly much more than can be earned in a typical development gigs.
If you want the job (and I think it's always great to get payed to do what you like) I'd negotiate that the non-compete clause only and specifically applies to the work you have done for after you leave the company and only while you are in their employ to the whole open source project. In other words: once you leave their employ you'd be free to contibute anything except what you've been working for the company.
Slashdot Mirror
It's a mistake to think that those two people needed the games to waste time or would have worked if they couldn't play. I think the OP is overshooting a little with giving everyone their own console but still monitoring their play time. I'd set it up in communal area and judge peoples productivity by their output. If somebody pulls their weight while playing quake 6 hours a day why should anyone care.
yes, get back to me when your precious commodore supports LAN, WLAN, 3D graphics, hundreds of input and output peripherals and the literal million things that a modern PC can do. There is a reason for this "sloppyness": hardware is cheap while developer time is not.
My knowledge about the justice system isn't great but at least I know that there is a difference between assault and robbery ... In germany you can get away with 6 month for assault but can expect a minimum sentence of 1 years for robbery.
it baffels me that so many people miss that ...
why do you even bother? Anyone who tried out automated testing knows that there are real benefits. Of course, it's not possible to do in every situation but if you never thought to yourself "man, it sure would be nice to verify that my code still does all of what I think it should do after I completely rewrote one part" you've never written and maintained anything worthwhile.
I don't need to account for complex code. Complexity is itself a metric and has no obvious relationship to lines of code. In fact, many software techniques aim specifically at reducing complexity such as encapsulation, design by contract, inheritance and the patterns pattern. Metrics are garbage if you try to interpret or derive to much from them because they suffer from that which all reporting suffers from: you get what you meassure. However, if you want to know the relative size of the codebase of two operating systems it's valid to count the lines of code. Lines of codes equals project size is almost a tautology just as number of centimeters from the ground equals height is...
I'm not attacking the OPs character either, instead I'm mocking that he tried to back up a blatantly wrong statement with an appeal to authority.
haha
Lines of code is not a metric of perfomance at all. It IS a (the) metric of project size and can also give you estimates on the number of bugs in the code. Maybe you should finish your classes before talking about them?
I don't understand what's keeping you from going to a LAN when you are subscriped to an MMO. Maybe the problem has more to do with reliable, affordable high-speed internet then online games although the prevalence of the former sure had a huge effect on the sucess of the later.
We use CVS at work mainly because eclipse had support for it inbuild for quite sometime and the only thing that *really* bothers me is that it doesn't handle deletion in terms of versioning. Aside from that I don't even know why I might need other source control ...
Their economic function is to spread risk, not avoid it.
RISK is the operating word. If you are already sick it's not a risk, it's a certainty. You can not insure against something that already happened or has a chance of 100% of happening.
If Ceasar had [Interstellar Travel] I'm sure he wouldn't have even talked to the dirty gauls :) ... thanks for voting Libertarian!
an alien invasion force would care about as much about different human civs as you care about which hive an ant you just stepped on belonged to.
I'm sorry for your condition but in market terms insurance is by definition not something you can buy for a certainty. Even if you could, the premium costs would by higher then that of treatment for the simple reason that insurers want to make money. In other words, you need to have health insurance before you get sick in the same way that you need to insure your house before it burns down. I sincerely feel sorry for your situation but it's misleading to say that the free market has failed you.
Compromise and ask marketing to call it "Captian Placeholder 2009". This way nobody lies to anybody but can still give the impression that your product is modern and fresh while providing versioning in case of later releases. Somebody seriously considering giving you so much money for software will have found out that there where no prior releases anyway and if that doesn't turn them away they probably ask themselves why you feel the need to lie to them right from the get go or how in the hell you need 6 releases to have something you are willing to actually sell.
... X] like SAP does with their netweaver family. Their first app server was "SAP Netweaver [snip] 620" and 620 can mean anything they like here.
Another route to go is to use version numbers that are not obviously in sequence [1.0
I fully approve of charging people, who are not able to press the correct button, money for fixing their mistakes. Appearance change, seriously? It's not as if you aren't able to level a new character on an other realm for free ...
Interesting how "Hayek Fanbois" predicted every major recession in the last hundred years and how they have a very consitent framework for explaining exactly the causes. This is a SHITLOAD more than any other econ theory can provide. Hell, even Krugman thought the techbubble would never crunch ... As for DEM v REP I don't think you'll find much love for either in the austrian school. In fact, Hayek even wrote an essay entitled "Why I'm not a conservative". But here is some food for thought: Do you really think that the current economic situation is wholely and completely caused by policies enacted during the last 8 years? 16? 32? Do you really believe that the economy works in year cycles that are multiples of four? Maybe it has more to do with this: http://en.wikipedia.org/wiki/Image:Components_of_the_United_States_money_supply2.svg
I think energy efficiency is the lowest priority benchmark for an IT landscape. Scalability is a much larger issue and distributed beats out central there by a very large margin.
Yes, welcome to 2000, 1990, 1980 and 1970! Look, here is the deal: centralization has massive problems itself. First of all you can't glue together 10000 cpus, 10000 hdds and 10000 ram banks and have the same performance as 10000 PCs. Secondly there is no unified preference / customization management for applications. We use eclipse on windows terminal server and setting it up so that every user has their own workspace and correct dependencies was such a nightmare that IT coded their own eclipse launcher. Now do that for each application that has something similar. Third, a massively centralized installation becomes unmaintainable because the installation is super critical in the business sense and any downtime leads to thousands of manhours wasted.
There is a reason neither thin nor thick client has won decisively the last N-times this battle was fought: the best solution depends on your circumstances.
You gotta be pretty stupid to not recognize a computer in a test setting. How about we only let humans compete that have an IQ > 100?
Really? How about the "bad connection" issue where the database server due to no reason obvious to the developer will count to ten and then just refuse new connections? How about when MySQL trips over itself and locks it's own tempfile? How about the admin gui that pretends to let you change parameters but really doesn't? How about MySQLs abmyssal speed once it has to deal with larger tables? How about introducing new keywords that are common words like 'release' and thus making a DB upgrade much more painfull then it needs to be? Overall I like MySQL, grew up with it even, but there is no use in pretending like there aren't any problems ...
Any mention of string theory should be modded likewise :)
I'm sure the real laws of physics are consistent. The crude approximation we have though, I'm not so sure. To me as a layman it seems that the existence of blackholes are a huge problem in the "divide by zero/infinity" dept and the only "solution" is "well, I guess as long as we can't see impossible stuff happening it'll be alright". Physics the ostrich way ... please enlighten me if any physicists are reading this.
yes, operating systems historically have been a BIG problem at gitmo *sigh*
It's simple, as long as we are all living in an environment of scarcity meaning that there are no opensource super markets you'll have to participate in trade to keep from starving (Econ 000).
On the other hand the non-compete clause is draconian. I can fully understand why they want you to sign it because without it there is a chance that you'd replicate your developments for them (especially if they've got some good ideas) as open source and thereby voiding their investment. However from your point of view they'd be buying an obligation from you that extends maybe for the next 50 years and applies to your private and professional conduct. For me, that would take a huge load of dough certainly much more than can be earned in a typical development gigs.
If you want the job (and I think it's always great to get payed to do what you like) I'd negotiate that the non-compete clause only and specifically applies to the work you have done for after you leave the company and only while you are in their employ to the whole open source project. In other words: once you leave their employ you'd be free to contibute anything except what you've been working for the company.