Señor Developer

About me(diafinger)

Born and raised in a small town in the west of Germany, I moved to Hamburg to study Media Information Science (Medieninformatik) at the FH Wedel. With my previous experience of building simple websites, I was able to land jobs as a student programmer at AOL and smaller companies.

After a year long break in which I studied in Bristol (UK) and lived and traveled in and around Vancouver (Canada), I returned to Hamburg to finish my Diploma (closer to the Master than the Bachelor degree) and start my career. I stayed there until the end of 2012 when I moved to Barcelona (Spain), a great place to enjoy life.

During my professional career I worked for agencies, a browser games company, an internet translation company, a large social network, a web development bootcamp, a bank and have been self-employed.

While my role was usually that of a web developer, I also developed applications, designed and balanced the game mechanics of a football manager and taught and mentored aspiring web developers.

Previously, I worked with languages like Perl, PHP, Java and ActionScript. But since discovering Ruby in 2010 I have worked exclusively with Ruby - and all the other languages and DSLs that come with Ruby and Ruby on Rails applications.

I like Ruby so much that I started teaching it to beginners. First through RailsGirls workshops in Hamburg and Barcelona (where I also organized both). Later through periodical meetups in Barcelona and as a (paid) teacher and mentor in the Ironhack Web Development Bootcamp. I am also one of the organizers of Barcelona on Rails, the local Ruby User Group.

The last 18 months I worked as a freelancer for solarisBank - a newly founded bank and tech company that offers financial products strictly over APIs. The main office is in Berlin, but I worked fully remote from Barcelona.

At the moment I'm on holidays and plan to start working from May 2018 on again. I did not sign a contract yet.

In case you want to hire me

I enjoy working in small companies with small development teams. This setup promises light processes and demands independent workers. People have to show initiative and should be willing and able to make decisions. At the same time it enables transparency and clear communication structures.

I do consider myself to be a product developer thinking of all parts of an implementation and not only ‘my code’. I prefer to write simple, maintainable code and to find a good, pragmatic solution, instead of a complex one. When layers of abstractions or optimizations become necessary, they can be added at the right moment.

I am a strong communicator. Spreading information and connecting people comes natural to me. I do push my colleagues to share more. Be it through the group chat or in pull request descriptions or by creating new tickets. When I am in the office, I use the opportunity to connect with people outside of my team to learn more about the business in general. When I am remote, video chats help discussing complex matters.

I am happy to work in a fully remote position. At home in Barcelona I have a great setup with standing desk, 4k screen, 200 MBit fibre connection and a sunny balcony. Now that summer is approaching I want to take advantage of living in Spain with a ‘Bulli’ and work besides a beach or in the mountains from time to time - when there is a fast internet connection available.

Feel free to offer me competitively compensated remote roles. I am registered as an autónomo (freelancer) in Spain.

Most challenging development projects

2012 at tolingo: integrating Salesforce CRM

  • replacing old PHP monolith
  • new Rails customer facing app
  • new Rails operators facing app
  • implementing a new payment solution
  • integrating Salesforce
  • Ruby services to glue internal and external apps together
  • challenging because of: the complexity of the task, developing new apps, integrating a large external application, big bang release (not the idea of the dev team)

2013 at XING: messages (over 1 billion existing threads)

  • modeling the data structure
  • optimizing queries for speed
  • migrating from old Perl to new Ruby implementation without affecting the users
  • challenging because of: the sheer amount of data, the sensitivity of the data, the search results’ speed and quality

2014 at XING: XTM statistics

  • collecting usage data
  • accumulating existing data
  • creating a data structure optimized for query speed
  • displaying statistics to different user roles through a flexible interface
  • challenging because of: development of the whole feature, finding a maintainable and fast solution without increasing the technical complexity of the whole project

2017 at solarisBank: Business Identifications

  • extracting existing functionality out of a monolith while building a dockerized m/SOA architecture
  • adding new functionality in new services
  • connecting to a terrible XML (non SOAP) API (without good documentation)
  • following banking and data privacy regulations closely
  • challenging because of: constantly changing architecture, unstable API, time pressure to be the first on the market with a solution to identify businesses and their legal representatives in an online process