\cvline{Parallel programming}{Interprocess comunication with unix sockets and D-Bus, multithreading with POSIX Threads, OpenMP and Intel Threading Building Blocks.}
\cvline{Languages}{C (Maemo, Varnish projects as the main language), C++ (Nokia-Siemens Networks main language, Roxar with Qt)}
\cvline{Scripting}{Bash, Perl, Python}
\cvline{Parallel programming}{Interprocess communication with unix sockets and D-Bus, multi-threading with POSIX Threads, OpenMP and Intel Threading Building Blocks.}
%\cvline{UI development}{Qt and GTK+}
\cvline{Platforms}{Linux (Debian/Ubuntu and Redhat at work, gentoo at home)}
\cvline{Packaging}{Debian, Red Hat, Gentoo, SELinux}
\cvline{Continious integration}{Jenkins, Docker, various unit testing frameworks}
\cvline{Continuous integration}{Jenkins, Docker, various unit testing frameworks}
%{Programs}{<Programs>}
@ -90,9 +90,11 @@
\section{Work experience}
\subsection{Current}
\cventry{2+ years: March of 2016 - present}{Tech lead}{Varnish AS}{Oslo, Nydalen}{Norway}
{Currently as a tech lead I'm tasked to oversee the work of 4 very skilled and self-reliant developer in a software company developing multiple tightly coupled projects. During team lead meetings we have to make sure that the projects are in sync and each team's progress and challanges are communicated.
As the responsible of release management, I have enforce that we follow good practices, ensuring the packages we publish in public repositories are not faulty, as breaking packages comes with high costs for many cursomers. This required going through the various stages of quality insurance.
I've played a leading role in modernizing our Continious Integration system's scripts to involve Docker, to make it more automatized, showing problems earlier, while letting developers building custom packages if needed locally.
{Currently as a tech lead I'm tasked to oversee the work of 4 very skilled and self-reliant developer in a software company developing multiple tightly coupled projects, to provide a complete HTTP accelerator solutions.
During team lead meetings we have to make sure that the projects are in sync and each team's progress and challenges are communicated.
As the responsible of release management, I have to enforce that we follow good and modern practices, ensuring the packages we publish in public repositories are not faulty, as breaking packages and downtime comes with high costs for many customers.
This requires going through the various stages of quality insurance.
I've played a leading role in modernizing our Continuous Integration system's scripts to involve Docker, to make it more automatized, showing problems earlier, while letting developers building custom packages if needed locally.
With very tight resources I often ``took one for the team'' by filling in for the developers who were busy with either customers or with high priority projects and helped with bugfixing, testing and customer support.
The technologies being used are: C, SELinux, Jenkins, Docker, debian/redhat packaging.
}
@ -100,12 +102,14 @@ The technologies being used are: C, SELinux, Jenkins, Docker, debian/redhat pack
\clearpage
\subsection{Previous}
\cventry{3 years: January of 2012 - ferbruary of 2016}{Senior Software Developer}{Roxar AS}{Oslo, Lysaker}{Norway}
{At Roxar, as a Qt expert, I participated in the UI's development and maintenance.
I had the chance to work on an enormous codebase (11 million lines). Sadly, most of this was made using worn, deprecated programming techniques, which is partially due to the age of the project (15+ years old).
Feature implementation and maintenance was further hindered by the fact that unit testing was not widely used. I tried my best to change what I can there and in that scope I took an initiative to introduce and spread automated unit-testing.
I also had the pleasure to attend conferences and give an internal presentation about high-level parallel programming techniques (\textcolor{cyan}{\href{https://github.com/dmatetelki/parallel\_programming}{link}}). I'm parrt of a paa-tent, LINK HERE!
The most often used technologies were: C++, Qt, GDB, unit testing.
\cventry{3 years: January of 2012 - February of 2016}{Senior Software Developer}{Roxar AS}{Oslo, Lysaker}{Norway}
{
As I participated in a reservoir optimization and 3D seismic visualization software for oil and gas industry, I worked on developing user interfaces and maintaining core architecture of a large (11M lines) system.
Being part of small team under a lot of responsibilities, I've learned how clear communication cannot be overemphasized between groups of different domain: geologists (who came up with new requirements), programmers (not speaking the domain lingo) and testers (who had different interpretations of the features).
I took the initiative to introduce and spread automated unit-testing as regressions and under-documented behaviours kept on occupying resources.
I also had the pleasure to attend conferences and give an internal presentation about high-level parallel programming techniques (\textcolor{cyan}{\href{https://github.com/dmatetelki/parallel\_programming}{link}}).
I'm a co-author of a software patent on 3D tracking a surface in a seismic block (LINK NEEDED!)
The technologies being used were: C++, Qt, GDB, python, unit testing.
}% arguments 3 to 6 are optional
\cventry{5 years: August of 2008 - December of 2011}{Software Developer, Scrum Master}{Nokia-Siemens Networks}{Budapest}{Hungary}
@ -115,8 +119,8 @@ We used Test Driven Development, unit testing (cxxtest) each subsystem with a co
One of my larger projects was the creation and maintenance of a functional test executor in Perl. I had to create this tool from scratch and provide support for multiple teams on our site.
After becoming a Scrum Master, I took pleasure in introducing scrum methodology not common in NSN and did my best to make software development fun again.}% arguments 3 to 6 are optional
\cventry{3 months in 2008}{Software Developer consultant}{Nokia Research Center}{Helsinki}{Finnland}
{During the time I spent there, I worked on the Maemo project (embedded, Linux).
\cventry{3 months in 2008}{Software Developer consultant}{Nokia Research Center}{Helsinki}{Finland}
{During the time I spent there, I worked on the Maemo project (embedded, Linux) being ``rented out'' by my employer.
As a subcontractor, I had to adapt very quickly to the rapidly changing projects and tasks.
At the beginning, my task was porting an application to use the new library interfaces, which was mostly coding (C, object-oriented C) and testing. During this period I obtained a lot of experience in debugging (GDB, Valgrind).
Later, I became a member of a manager-tester-developer trio as a developer, on a project focused on integrating a trial-set of applets. I had direct contact with the other members of my team and we reported to each other and discussed problems daily. I bundled some applications (creating Debian meta-packages), took care of the installation problems and developed a configuration GUI (GTK).
@ -124,7 +128,8 @@ I was also assigned to maintain the applications. This meant that I and some oth
These tasks mostly had short and strict deadlines.}% arguments 3 to 6 are optional
\cventry{2 years between: 2006 - 2008}{Software Developer}{Blum Software Engineering LLC}{Veszprém}{Hungary}
{In my first job, I worked in a team of 4-5 people, reporting directly to the manager on a weekly basis. Each developer maintained a separate part of the software code, fixed bugs and similar issues and dealt with the integration of that particular part.
{In my first job, I worked in a team of 4-5 people, creating applications for our customer, Nokia.
Each developer maintained a separate part of the software code, fixed bugs and similar issues and dealt with the integration of that particular part.
My task was to develop and maintain GUIs (GTK) and to handle the communication between it and the rest of the program with inter-process-communication (DBus). The programming language was C (object-oriented C, gobject).
During this period, I gained familiarity with development for embedded systems (Maemo platform), emulators, cross-compilers, Software Development kits and debuggers (GDB, Valgrind).}% arguments 3 to 6 are optional
@ -210,7 +215,7 @@ During this period, I gained familiarity with development for embedded systems (
\section{Interests and hobbies}
\cvline{}{\small
\begin{itemize}
\item Sports (powerlifting, football), living an active lifestyle.
\item Sports (power-lifting, football), living an active lifestyle.
\item Hiking and hunting, would like to learn fishing.
