Slashdot Mirror


User: twqqis

twqqis's activity in the archive.

Stories
0
Comments
1
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 1

  1. Don't take their crap & other suggestions on How Do I Get Back a Passion For Programming? · · Score: 1

    Before I respond to the passion thing, I want to ask you and all the responders here, in an industry where there's an under supply of techies
    - Why is it that we take their (employers) crap?
    - Why is it that we put up with their bad management?
    - Why are they calling the shots
    etc...

    Are you insecure about your ability? scared that you wont be employed elsewhere? WAKE UP! THIS ATTITUDE IS PART OF THE PROBLEM AND CAUSING IT TO CONTINUE!
    If you put your foot down, if EVERYONE did, and showed their employers that WE call the shots, else WE LEAVE, then they would change their ways. Isn't that obvious? We need to stop being timid, and start being professional. Treat me professionally and I'll return it. When that happens you will be taken seriously. It is our responsibility to wake everyone up, you need to shake those techies around you that's SLEEPING! I just cannot beleive people would put up (wrook's post) with Employer:"If you want to program outside of core hours you should be doing work for us". !!?? Screw them, that is unacceptable, you don't own me, THIS IS MY LIFE! You have to stop and realise that you don't owe them anything, yes they pay you to deliver certain things, but if you don't enjoy what you're doing then you move on. that's it.

    Okay. Passion.
    I've been through this kinda thing a couple of times, and I figure that we confuse the source of the problem.
    Developers often say "I didnt get anything done today!", when they mean "I didnt write any code today!" - ie, what is it that you want to do, what is it that would make you happy? Do you want to write code? Do you want to write more code? Do you want to work with other tech, or maybe try new technologies? Do you want to be more involved with the project instead of _just_ code? Do you want to make decisions, instead of just following instructions? These questions would lead you to understand what you need to ask for at work (dont use attitude, be realistic, and factual), or what you need to look for when you're out doing interviews. An interview is not just a place where they check you out, but where you CHECK THEM OUT, ask them all those questions regarding all those things you've figured you're interested in, ask them question regarding their setup so you can understand how they function and if that would be what you want! Take control!

    One other thing, get a grip on the average performance of the team. When you're given something you dislike, perform at that level. Have a neutral attitude. BUT, when you're given something you like, perform like your life depended on it, show energy, enthusiasm, etc that is way above average; if your management are somewhat smart, they'd recognize that, and hopefully realise that they can use that to their advantage...AND you'll be happier.

    OR, look for something in your code base (or whatever area you're interested in) that you;re interested in, and that you know been sitting on the backburner for a while, and solve that in your spare time. do a good job. like the previous paragraph, hopefully they'll realise that you could be much more productive in another way...

    else, get another job :)

    And this thing about "accept a crap job, and doing what you love after work like OSS" is bull. you're spending most of your woken hours at work, it better be good. (and jeez, how about a balanced life?! After work I really want to enrich my life with other things; learn to cook the perfect tenderloin, build myself a nice cupboard or work on my bike in the garage, go ride my motorcycle, go for a beer with friends....!)
    get involved with forums, user groups, projects that interest you - this would probably lead to an opportunity that would get you excited. try it.