Who is the best candidate for a job coding perl in Tampa

I’ll get right to it:  Is it the experienced programmer who knows exactly how everyone should be programming perl or the less experienced programmer who is willing to adapt their programming style to the existing practices of the company?

There is no easier answer.

On the one hand, the experienced programmer will bring the quality of work up at the company.  However, depending on their personality, they may insist on re-writing chunks of code that might be less than textbook perfect but working perfectly well.  And, as we know, every re-write means more testing.  Not only that, but it doesn’t do the existing programmers morale much good when the new more experienced guy comes in and starts bashing their code as outmoded and difficult to work with.

But is the inexperienced programmer much better for the company?  They are going to make mistakes.  Their code will need more scrutiny by others and therefore be more costly to the company.  And that means less take home for everyone.  Sure, the existing programmers will enjoy the fact that they are still leaders in the organization, but is an ego-boost really worth the cost of training the programmer?

This one’s like economics.  “on the one hand, but on the other, ” what in heck is Bernanke talking about anyway?

For me, it boils down to temperment.  If you’re experienced and cocky – forget it.  But, if you’re a team player and willing to deal with some “inferior” code while you help the team up its game – then you’re in. 

If that’s you, check out our job posting at http://jobs.perl.org/job/14908 (only central Fl candidates need apply)

Hey and let’s not forget the inexperienced guys out there.  Do you want to be a perl rockstar?  Are you willing to put in the hours to learn what  you don’t know?  Are you willing to do a lot of support calls in order to really learn the application.  If that is you, then you should check out our job posting too!

http://jobs.perl.org/job/14908 (only central Fl candidates need apply)

Good Programmers Are Good Scientists

This posting is not just about perl programmers, it’s about all programmers.  So, it applies to all perl programmers.  The kind we are looking for here in Tampa!  see http://jobs.perl.org/job/14908

I spent several years in my twenties roaming the hallways and laboratories (at times bleary eyed from hours at the workbench) at various institutions from Howard University to the University of Maryland and also at NIH. 

What I learned from those experiences was the importance of critical and analytical thinking.  What’s that you ask?  It means being able to figure out with just a few bits of information what is going on in a very complex system.  And that is what a good programmer must do.

After all, it’s one thing to be able to build some super cool stand alone web app, but what about a program the size of a small eco-system?  And, to add a bit more complexity – you didn’t build it to begin with, someone else did and now you’ve got to figure out how to add your code to this intricate machine without farking up the system. 

Of course, after enough tinkering it is inevitable that you will eventually break something.  And, that is when a good programmer puts on thier scientist hat.  Now, you must figure out what is wrong in the least amount of time and with the least disruption.  Because, let’s face it, sometimes testing doesn’t catch the problem and now – drum roll – your mucked up code is live and in production and time is of the essence to get a patch online.

If you are not a scientist – just a programmer – you are going to be a drag on your organization and your team.  Clients will be peeved, managers will be stressed and you’ll be hopping and jumping trying this and that willy nilly much to everyone’s dismay.

A true programmer, a scientist, will remember prior cases that are similar, will identify logical requirements – must be database configuration versus code – or will know that this item will be quickly found in a specfied log.  Through deduction, the scientist will develop a thesis and test his/her diagnosis before jumping into a time-intensive solution that may not solve the problem.

Building code is cool and fun, but fixing code – fast and well – is the sign of a true scientist/programmer. 

If that is you, and you are looking for work coding in perl in Tampa, check out our job posting @ http://jobs.perl.org/job/14908 .

Tampa Perl Programmers – Where are you?

Our company, M.D. Web Solutions, develops an advanced web-application Electronic Medical Record in perl.  We’ve got lots of work to do and we are looking for great local perl programmers.  It’s been hard to find you! 

We’re growing and we can pool together to create a strong perl community right here in Tampa.  Let’s make it happen.

Check out our perl programmer posting at http://jobs.perl.org/job/14908 .

Would you like to be able to meet up with a couple dozen other enthusiastic perl programmers in Tampa?  We would.  contact us through the posting.

Cyril

Great Programmer – How about team player?

Does a planned meeting matter to a programmer? 

Ok, I get it.  When your deep in the woods of code it’s lame to extricate yourself out of for a planned meeting.  After all, half the thrill of programming is successfully storing 100 variables in the RAM of your mind at once and when you leave your task those bits of memory are gone….  And, it will take a good 15-30 min to get them all back in your noggin, so what’s the BFD about missing a planned meeting if at the end of the day the program is completed.  My manager won’t care right?

Wrong.

You gotta talk to your manager.  Call, skype, text whatever – just let him/her know that you are in the woods and need to reschedule. 

If your manager is waiting for you and a few hours later you announce triumphantly that you’re done with the project – you’re still dissing your manager.

Now s/he’s pissed and your pissed.  And all it took was a simple text to remedy the situation.

What about you?  Would you have called?  If so, contact us because your the programmer that we want!

http://jobs.perl.org/job/14908