Author

About the author

What problem are you solving?

Mateusz Radziszewski

This daunting yet meaningful question companions Mateusz Radziszewski in his career. He is a problem solver. In IT industry we often skip “why?” and proceed straight to “how?”. Producing software is a mean of solving business problems. Mateusz plays many roles in solving those problems on different phases of software development lifecycle – like analyst, team leader, architect, developer.

  • Magnitude
    Designed and implemented solutions for corporate enterprises.
  • Domains
    Worked with various domains - including sales, cybersecurity, video streaming.
  • Experience
    He has 10+ years of commercial experience in software engineering.
  • Roles
    He plays multiple roles. Primarly he's software developer and an architect. Secondly team leader and DevOps.
  • Cloud
    A certified AWS solutions architect.
  • Knowledge sharing
    Experienced team leader, mentor, blogger and YouTuber.
  • Technical stack
    Java, NodeJS, PostGreSQL, MariaDB, MongoDb, DynamoDb, Redis, Spring Boot, React, AWS Kinesis Data Streams, AWS SNS+SQS.

What he does?

Leads teams

Mateusz makes sure his project team mates are motivated and enjoy working on the project. Everyone is motivated by something else and key to team satisfaction is to identify those motivators and trigger them.

Sets SDLC up

Proper software development lifecycle is necessary to assure different parties that hold interest in produced software are able to work on it concurrently. Mateusz is experienced in DevOps reponsibilities like setting up development pipelines, creating environments, defining infrastructure, choosing appropriate branching strategy, etc.

Collects requirements

Mateusz learned what questions to ask non-technical stakeholders in order to identify non-functional requirements. When applicable Mateusz also facilitates Event Storming sessions, .

Designs solutions

What make good architecture? One that satisfies architecture drivers and complies with existing constraints. What makes good architecture documentation? One that describes the intent well, is not easily outdated and prevents repeating mistakes. Mateusz uses C4 model along with ADRs to document architecture.

Implements solutions

Mateusz is skilled programmer with focus on quality. While developing he adheres to testing strategy agreed on in the project and performs code reviews.

Evaluates & releases product

Mateusz values getting frequent feedback from customers and appreciate the need to coordinate approvals before releasing incrementally produced software.

Maintains product

Software, once released, is used by many different users. It is not uncommon that some problems manifest themself in production environment. A key ingredient to producing high quality software is making it observable, and configuring actionable notifications.