Experienced full-stack web developer excelling at Django
excelling at Django
Hi! I'm Tomasz. As of April 2018 I'm looking for a new challenging project. So if you are currently looking for a skilled developer, contact me now!
I’ve been using Django since 2008. I started my journey with it when it was still in its infancy (version 0.96). Over the years I’ve kept up with its development, learning it inside out throughout close to fifteen assignments, ranging from short-term consulting engagements to bigger, long-term projects.
The latest project I worked on was probably the biggest and most demanding one in my career—I was a developer of a web platform that issued and administered the policies of a large US insurance company (more on that in the Projects section). That set the bar pretty high and now I’m looking for something just as awesome!
I’m not afraid of taking responsibility of important tasks, I pay attention to details and I always look for new, interesting things to learn and work on.
You can find and meet me in the beautiful city of Wrocław, Poland, where I currently live.
|Back end||Django, South (for Django < 1.7), Celery, Django REST Framework|
|Front end||AngularJS, Knockout, Bootstrap, ZURB Foundation|
|Databases||PostgreSQL, MySQL, SQLite|
|Deployment, automation||Fabric, Ansible, Vagrant|
|VCS/||git, GitHub, BitBucket|
|+ click here to see over 300 tags|
on Stack Overflow
I joined the project (a web platform for issuing and administering the policies of a large US insurance company) in its early stages of development to speed up the whole process. After some months of translating the business rules and requirements into the code, the platform was ready for launching. After that I and the rest of the team provided ongoing maintenance and further development of new features.
I worked as a development team member, and gradually became responsible for many areas of the software (rates, endorsements, document management, complex web forms); additionally I undertook non-programming tasks such as infrastructure management and tech interviews with developer candidates.
During the two years I worked on the project, I became the top committer, with respect to both the number of commits and the number of lines of code.
As the lead developer I was mostly focused on the back end, though I was involved in much of the front-end scripting as well. The front-end scripts heavily relied on the Knockout library. The site was fully integrated with Facebook.
A significant part of the challenge was to implement the code for importing data from an external provider (that included team data, league/division data, fixtures, match results, schedule changes, etc.).
The imported data was a basis for social interactions, e.g. the imported match results were automatically posted as comments to the activity streams of the relevant leagues, teams and players, where they could be discussed (similarly to how it happens on Facebook).
Together with one other developer we built a replacement for a well-known CRM product from scratch, by providing a sub-set of its features while tightly integrating it with other software used by the company. The integration allowed presentation of important data & statistics in a single place, thus saving employees a lot of time and effort.
A list of sites using the AskBot forum can be found here.
I worked closely with Evgeny Fadeev (project owner/lead developer) on the major refactoring of data models to remove duplication and simplify their structures.
I also spent a good deal of time reworking the database migration scripts to make them work flawlessly on all three supported databases (MySQL, PostgresSQL, SQLite).
The goal of the project was to allow automatic two-way communication with employees using text messages (SMS) and voice calls. The system would send messages and make calls to selected employees to collect their responses.
The major challenge on this project was the integration of the Tropo API, and its speech recognition feature.
The module was meant to collect incoming data originating from remote sensors and relied on the scalability of GAE to process the volume of incoming data.
If you don’t want to be tracked, turn off cookies (and other similar APIs) in your browser settings.
The site also uses the following 3rd party services, which use their own cookies (and possibly localStorage and/or other storage APIs): Google Analytics (to track usage statistics), Google Fonts (to improve the appearance), Google Hosted Libraries (to improve loading time) and YouTube (to embed a video).
Privacy policies of the 3rd party services: