Comments on: Finding Python people is hard.

By: jnoller

jnoller — Wed, 23 Apr 2008 16:18:37 +0000

Why you gotta be like that :)

By: jnoller

jnoller — Wed, 23 Apr 2008 12:18:37 +0000

Why you gotta be like that :)

By: PKKid

PKKid — Wed, 23 Apr 2008 02:43:09 +0000

Does PEP8 say anything about white space between big chunks of dense code snippets?

By: Ryan Freckleton

Ryan Freckleton — Sat, 19 Apr 2008 01:34:49 +0000

It just so happens that I got hired in a QA automation position because of my python experience.

Sadly, management considered the lack of python developers such a big issue that we ended moving to Java.

I'm located in Colorado (front range), but I'm not tied down, if you guys are still hiring after December ;-)

By: lozinski

lozinski — Thu, 17 Apr 2008 14:51:23 +0000

Post your resumes online.

python.jobmart.com/Register

By: sujith

sujith — Thu, 17 Apr 2008 13:50:40 +0000

i have 2 friends kader and jayesh
they do python well

By: tshirtman

tshirtman — Thu, 17 Apr 2008 07:56:21 +0000

Yes testing is a real challenge, and you can always make tests more precise, complex, and complete, your example is interresting, certainly a mind blowing problem, wich need more complexe test procedure than unittest I think.

I will try to be more skilled in this area as there are interresting problems to solve.

a last question: do you test your test code? ;)

By: lozinski

lozinski — Thu, 17 Apr 2008 05:18:59 +0000

I count 1138 python developers listed at
http://python.specialtyjobmarkets.com/Resumes

By: Jerry

Jerry — Thu, 17 Apr 2008 00:58:24 +0000

I am in the midwest (Iowa). I only mentioned the work-at-home option in lieu of finding a company locally that would be looking for a Python developer.

By: jnoller

jnoller — Wed, 16 Apr 2008 23:23:55 +0000

See, “testing” is such a generic term that I don't think it gets the credit it deserves.

Take for example – the perfect cluster. Ignore what it does for a moment, but imagine how you would test it. You would have to make a test that proves on a basic level, it does what it is supposed to do (store a file, compute pi). But how do you break it? How do you make sure that under no circumstances (random power failures, flaky processors) that it never stops doing what it is supposed to be doing?

How do you prove it scales? How do you prove that is truly does what it does? Someone could reply “well, I ran it on my machine, and the units passed” but that doesn't show it's true capabilities, nor it's limitations.

Someone once told me – QA is the identification of Risk – i.e: “you can ship this, but the following are it's limitations” – everything that you do with software once you are done compiling it (which is itself, a test) is a test – from the moment you look for security holes, to the second you push it to a live site.

Test driven development is a logical extension of this – write tests that define what the product is capable of – then write to that. I don't agree with 100% of that, as I think it is possible to write a test no piece of software will pass, but you get the idea.