Speaker

Michał Michalczuk

Michał Michalczuk

Senior Software Engineer & Consultant @Tektit Consulting

Gdańsk, Poland

Actions

Senior Software Engineer and consultant at Tektit Consulting. IT trainer at Infoshare Academy. Previously worked on Jira Cloud and Atlassian Forge.

He talks and records content on front-end and web development topics. One of the talking heads on “Śniadanie z Programowaniem” and “Z Archiwum IT” by JustJoin.it

👉 michalczukm.xyz

Area of Expertise

  • Information & Communications Technology

Topics

  • JavaScript & TypeScript
  • TypeScript
  • Frontend
  • Frontend Engineer
  • FullStack Development
  • Front End Testing
  • NodeJS
  • Node

Benchmarking tsc - why compilation takes so #!@# time!!??!

Have you ever wondered what happens in the background as your TypeScript project grows and evolves, transforming from a simple sketch into a complex system?

As line by line, function by function, your development environment starts to slow down, and the processor works at full capacity, slowly cooking the DX frog - where exactly does the problem begin? Why does TypeScript compilation take longer and, most importantly, what can be done about it?

During the presentation, we will reveal the backstage of the TypeScript compiler's work. I'll show how to profile the compiler, look for performance bottlenecks in the compilation process, and effectively optimize your workflow.

Is it possible to fall in love with your code and work environment again without the frustration of waiting for compilation? Let's find out.

The power of mobile web browsers

Once upon a time, Progressive Web Apps were a buzzword.

In the whole discussion about PWA I've missed one thing - deep dive into modern browsers' native capabilities. Native APIs that can give you access to smartphone equipment, memory, OS parameters, give you ability to connect external controllers, etc.

During my presentation, I will show you a less-known browser API and demonstrate how to get information about users' phones. The presentation will take place directly on your device so you will see real examples, not cold facts.

Warning: Please take your smartphone and connect to the network for this presentation

TypeScript Template literal types - who need it anyway?

A long long time ago TypeScript 4.1 brought major change - introduced Template Literal Types. After this release examples like type-based parser or type-based SQL engine spawned like crazy. In the next releases, we get even more Template Literal Types features!

Cool. But it doesn’t answer our question - “Who needs it anyway?”

I’ll talk about Template Literal Types, and we’ll check more real-life use cases for them than the mentioned type-based SQL engine :)

Less is more? Insights from a 4 day workweek

A 4-day workweek. Sounds idyllic. That's exactly my week - the whole company has Fridays off. From Monday to Thursday, we work 8 hours each day, managing to wrap up our work in 32 hours.

Wow. Behind this wow effect is an appropriate organization culture, good goal setting, and alignment with clients who work the regular 40 hours.

But is it always wow? Isn't there a temptation to "crank up" more hours when a project is on fire? Are there any hidden costs and pitfalls?

I've been working this way for over 2.5 years, and I'm eager to share with you my thoughts on the 4-day workweek, flexibility, and the boundaries between work and life. And why the 4-day workweek movement has gained popularity in recent years.

From Senior Developer to Manager and Back: The Journey of Returning to Coding

You're working as a developer, and one day - BAM, you're offered the chance to lead a team, to step into a managerial or leadership position.

What now? If I accept the offer, will I forget how to code? Will my skills depreciate? Is there a way back to a specialist path? Can I really be a “manager by day, developer by night”? Will I still be a technical person?

Staff Engineer, Engineering manager, Tech Lead manager - what do these titles actually mean, and what scopes of responsibility and management models potentially lie behind them?

Questions multiply and branch off, and the answers contain too many "it depends."

I've been at this point! At Atlassian, I undertook an experiment and moved from a senior developer position to a manager role for 15 months... and then I went back to coding.

I'll talk about my transition from developer to manager, my doubts, my new skills, and how the organization of work changed. What potentially hides behind the job titles with "manager" in them? Also, about returning to coding and the added value from my experiment.

Will my experience help you make a decision if you're facing one - I don’t know. But it will be food for thought 🙂

Next.js is my main web server for all APIs. And I like it!

Why don't you use something more specialized like Fastify or Nest? Why are you using Next.js in a way it wasn't designed for? You might ask.

Because it is good enough for my use cases and more flexible than I initially thought.

In this presentation, I’ll provide arguments for using Next.js as a delivery layer for your REST & GraphQL APIs.

With some middleware, a few libraries, and tweaking next.config, you can get a lot out of it.
The question is - is it performant? Well, we will see :)

Michał Michalczuk

Senior Software Engineer & Consultant @Tektit Consulting

Gdańsk, Poland

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top