I work on a 100% Python code base that has nearly 20 million lines of code.  Even with over 1000 developers working on it, I'm still considered the "Python guy".  You can be, too!  There's nothing secret or magical about what I do, I've just had a lot of help from a lot of good people.  Learn how to write production quality code that far surpasses the industry standard.  

A Marine has their rifle, a samurai has their sword, and a dev has their IDE.  PyCharm is incredibly powerful and will increase your productivity and decrease your time chasing down stupid bugs by an order of magnitude, but only if you know how to use it.  I'll help you unlock the power of this incredible tool so you can take your Python game to the next level.   

When was the last time you saw a job add that asked for "strong experience in functional programming"?  Everyone wants experience with "OO" and "OOP".  Yet, developers often speak in reverent whispers about those dangerous Sith-like developers who program in Lisp, a "functional" language.  Bring this power to your Python and find out why the path to declarative Utopia takes a detour through the Dark Side.

Everything in Python is an object.  To a Python developer, Object-Oriented Programming really means "User Defined Object Oriented Programming"!  Whether you just want to know why every class method starts with "self", learn how to properly implement those annoying design patterns that interviewers always ask about, or you want to learn how to write production quality classes: hang out with me and up your "state" game!

Michael Feathers, author of "working effectively with legacy code", defines legacy code as "anything that doesn't have a unittest".  Testing wants to make most developers barf (not rainbows), even though untested code isn't worth the paper it isn't printed on.  I've seen a lot of embarrassing tests -- self.AssertTrue(not None, result), what?? -- even in production code!  Don't be that guy.  Don't be mocked for not knowing Mock!

Test driven development really -- no, really -- means using tests to drive your design.  For an additional 10% time investment up front you save yourself (and your coworkers) from countless hours of agony.  

Interviewing is its own game.  It's almost an entirely separate skillset than actual software development and it can have a dramatic impact on your salary.  It starts with the resume, then often progresses through a recruiter, followed by technical interviews.  I'll take you from cradle to grave through the process and you get paid what you're worth.  

Personal details

J.J. T.

Summary

Technical skills