| a) Share with us example(s) of stuff you've done. so far you have hidden behind doubt, can't give you pity till I see something pitiful. :-) (if you are nervous, preface it with, "please, be gentle") b) Maybe the platforms/technology/projects you've chosen aren't clicking with what you want really to do, just because its popular doesn’t mean it works for everyone. c) Sounds like you might trying too hard, relax your self standards a little and concentrate of getting something running to your satisfaction, don’t worry about tight/pretty code. Once you like how it works, go back and re-factor if you feel the need. c-2)Take one of your earlier projects and revisit them, might have some new insights on how to prop up some earlier work. Sometimes looking over my old code is a mixture, of "I can do that so much better now" and "wow, I wrote that?!" d) you might be REALLY good at debugging from what you say. e) you know, you can build stuff on your own. Reinventing the wheel is also something to do, maybe you can make a spiffier one. f) maybe the jobs you are applying for are too high for starting out. Or maybe you should take a non-developer position and work your way up through the company (this is how a lot of folk do it, including me). g) network, it's not always what you do but also who you know, even in non-teach, someone might know somebody... |