clickonchris
The memory management bit Prasad references is a big deal too. Can you imagine not being able to release a feature that you've invested a lot of money into because you've got a performance problem or crashing issue that the tooling is not good enough to let you solve?
Corporate life doesn't agree with this fellow. Assuming he's not facing any lawsuits it sounds like a great time to launch his own software firm (where he outsources the work of course).
Or - he could go into consulting to show companies how to effectively do outsourcing.
update your Gemfile and set the version you want. In my case:
gem 'rails', '3.2.10'
locally, run
'bundle update rails' which will update your Gemfile.lock
check-in and deploy your code. If you are using capistranso, the default 'deploy' task should handle everything for you. Otherwise, run 'bundle update rails' on your production server.
update your Gemfile and set the version you want. In my case:
gem 'rails', '3.2.10'
locally, run
'bundle update rails' which will update your Gemfile.lock
check-in and deploy your code. If you are using capistranso, the default 'deploy' task should handle everything for you. Otherwise, run 'bundle update rails' on your production server.
Making Software that Doesn't Suck
Why We Test: an article for developers, managers, and executives
What are some techniques for getting a unique identifier for different devices?
For me it is a question of cost/benefit analysis. What real value do you get out of being able to write super mathy algorithms when the solution is often a Google search away? More importantly, programmers get paid to build software that works, not to recite algorithms. (that's a generalization. Google & Amazon probably care much more about in-depth knowledge of algorithms but I consider them the exception).
Take the search algorithm example. Don't pre-optimize. I'll use the simplest linear search I can to get the job done, and if needs be, look up a faster algorithm to speed up the search.