If someone feel completely lost when he learns a new language, even if he specialize, that would scare me.

If a company want someone to do a quick job in short term (1 week – 1 month let’s say), then you might want someone who can be productive technically from day 1. Still you don’t eliminate the non-coding task like analysis, learning the business domain, etc. and even further, you often have a learning curve of how they used the language(s) in their architecture (coding style, framework, philosophie, etc.). In other words, only knowing the technologies underneath is far from guarantying someone to be productive from day 1 when diving in codes.

It might be reassuring for a lot of people if the ressource know the techno, but if you are looking for a long-term team member to bring the team to the Stanley Cup (I’m Canadian, eh!), I would suggest to take the best developers instead of only the ones who know the technologies upfront. Easier said than done to evaluate, but you can evaluate what you search for without necessary focus on the technology you *currently* use. I may be and/or sound judgmental, and I do know some people on the market who still struggle with this, but for example, if your future developer can’t solve a simple recursion problem, in the syntax he wants, then it smells bad. There is other factors than skills or potential skills that might make someone fail those kind of tests of course.

All in all, I strongly believe that a good developer, with reasonable time for it, will learn the technologies and in the long run should make your team way more productive than an average one. So my suggestion would be that if you got a very interesting resource that don’t know your techno, find a way to evaluate his high-level/abstract/problem-solving/etc. skills, and take a decision based on this rather than the techno he had the chance to touch in his past.

Lot of people also suggest to learn/experiment-with a new language regularly (e.g., one per year), as you can see different ways of doing and become a better programmer in your language of choice. Similarly to playing a lot of sports will often make you better in your favorite one as you will develop other skills that you may use creatively in your chosen one(s).

Great article, btw. Keep ’em coming!

I have a dBase picture framing system that I wrote in the 1990?s that has 1 main calling program and 77 called sub-programs. I also have all of the database tables for the system. The program is initiated by double clicking on the fc.exe and it runs fine (except for the small screen size). My problem is that I would like to begin again working with the system but it has been 16 years since I worked with it and I do not remember what the DOS command was to create the .exe and I need a good version of dBase III or a version that will work. I need to convert the screen size from the small screen size to today?s monitors. Do you have a suggestion about, first, the command line to create the .exe and a good way to convert the screen size?

On another level, of course, you’re 100% right. There’s no excuse for the way Prograph was handled. No excuse.

I hear Apple is bringing it back, which is a start.

Sucks, but so does a lot in the industry.

Now… time to buy yourself a cheap backup drive!

I did the latter. Thanks for saving me the money. It was a close call, but the company you mentioned (Hard Drive Recovery Group) were way cheaper than I thought they’d be.

Big thanks!

Personally, I use Recover My files program to restore back lost data from my computer. There are other as well, you should try the demo version before getting the full version.

thanks for the article