I recently revealed my first start up, Cross Section, which is a revolutionary online business intelligence tool. It's not quite ready yet, but you can learn more by clicking on the button below
Anything that I have given away as free software or any contributions that I have made to free software projects.
Flask Foundation is a simple template that I wrote in order to initially teach myself the Flask web framework for Python. I was frustrated that all of the available examples of Flask code were very platform and deployment specific and very little could be learned from the convoluted code. So, I decided to build a simple, solid foundation for flask applications, built on MVC using the most popular Python libraries, that you can easily construct any Flask website/webapp off of. My solution is different from most Flask frameworks as it does not assume anything about your development or production environments. Flask Foundation is platform agnostic in this respect. Check it out here.
I am an official member of the D Language team. I have contributed many changes, closed a couple of bugs, and made some new additions to the standard library of the D programming language. To see a list of all of the merged pull requests I have on the standard library, click here, to see all of the open pull requests click here.
date-parser is a translation of the very popular date string parsing functionality of the dateutil library to D, and it can be found here. It started out as just a port of the existing functionality, which only resulted in a 2x faster library than the Python version. But, after optimization and translating it to idiomatic D code, my version is 10x faster than the Python version with space still available to optimize.
Mastering Flask is a programming book that I wrote for users of the Flask web framework for Python. It is designed to take the reader from simple web pages with Flask to large scale web apps.
Starting from a simple Flask app, the book walks through advanced topics while providing practical examples of the lessons learned. After building a simple Flask app, a proper app structure is demonstrated by transforming the app to use a Model-View-Controller (MVC) architecture. With a scalable structure in hand, the next chapters use Flask extensions to provide extra functionality to the app, including user login and registration, NoSQL querying, a REST API, an admin interface, and more. The, the book covers how to use unit testing to take the guesswork away from making sure the code is performing as it should. The book closes with a discussion of the different platforms that are available to deploy a Flask app on, the pros and cons of each one, and how to deploy on each one.
Packt Publishing released a book on Flask web framework best practices, The Flask Cookbook, and I was chosen as one of technical reviewers for the book during the writing process.
All of the things I have worked on for my job or I decided not to release its code.
In 2013, I was (and still am) working for a company called Apollo America. Apollo has a morning stand-up meeting across the entire company, but at the time, everything in the meeting was done on paper. Graphs were drawn by hand on giant post-it notes that were stuck on the wall, and manually updated every day. News items were written on small sticky notes and stuck onto the giant ones.
Needless to say, this was a lot of maintenance, and it was hard for anyone more than 10ft away from the notes to see anything. So, my first task at the company was to digitize the whole thing into a web site and have it displayed on a huge TV in the cafeteria where the meetings take place. Using Flask for the server, and Backbone.js for the client I made an interface where
The effect of the change to the electronic version was much more involvement from everyone in the building during the meetings. The chart and KPI screen made it so everyone in the company knows where it was in terms of hitting this months budgeted target and staying profitable. Things were visible by everyone in the room, and there was a certain "coolness" factor that encouraged people to participate by adding news items and talking about things that needed improvement.
Another project at Apollo America was to make our work order process for scheduling manufacturing paperless. Scheduling manufacturing was handled by putting printed work orders in a pile at the start of each line in order of when they should be completed. The problem with this system was that it was very tedious for people to schedule things because it required going back and forth and looking at all of the sheets of paper, or looking at a long list of orders in a spread sheet which didn't include all of the necessary information.
I was given the task to make it easier to schedule orders and also take the opportunity to gather more data about the performance of the line. I decided to replace all work orders with iPads. Each of the manufacturing lines would have an iPad at the end of the line which lists all of the orders in the order which the foreman decided on. Each of the orders had to be marked as started when work on it begins, which would start a timer, and stopped when finished. The resulting time is then sent to the server and then saved. Each of the orders also has the ability to be marked as un-completable or that the order is causing downtime on the line, each of which is also timed and sent to the server.
The foreman would have an iPad which lists all of the lines and the open orders and decides on what to work on today and what not to, and in what order. There is also an interface which shows all of the orders scheduled for today and their status.
The end result of this system was the ability to completely map out what the factory did in a day, how they did it, how long it took them, and where there was any lost time and what caused that to happen.
When I started at Apollo, the engineers were storing product component metadata in three places
Needless to say, it was hard for engineers to get info on anything, especially when drawing schematics. All of the different locations got out of sync with each other because it was too much work to edit all of them at once. The engineers wanted to have all of the part information consolidated, so my task was to take all of the information to store it in one database, make it easy for anyone to see and edit part information, and to make the information available to the schematic drawing software.
I created a interface that allowed for easy filtering and editing if the part information. Users could click on any part to instantly update it's info. Also, users could, for example, filter by all LEDs which had a cost greater than or equal to 2¢. Users could also stack filters, so you could search for all parts which have more than zero quantity on hand and have the word "green" in its description.
When decided to create a promotional site, I took it as a personal challenge to see how fast and small I could make this page while still having a responsive, modern design. Not including images, this site is roughly 46kb and it loaded on your computer in (again, not counting images).
The ability to cut down load times is a very important skill for web developers. Studies have shown that what would seem like trivial differences (in some cases a half second) in page speed can cause 20% of your users to leave your site before it even loads  .