Re: Euphoria jobs?
- Posted by Irv Mullins <irvm at ellijay.com> Jun 19, 2001
- 423 views
On Tuesday 19 June 2001 00:51, Lewis Townsend wrote: > Hello all, > I am quite aware of the UNLIKELINESS of finding a Euphoria job that's why > I've been looking for a VB job. I don't need any discouraging comments > right now. I know there ar a lot more VB jobs out there but most of them > require a lot of experience and more in additional technologies that can be > used with vb. I have aproximately 2 years vb experience but more than 4 in > Eu I think. Hi Lewis: If someone came to me and asked "Do you have any hammer jobs?", that would worry me. If instead that person asked "Got any work for a good carpenter?", then he or she would have a much better chance of getting hired. And I wouldn't feel the need to wade thru an almost endless list of possibilities: "Can you run a skilsaw, too?", "How about a level - ever used one of those?" :) If you're specifically looking for a job with a company that has a large staff of programmers, then you'll obviously need to be able to work within the 'system', that's why _some_ jobs specify VB, or COBOL, or C++, whatever is commonly used at that shop. Often, however, such things are specified because a clueless HR person has found those buzz words in a book and thinks they will somehow weed out incompetent people, or because the CEO's nephew uses VB and creates snazzy demos. Either way, programming jobs with large companies are becoming harder to get. There are lots of high-tech businesses failing right now. And frankly, these jobs never offered much except good pay which barely made up for the aggravation, anyway. I suggest a different approach: instead of looking for someone who needs a hammer operator, look for someone who needs a problem solved, and suggest that you, yourself, are just the person who can solve that problem. That's what I have been doing for the past 20 years. I rarely have a client express any interest in what software I am using to solve their computing problems. Most don't know or care at all, as long as the software does what they need and doesn't crash. It is easier and more productive if you begin in familiar territory; some type of business that you are already familiar with. What kind of *non-programming* work have you done in the past? It also helps to concentrate on smaller businesses, those who can't justify a full-time programming staff. They'll appreciate your efforts more, and there won't be an entrenched bureaucracy to get in the way of you doing your job. Besides, it's much harder to lay off their 'only' programmer. One final point - never, not once in the past 40 years, have I gotten a good job from a want-ad or by using a placement service. If you rely on those to get work, you're in for a disappointment. I'll elaborate on the methods that _do_ work, if anyone is interested. Regards, Irv