Type-casted as a "contractor"

Post #6,630 by tablizer 8/24/01 2:23:17 PM Reply	Type-casted as a "contractor" Full-time positions are trashing my resume, saying that I have been "contracting too much to be loyal". I really don't like contracting. You get puny desks with no leg room, crappy monitors, other people's copy-n-paste speggity code, and an unstable income (include paycheck flakes.) I only did the contracting thing because web projects repeatedly had a boom-bust cycle to them. I have tried to get into VB projects to escape yet more web bombs, but there are too many VB people floating around, and I don't know how to stand out from the herd (in a good way). Everybody wants Java Java Java. Blek! (Not only Java, but 3+ years experience in Java. I could never fake it because Java does not fit the way I think. The days of me picking up things in a snap are over in the OO area. OO stuff takes me 10 times longer to absorb. It's discrimination against table-heads.) It looks like I am stuck forever contracting with flakes for flakes. (I think the use of contractors is proportional to how screwed up a company is. PHB's think plug-n-play if they hire contractors and never give a fudge about having change-friendly code.) (Oops, I screwed up form-feeds again. Sorry) ________________ oop.ismad.com
Post #6,634 by ChrisR 8/24/01 3:06:01 PM Reply	Why not go the dba path... I got turned down for one job from a company with a similar attitude - not so much for loyalty issues but because they didn't think contractors could get into long range planning. Anyhow, if your so set in the table world, I'd suggest going the path of dba type work - Oracle, SQLServer, or DB2. In the long term, that line of work will probably have better pay and stability.
Post #6,666 by tablizer 8/24/01 6:49:11 PM Reply	Re: DBA Perhaps, but it may take a while to get the certificates and what-not. If I bet on MS, then what if MS tanks? And, Oracle takes longer to "get into". Plus, T-SQL/PL-SQL suck as languages. But I guess not as much as Java, eh? I'll think about it more though. Anyhow, how does that solve the "contractor stigma"? Thanks for the advice. ________________ oop.ismad.com
Post #6,694 by ChrisR 8/25/01 9:45:49 PM Reply	Just a random thought Perhaps, but it may take a while to get the certificates and what-not. Yes, it can take a while to get certified, but a lot of knowledge in databases is not specific to any particular vendor - i.e. the design is similar, just the implementation details vary. I was just suggesting that if you're not current on VB (or .Net right around the corner) , and with your proclivity to database based solutions, time spent learning these products may be more productive both in the short and long term. If I bet on MS, then what if MS tanks? Well, there's always Sybase - MS hasn't managed to totally screw up the language just yet. SQLServer will be around for quite some time, the only question is how far it can scale up. SQLServer is definitely on much more solid footing than VB. And, Oracle takes longer to "get into". Programming is all about challenges. If it's not challenging, then it tends towards being boring. Yes Oracle takes longer and has many more subtleties, but it also scales and pays better. Consider it an investment. Plus, T-SQL/PL-SQL suck as languages. I agree that they suck - but then I believe that all programming languages suck. I'm of the opinion that writing elegant code is not the payoff for our profession - it's merely a side effect of other goals. Constructing things, having ideas realized, solving problems, that's where the payoff is at. Whether I do it with a sucky language or a beautiful one really doesn't matter in my line of thinking. You do the best with the tools at your disposal. A better language allows you to deal with stuff at a higher level, but in the end, programming is all about discipline and rigorousness - well at least it should be. :-) Anyhow, how does that solve the "contractor stigma"? It doesn't solve it head on. I was expressing the opinion more along the lines of your lament of VB and Java. I personally believe that VB and .Net are carreer dead ends. The profit curve for Java is also no longer logarithmic. I think longetivity is best found in the data and process side of the business. Front ends come and go with the latest bells and whistles. The stability is best found on the database and business process side.

Welcome to IWETHEY!