Proof that Sega still knows how to make great games:
698 karma · joined March 20, 2007
Proof that Sega still knows how to make great games:
There's no reason that Nintendo couldn't follow suit. Pride is probably the biggest obstacle preventing that from happening, but if/when things get bad enough, they'll make the switch.
Are there people who really want to work at all hours? Maybe eager students right out of college.
Personally, I'm at the point where if I'm going to be working at all hours, I'd better be one of the primary beneficiaries of that work.
1. Steve Jobs
2. Dennis Ritchie
3. John McCarthy
I figure, if you're bootstrapping a business on the side, you're probably looking to get out of working for your employer anyway. If your employer can't tell the difference between when you're giving them your most productive hours and your least, I wouldn't consider it to be shortchanging.
The usual pattern is work -> personal time -> sleep. Why not reverse personal time and sleep? So when you come home from work, you sleep (thus getting an 8-hour rest), wake up around 2am fully charged and then work on your bootstrapped business during your personal time. You'll get more than 2 hours. Finally, work time comes last.
This way, your business gets your best energy and effort for that day, you get more rest, and work won't notice the difference.
I would have gone just to see the looks on their faces.
Cringely's post is pure link bait (or even flame bait). I feel sorry for those who read the post as if the author is knowledgable about this subject matter. Picture the IT manager or CIO who reads that and thinks their continued investment in Java as the "one language to rule them all" was a good decision. That person would be better served reading Steve Yegge's platform rant from earlier today.
No one language is equally great at solving every foreseeable problem. The only good answer is not to be afraid of using multiple languages/technology stacks and be prepared to replace existing pieces with ones that are better when the time comes.
If hours are the chief measurement, then you can stretch things out to make it take more time. I'm sure this is happening in businesses the world over anyway.
I'm generalizing, but It seems as if institutions who have made a living researching treatments to major diseases don't seem that interested in cures. That could threaten their existence. So they put their money in providing hospital services instead of research. They can't get government money for research grants if their idea for research seems too unorthodox.
In the end, it's about protecting jobs and finding a way for you to live longer with the disease.
Don't forget, that 10 years of experience could just be 1 year repeated 10 times. A cardinal number of years doesn't always equate to increasing breadth of knowledge.
I love the fact that they come up with the best solution that solves the problem based on their skill set at that time; and when either their skill set improves or the technology improves, they actually go back and replace the current solution with a better one (even if the better solution requires a change of programming language)!
It shows the true power behind hiring the right people. It's not as much about the number of years of experience with a technology stack, as it is proof of a person's ability and willingness to learn new skills.
Although I agree that SSH keypairs feel more secure than a username/password, it would make setting up a new machine for development a lot easier than generating a new SSH keypair and adding it to my GitHub (or any other git server) account.
Nothing wrong with that.
We use Oracle, MS SQL Server, and Sybase because that's what the vendorware we use requires. We do have some open-source software that uses MySQL for administrative purposes.
Seems kind of silly to me. If your better employees regularly leave your company, than you probably have more deeply-rooted organizational problems that need fixing.
I haven't looked at Rackspace too much. Is deployment as simple as a git push, like Heroku? How's their pricing compared to Heroku? Is rolling your own scalable Rails architecture using AWS directly too complicated?
Is there an actual difference between these methods?
I guess that means my current job ranks low according to the criteria in this article.
At your employer's workplace, you don't have that control. You can be interrupted at any time by anything.
You don't appreciate that flexibility until you have to use headphones and music to drown out your co-workers' inane personal conversations.
Management is not excluded from this either. They have to:
1. know, in depth, the business they are in and the tools they use (or could use) to achieve their goals
2. listen to what their team tells them and provide an environment where they can do the job right
It sounds like there was a lot of micro-management and putting out fires in this case.
But seriously, I understand that option A almost never pays that well and is usually not guaranteed. For example, working for stock options that you'll most likely never see vest.
Also option B is not guaranteed to make no money either, and at least you like option B. So, I'd take B too.
I'm not saying that you can't have a mixture of both, or transition from one motive to the other, but most people's first thoughts are about themselves, others tend to come afterward. We are afraid to admit this in public, but I think we can all agree it exists.
So what's wrong with seeking personal happiness first? Does that preclude you from being more altruistic later in life? If you can put others' needs first, more power to you, but that doesn't make those who cannot worse people.