I agree with the statement that a non-brilliant idea is the problem for these developers. I see people draining their life-blood into startups with absolutely no compelling future or growth potential, but somehow manage to talk some investors into paying for their time. They are piggybacking on a popular platform, thinking that a certain kind of application behavior (like smooth scrolling!) is extremely valuable, spending years to develop it while blindly ignoring the fact that they aren't doing anything innovative.
99.9% of humans don't have good ideas. The ones that do usually can't engineer them.
I can only hope that the injunction calls for the end of his rapping for all eternity.
Because I think this was the straw that broke the camel's back for me:
http://www.youtube.com/watch?v=9iUvuaChDEg
After having to sit through that awful experience, I was all "Git 'im and make him stop!"
So you want to be an android develeper?
No.
I'm a Motherfucking programmer motherfucker. And garden variety Java programmers? Is Objective C that friggin obtuse?
What does the app do? Does it contain videos of Aria Giovanni, Luba Hegre or Zuzanna from bodyrock.tv? I'm pretty sure they cured any gayness I might have have.
The app store isn't a wild west free-for-all (chaps anyone?). I'm perfectly satisfied with my Android.
Agreed. I found that around the age of 25, I began re-reading certain books and re-watching movies to find that I interpreted them differently the second time. Years later I'm still re-watching movies that I forgot I watched. Thanks to Netflix of course.
Cost. Cost and politics are not the same thing. If you threw out every piece of engineering as soon as a new design came along, you'd never have a running system in the first place. Reactor cores last longer than most engineer's careers. They are also integral to the design. No reactor is completely fail safe.
Their advertising and especially sales people and the TOS don't agree. I had an account for a while, but got a backup DSL from ATT. I ended up using only the backup line because even though it was the lowest priced package from ATT, it always worked and was always fast enough.
This is garbage. Mobile gaming, cloud computing, eh rewriting wolfenstein to add ray tracing in the cloud???
I can see why that might make a POC, but Wolfenstein's not even 3D!
"We have a red car sitting at a courtyard, which has a very shiny reflective surface. That can be rendered very good."
OK, not speaking Inglish isn't a crime. But the editors should catch this kind of thing.
UNworth reading.
We have thousands of Linux boxes. Our admins either slow roll, fast roll, kick or flash them individually or in groups, depending on the situation.
Maintaining the servers and apps on them individually doesn't scale in terms of human resources. If an app is leaking resources or otherwise misbehaving, the admins take a snapshot of the app state (heap dump etc) and roll the app.
Flashing happens infrequently, usually for upgrades. Patching is just as slow and tedious, so flashing makes sense when you can just schedule an operation to happen on a few hundred servers at a time. Otherwise we'd have to do things by hand incredibly slowly over SSH. We used to do it this way, but that doesn't scale either.
"You have the right to remain silent. Anything you say may be used against you in court."
You don't have to be a genius to understand the US Miranda rights.
Can you provide an example? I think that may have been the case a few years ago. Hotel and travel search are very competitive.
It is a whole lot more difficult to find relevant technical info on popular web tech/languages/frameworks etc that it was a few years ago.
Porn, now that is the biggest offender. There are hundreds of fake porn blogs and redirects for any search. Nobody really cares though, since pretty much all of the sites contain porn, which is what you're looking for.
FTA:
"Organizations could use the servers to test the applications locally before uploading them to Amazon's paid service. The servers have a preconfigured testing and development environment. Eucalyptus duplicates the AWS APIs (application programming interfaces)."
At first, I was like, They're just selling the PowerEdge server + cloud buzzword. However, a local Dev and QA environment for AWS is nice, especially if its already configured to behaving like AWS. One problem with running stuff on AWS is troubleshooting and reproducing performance problems.
The AI part is image recognition of the grid and clues. That's interesting, but it's been done already. I'd like to know how they implemented the solver. The Soduku problem is considered NP-complete. Which is just about the only thing that is interesting about the puzzle. I've never bothered to solve one myself, since I don't think there is anything to learn from it. Actually implementing a solver might be an interesting waste of time though.
Say there are 5 million contributors @ $100 (unlikely). What size etching should each get?
Lets pretend we have 2 sides of a 10 meter tall monolith to etch.
Each contributor would get a space roughly 0.04mm in size in which to etch his name....
This needs rethinking.
1) Don't spend too much time on development.
This may be true for sequels. It isn't necessary to spend a whole lot of time (5+years is a long time) provided that the original was coded well and can be re-used for the most part.
2) Change your engine every so often, and if you can, use one that you've developed yourself.
This goes against #1 to some degree. I can't see any good reason to create a new engine unless you are developing on a new platform which the existing engine doesn't like.
A really good modular general purpose engine can evolve to take advantage of new platform features (theoretically).
3) Try to keep the team the same, especially if the original was good.
There are two sides to this. Some of the original team members will have a context for improving the game. They obviously will understand the design better than noobs.
Bringing in new blood is usually a good idea, especially if it refreshes the team and doesn't create harmful tensions.
I don't have much to say about the rest of the points. Yes, keep what's good, what people like, improve everything else.
AA wasn't one of the airlines to see the benefits of the OTAs in the first place. That was up to Delta, United, Continental and Northwest in the late 90's, which spawned Orbitz. Orbitz later built, maintained and hosted AA.com, AFAIK, still hosts it. The 'war' here is going on because AA wants to negotiate rates that are beneficial for itself, but costly for the OTA's. AA wants to pay nothing for OTA bookings, which means the OTAs would lose money providing AA fares. Every fare search costs the OTAs money, as does transaction processing on bookings. AA will take a hit if they pull their rates out of the OTAs. They are hoping to recover that loss by somehow generating more direct bookings through their own site. AA accounts for less than 5% of the major OTA's bookings, so the OTA's really don't care all that much. The OTA's account for a much larger percentage of AA's bookings though. AA can't just start doing what Southwest does. They are too large and have way too many routes. Southwest's model is very different.
Slashdot Mirror
I agree with the statement that a non-brilliant idea is the problem for these developers. I see people draining their life-blood into startups with absolutely no compelling future or growth potential, but somehow manage to talk some investors into paying for their time. They are piggybacking on a popular platform, thinking that a certain kind of application behavior (like smooth scrolling!) is extremely valuable, spending years to develop it while blindly ignoring the fact that they aren't doing anything innovative. 99.9% of humans don't have good ideas. The ones that do usually can't engineer them.
I can only hope that the injunction calls for the end of his rapping for all eternity. Because I think this was the straw that broke the camel's back for me: http://www.youtube.com/watch?v=9iUvuaChDEg After having to sit through that awful experience, I was all "Git 'im and make him stop!"
I think it's even harder when 'all the cool people are doing it'. Soon all of the hipsters will be saying 'hey fuck pandas, man'.
It has become popular to rail against the panda for its unimpressive performance as a species.
So you want to be an android develeper? No. I'm a Motherfucking programmer motherfucker. And garden variety Java programmers? Is Objective C that friggin obtuse?
What does the app do? Does it contain videos of Aria Giovanni, Luba Hegre or Zuzanna from bodyrock.tv? I'm pretty sure they cured any gayness I might have have. The app store isn't a wild west free-for-all (chaps anyone?). I'm perfectly satisfied with my Android.
Agreed. I found that around the age of 25, I began re-reading certain books and re-watching movies to find that I interpreted them differently the second time. Years later I'm still re-watching movies that I forgot I watched. Thanks to Netflix of course.
Cost. Cost and politics are not the same thing. If you threw out every piece of engineering as soon as a new design came along, you'd never have a running system in the first place. Reactor cores last longer than most engineer's careers. They are also integral to the design. No reactor is completely fail safe.
Their advertising and especially sales people and the TOS don't agree. I had an account for a while, but got a backup DSL from ATT. I ended up using only the backup line because even though it was the lowest priced package from ATT, it always worked and was always fast enough.
This is garbage. Mobile gaming, cloud computing, eh rewriting wolfenstein to add ray tracing in the cloud??? I can see why that might make a POC, but Wolfenstein's not even 3D! "We have a red car sitting at a courtyard, which has a very shiny reflective surface. That can be rendered very good." OK, not speaking Inglish isn't a crime. But the editors should catch this kind of thing. UNworth reading.
http://en.wikipedia.org/wiki/Transmeta_Crusoe too much, too early? I still don't understand why Transmeta failed.
We have thousands of Linux boxes. Our admins either slow roll, fast roll, kick or flash them individually or in groups, depending on the situation. Maintaining the servers and apps on them individually doesn't scale in terms of human resources. If an app is leaking resources or otherwise misbehaving, the admins take a snapshot of the app state (heap dump etc) and roll the app. Flashing happens infrequently, usually for upgrades. Patching is just as slow and tedious, so flashing makes sense when you can just schedule an operation to happen on a few hundred servers at a time. Otherwise we'd have to do things by hand incredibly slowly over SSH. We used to do it this way, but that doesn't scale either.
An API or library which attempts to save the engineer from him/herself, but ends up suffocating the engineer by collapsing around him.
"You have the right to remain silent. Anything you say may be used against you in court." You don't have to be a genius to understand the US Miranda rights.
Can you provide an example? I think that may have been the case a few years ago. Hotel and travel search are very competitive. It is a whole lot more difficult to find relevant technical info on popular web tech/languages/frameworks etc that it was a few years ago. Porn, now that is the biggest offender. There are hundreds of fake porn blogs and redirects for any search. Nobody really cares though, since pretty much all of the sites contain porn, which is what you're looking for.
FTA: "Organizations could use the servers to test the applications locally before uploading them to Amazon's paid service. The servers have a preconfigured testing and development environment. Eucalyptus duplicates the AWS APIs (application programming interfaces)." At first, I was like, They're just selling the PowerEdge server + cloud buzzword. However, a local Dev and QA environment for AWS is nice, especially if its already configured to behaving like AWS. One problem with running stuff on AWS is troubleshooting and reproducing performance problems.
I don't use any input device. I control a complex set of metaphorical gestures
The AI part is image recognition of the grid and clues. That's interesting, but it's been done already. I'd like to know how they implemented the solver. The Soduku problem is considered NP-complete. Which is just about the only thing that is interesting about the puzzle. I've never bothered to solve one myself, since I don't think there is anything to learn from it. Actually implementing a solver might be an interesting waste of time though.
Honeywell makes everything. EVERYTHING!! Supercomputers, brake pads, turbines, washer/dryer combos..
I'm bad at patents. Why does the third stipulation kill it?
Say there are 5 million contributors @ $100 (unlikely). What size etching should each get? Lets pretend we have 2 sides of a 10 meter tall monolith to etch. Each contributor would get a space roughly 0.04mm in size in which to etch his name. ...
This needs rethinking.
We developed and released a few "database backed online tournament systems" years before this at Midway Games.
MTN (midway tournament network)
http://www.thefreelibrary.com/Midway's+New+Coin-Op+Tournament+Network+Allows+Players+to+Compete+for...-a062017850
Wavenet
http://en.wikipedia.org/wiki/San_Francisco_Rush_2049 So, STFU, GTFO Mr. Patent Pants.
Golfing huh? Fuck those baby boomers right to Hell. They sucked anyway.
1) Don't spend too much time on development. This may be true for sequels. It isn't necessary to spend a whole lot of time (5+years is a long time) provided that the original was coded well and can be re-used for the most part. 2) Change your engine every so often, and if you can, use one that you've developed yourself. This goes against #1 to some degree. I can't see any good reason to create a new engine unless you are developing on a new platform which the existing engine doesn't like. A really good modular general purpose engine can evolve to take advantage of new platform features (theoretically). 3) Try to keep the team the same, especially if the original was good. There are two sides to this. Some of the original team members will have a context for improving the game. They obviously will understand the design better than noobs. Bringing in new blood is usually a good idea, especially if it refreshes the team and doesn't create harmful tensions. I don't have much to say about the rest of the points. Yes, keep what's good, what people like, improve everything else.
AA wasn't one of the airlines to see the benefits of the OTAs in the first place. That was up to Delta, United, Continental and Northwest in the late 90's, which spawned Orbitz. Orbitz later built, maintained and hosted AA.com, AFAIK, still hosts it. The 'war' here is going on because AA wants to negotiate rates that are beneficial for itself, but costly for the OTA's. AA wants to pay nothing for OTA bookings, which means the OTAs would lose money providing AA fares. Every fare search costs the OTAs money, as does transaction processing on bookings. AA will take a hit if they pull their rates out of the OTAs. They are hoping to recover that loss by somehow generating more direct bookings through their own site. AA accounts for less than 5% of the major OTA's bookings, so the OTA's really don't care all that much. The OTA's account for a much larger percentage of AA's bookings though. AA can't just start doing what Southwest does. They are too large and have way too many routes. Southwest's model is very different.