Hi. My name is Micah Tischler.

I write software. I like to solve problems and build interesting things.

Contact

  • +1-855-CODE-BIZ
  • webwork@(my name).com

Smarterer Badges

  • my Smarterer score for HTML
  • my Smarterer score for CSS
  • my Smarterer score for JavaScript

Disclaimer: Since Smarterer's testing approach often centers on deliberately obscure aspects in place of practical usage, I'm not sure these really provide an accurate representation of skills.

Also, the Smarterer badge graphics are currently cached on my server, as they don't seem to be able to settle on a stable API at Smarterer. To verify the scores, click through the links.

Introduction

I'm a Boston-area software developer. I love to build things, and my wide range of experience leaves me well suited to help solve problems on your projects.

Skills

Over the years, I've spent time working in systems administration groups making them tools, developing gateway-oriented network security products, and building out custom websites, backends, and scripts. As a result, I have an intimate understanding of much of the ecosystem modern, network-oriented software lives in. Also, with my background developing security products for mission-critical applications, I have experience with making things robust and fail-safe. To read more about my skills, see my Capabilities section and please feel free to poke around this site's sources.

Disambiguation

As it turns out that googling my name turns up a number of other Micah Tischlers as well as myself, I should mentioned I'm not on Facebook, though Google+ has finally ensnared me. Given my security background, and the vulnerabilities consistently plaguing Facebook, as well as the excess disclosure present in most social networks, I'd like to think this is an understandable position for me to take. G+ is the obvious exception, due to their ACL (access control list) model.

On the other hand, matches regarding Symantec (SYMC) and an IE6 PNG fix script are me. I should probably also mention my middle name isn't Ari, and I've also never coached a youth orchestra.

History

For a quick recap of how I got this way, keep reading.

I grew up with computers. When I was small they were always around the house. By high school I'd already gone through a lineage of x86 systems and was coding in C. As an outgrowth of BBSing, my friends and I got interested in networking and set about bringing the still-nascent internet to our school. We established the link, built and maintained the gateway systems, wired the various parts of the building that'd be connected, and even administrated the network and systems involved, going so far as being responsible for AUP enforcement. This'd be pretty mundane, except we did it in the early 1990s.

During my college summers, I worked at a game company and in the IT group of a large chip manufacturer. At the game company I conducting testing, additional 3D modeling, and helped out with system and network administration. While working at the chip manufacturer, I drew from this experience, making tools for the IT group to use in more smoothly administering their systems, networks, and users, including storage provisioning, user migration, and naming service maintenance.

Througout my time since high school, networking had remained a key interest of mine and gradually transformed into a penchant for network security topics. Firewalls, authentication, tunneling, and other suchs things were the material of my hobby. So, when I embarked on my career, I wound up working on a gateway security device. Initially it was a firewall / VPN server hybrid, though over time it grew IDS and anti-viral appendages.

Eventually I rose from Software Engineer, to Senior Software Engineer, and, finally, to Principal Software Engineer, but even at the very beginning I started out having heavy responsibilities. Within weeks of starting, I was responsible for large sections of the kernel driver, which took care of network controller interfacing, core firewalling, NAT accounting and transforms, and stateful forwarding of any data streams not being routed to the application proxy suite. As the featureset of the project was expanded, my responsibilities grew along with it. With years passing, I wound up taking care of everything from the installer, to a number of the application-data proxies, to the core libraries, to the clustering system. When the time came to integrate with an IDS solution, I even produced a man-in-the-middle TCP implementation which would allow us to feed that component purely contiguous data while also conditioning the network stream itself.

With this kind of activity now my job, my hobbies moved toward web work. The first wave of dotcoms long-since crashed upon the rocks, it seemed that sector would eventually rebound. With this in mind, I developed my markup, CSS, and PHP skills. So, when the business unit I was working in eventually closed in late 2006, I struck out on my own doing web work as a consultant and contractor.

Since then, I've mostly worked with rather secretive clients, but I've solved more than my fair share of bizarre frontend and backend business needs by way of creative PHP and JavaScript solutions, sometimes with some CSS on top.