About us

This is Allegro’s public-facing tech blog. We use it to share our knowledge with the community and to tell others what our work at Allegro is like. It is also a tool for promoting Allegro to potential candidates. However, we try to be objective, and we explicitly avoid any kind of excessive propaganda. We write for smart people who are good at telling genuinely interesting and useful information from corporate.

Goals:

  • Creating a technical blog valuable for the community. We focus on development and devops.
  • Letting the community know about events we organize or take part in.
  • Maintaining the image of Allegro as a technical leader and a place where great engineers work.
  • Highlighting our achievements but also describing our failures, for example by publishing outage postmortems.

Our editors:

  • Bartosz Gałek

    Editor

    Software Developer at Allegro, engineer with devops flavor. Believes that there is always a place for improvement; likes to try new technologies and languages. Open source fan and occasional contributor.

  • Daniel Dopierała

    Editor

    A Software Engineer who just likes to do his job well. Specializes in backend technologies on JVM, but does not shy away from frontend and big data.

  • Katarzyna Zadurska

    Editor

    Frontend Engineer at Allegro Ads. React enthusiast with passion for good quality code and attention to detail. Genuinely excited about code review. Willing to learn and discover things, whether it is code-related or just a new spot with eclairs.

  • Michał Kosmulski

    Editor in chief

    Michał is interested in all things high-performance, whether it be low-level stuff like analyzing how OS caches affect I/O operations or high-level like proper application design and functional programming. At Allegro, he has worked both as a software engineer and as a team leader, in finance and advertising divisions.

  • Wojciech Poniatowski

    Editor

    As Product Team Manager Wojciech builds product teams and manages Product Managers within Allegro’s technology. At our Tech Blog he provides a bit of business perspective.

Former editors:

  • Bartosz Walacik

    Former editor in chief

    Software engineer with 15+ years of professional experience. He focuses on lightweight and modern technologies around JVM. At Allegro, he works as a development team leader. JaVers project lead. Spock advocate.

  • Mateusz Krzeszowiak

    Former editor

    Webperf Team member. Likes to constantly optimize and improve existing solutions. Finds it hard to stop talking about his work and sharing knowledge.

  • Mirosław Gołda

    Former editor

    Mirosław is a software engineer with programming experience in Java, PHP, JavaScript and Node.js who joined Allegro Group in 2011. He likes playing around with various programming languages and technologies. Recently he’s experimenting with various automated testing tools and frameworks.

  • Piotr Orłowski

    Former blog founder

    Software Development Manager with over twenty years of experience in IT and e-commerce. At Allegro he manages the work of 150+ engineers taking care of their continuous substantive development, he is responsible for the technical quality, stability and efficiency of the Allegro platform. He likes simple solutions which gives more possibilities than originally planned :)

  • Tomasz Gospodarczyk

    Former editor

    Frontend Engineer and team leader in the team responsible for offer page and navigation components at Allegro. Web Performance enthusiast and occasional music creator.

  • Waldemar Panas

    Former editor

    Engineering manager with a rich background in professional software development. Since joining Allegro in 2018, Waldemar has been at the forefront of driving innovation and excellence in software engineering. His role extends beyond the confines of Allegro, actively engaging in the wider tech community as a co-organizer of the Java User Group in Poznan and GeeCON, a prominent conference focused on JVM technologies in Krakow and Prague.

Unassociated reviewers:

We'd also like to thank all the people, too numerous to list here, who reviewed articles without being formal members of the editorial board. Just like code reviews, article reviews are open to everyone at the company and often people just drop in when they feel competent to discuss a topic. You can't overestimate the value of such spontaneous help.