Tag Info

New answers tagged


No, you are not professionally obliged to provide support for a previous employer. If you want to do this, make sure there's a contract in place to compensate you for the time you spend. It may also be that you could offer to come back for 1-2 weeks and train your replacement (as it were), naturally at a suitable fee. What I would say, though, is that ...


Here's a potential e-mail to craft*; Sorry, I'm very busy right now with my existing contracts and not regularly checking my e-mails. If you have a support request for a product I used to work on, send a message to "support@mattharrison.com", so that we can discuss setting up a support agreement. If it's urgent, be sure to prefix the subject with ...


You are in no way obligated to help them. Whether or not your former employer have realized it, they have taken a low cost/high risk decision by having only one developer work on the software. That was their (perhaps uninformed) decision, and now they are paying the price - you should not. If you feel like helping them, you should make a support agreement ...


If you havent signed a contract with the company/clients about offering help to them in future, then you can say no to such calls. There is generally a agreed support time between client and developer. The developer is supposed to help the client till the support time is breached.


Programming is certainly a Concept and it won't bound to the language, but you might bind yourself to a language as a Programmer. More you learn the concept, less you face the limits. I agree with the quote.


It takes a while to become really good in a language, to know all idioms, to know the most important parts of the library and how to use them. It's perfectly fine to be an expert programmer in only one or two languages. Not everyone has the time to follow every trend that emerges. Aside from that, being a good programmer is more about knowing the concepts ...


For a programmer with enough experience, a programming language is a tool which has strengths, weaknesses, relevant use-cases, and syntax. For such a programmer, when faced with a problem, he does not choose the technology to use from the set of technologies he already mastered, but rather according to the technology he believes is the most appropriate to ...

Top 50 recent answers are included