Hello, My name is Brett Paufler (of www.paufler.net fame) and I like to program (especially in Python, pretty much only in Python). And on the assumption you cannot wait until you reach the end of this document, please feel free to contact me immediately at **redacted** or **also_redacted** (operators are standing by, internet connectivity and/or toll charges may apply, please check with your carrier for full details and any applicable restrictions). Welcome to My Rambling Resume Twenty Five Years (25) Business Experience Yes, it's true. I flat out wasted 25 years of my life doing something I could not care less about for an easy pay check. Why? Well, um, that easy money thing, probably explains it all. While gainfully employed, I learned about sales, business meetings, returning phone calls, showing up, shaking hands, doing what you say, and all that, along with the standard paperwork thing-er-renos (I'll try to keep the business/sales jargon to an absolute bare minimum, here) like cashing checks, keeping accounts, writing letters, and emails, and all the rest. Long story short, I know the bare bones basics (and only the bare bones basics) about how to keep a small office up and running. Heck, I even did that telecommuting thing-er-reno (you'll have to excuse me once again, but sometimes that jargony stuff just sort of makes the most sense) way back in aught-six, before it was fashionable and became all the rage. Accomplished Writer I know! With prose like this, you wouldn't think I'd even need to say it, but I've done tons of writing in my time. Granted, I'm applying for a programming job (Python, I'm drawn to it's sparse verbosity... if you can believe that); and so, a certain awareness of style, syntax, grammar, and structure probably doesn't apply. Anyhow, you can check it all out at my website www.paufler.net, which is closing in fast on that coveted 5,000,000th mark in the overall world wide rankings (if I may be so bold as to toot my own horn... or maybe it's bounced a bit up... or a bit down... or whatever that direction towards 20,000,000 is called); anyhow, attention to detail, countless rewrites (refactoring being what we call that editing/rewrite thing in the literary world) and keeping endless dynamic variables in their good and proper place (something which also goes by the name of character development and/or fact checking in the world of words). Eh, so, I'm proud of it. Never made a dime. And thus, a few years back, it became clear that it was time to move on to something that would (make me a dime, perhaps a bit more). So, Programming I started in JavaScript (actually .Net or something, I can't remember exactly, but I didn't have an IDE so that was hell) and worked my way through the paper.js library (in Notepad++, which was not quite as hellish). If you'd like, there's tons of stuff relating to JavaScript on my website. I think my tutorial on paper.js join() is the only reason the site has a ranking. But then, quite a few years ago (perhaps two, maybe three), I stopped caring about JavaScript (not looking for a job doing that at the present). And so, I moved on. First I may have looked at Lisp (dig those crazy ()()(()()), if you know what I mean), camped out with Haskel for a while (but I know a losing proposition when I see one -- I am no Category Theorist -- though I will be happy to explain why -- oh, yes, I will -- I believe that a monad is less like a burrito and more like a Python @wrapper if you care to indulge -- but then, I'm gleefully happy to be ignorantly wrong, so take the offer for what it's worth), and even spent some time (call it a week, maybe a month) down amongst the SmallTalkers ('Squeak! Squeak! Squeak!' or that is to say, the one time I fired up Java, what I saw was a SmallTalk implementation). Anyhow, none of that is to imply competence (merely time spent in search of the way). Yeah, sure, I sort of know HTML and CSS. But a quick glance at my website (no need to dig further than the front page, but hey, feel free to poke around as much as you like), and one will quickly realize that 'knowing something' and 'knowing something' are two completely different things. And as to 'knowing something', the only language that I really know, care to know, have done anything but merely scratch the surface is Python. And it's questionable at times how much of Python I really know. But I like programming in Python (about as much as I like writing this sort of nonsense that I'm hoping as a resume will suffice). And the simple fact is, I like puttering around in code. And maybe that should lead us into a discussion of my projects. So, historically, my average project has been some sort of image manipulation thing. But I question whether other folks appreciate the aesthetic nuances involved in something like that; so to make it simple, let's just say, I've enjoyed many an hour goofing around and playing with numpy, scipy, and from skimage.io import imread (and now, excuse my while I open Eclipse and ensure that is the correct syntax... and, yes, glory be, it is). All of which leads us to my current project, one that may last for the next few months, weeks, or even years (who knows how long it will take to appease the muses and/or find a paying gig to replace the time sink it has become -- especially after one considers that this is the type of resume I feel compelled to send out). Anyhow, I'm calling that project MetaGenetic Football(TM), which is an AI project of sorts using a simple Genetic Algorithm (home brewed, of course) to explore an Agent Based Model (in many ways, that's just a fancy way of saying OOP) that plays football against itself (two-player pass-receiver mode proof of concept complete, gifs ready for demo at your office or via email sometime soon). Though, seriously (as if I haven't been way too stoic thus far), I really am looking for a paying gig so that I can afford to sink that much deeper into code full time, spend that much more time immersed in it, and gleeful skip further down the rabbit hole that will, no doubt, eventually drive me insane (no smirking, please, the tense is correct, future perfect). TL:DR; I do indeed like to code (and I will bring something new -- that unique individual perspective -- to the table, oh, yes, like it or not, most definitely, I will). But That's Not All! Tell Them What Else They'll Get Johnny! Before I went rambling on about code, I was going to talk about Economics. But Economics is just a spur. It's like a minor. And none of that is easy to understand. So, how about a lifetime of reading? Is that easy to understand? I like ideas. I get off on the abstract. And I was doing research on ABM's (Agent Based Models). And Economics (markets) was one of the popular use cases (MutaGenetic Football(TM) not so much, so who knows why I'm enthralled with that). Anyway, so like, I read a paper... and then, another... and then, another. And it turns out, I find exploring the root causes of the Industrial Revolution to be a fascinating area of intellectually inquiry. But will that last? Will I ever model a market? I don't know. The future is not mine to see. One thing I do know is that I will never-ever-ever get a Phd in Economics or follow up my certificate in Electronics or build any further on my Psych Degree (gads, what a waste of time that was). But, hey! It did turn me on to that Addiction Studies certificate, which built upon this, which built upon that, winding us all the way back in time, down countless years on the path to experience, which for the most was way to weird and wonderful to try and constrain to mere words on the page, until we come full circle, back to the present, where I find myself looking for a paying gig, a job, and a place on your team. Code Until I Code So, long story short, I have every intention of spending the rest of my days punching code, working on projects (the more collaborative the better), and preparing the world for our (can't come soon enough for me) robotic overlords. The only real question at this point (at the end of this here resume, that is) is whether both of us believe that each of us would have more fun (and get further and farther and all that other yada-yada professional productivity stuff) working together at each other's side and on the same team... or not. And as to that last, I'll let you be the first to decide. Python Programmer Content Creator Brett Paufler www.paufler.net