Michał Zakrzewski
@michalzakrzewski.com
Web Developer | 12+ years of simplifying code & crafting web solutions 💻 | Sharing tips, insights, and my coding journey 🚀
Blog: https://michalzakrzewski.substack.com/
Blog: https://michalzakrzewski.substack.com/
Pinned
Don't be afraid of making mistakes when coding.
There is no better way to learn.
There is no better way to learn.
If you have too much free time in the evening and you played/watched Factorio for too long! 😁
Quick idea, quick execution.
What do you think about input like that?
Quick idea, quick execution.
What do you think about input like that?
July 25, 2025 at 8:41 PM
If you have too much free time in the evening and you played/watched Factorio for too long! 😁
Quick idea, quick execution.
What do you think about input like that?
Quick idea, quick execution.
What do you think about input like that?
I’m coding in PHP, Python, Go, & JS… and guess what?
I’m double checking basic stuff every 5 mins 😅
I’m double checking basic stuff every 5 mins 😅
July 24, 2025 at 7:30 PM
I’m coding in PHP, Python, Go, & JS… and guess what?
I’m double checking basic stuff every 5 mins 😅
I’m double checking basic stuff every 5 mins 😅
Which do you prefer:
🛠 Fixing bugs
🚀 Building new features
🛠 Fixing bugs
🚀 Building new features
January 23, 2025 at 6:00 PM
Which do you prefer:
🛠 Fixing bugs
🚀 Building new features
🛠 Fixing bugs
🚀 Building new features
Naming matters.
Use descriptive variable names like userAge instead of x.
Code is read more than it’s written.
Use descriptive variable names like userAge instead of x.
Code is read more than it’s written.
January 23, 2025 at 12:00 PM
Naming matters.
Use descriptive variable names like userAge instead of x.
Code is read more than it’s written.
Use descriptive variable names like userAge instead of x.
Code is read more than it’s written.
Once, for a "small change", I overlooked writing unit tests.
That "small change" broke production for two days.
Lesson learned: Tests aren’t optional.
That "small change" broke production for two days.
Lesson learned: Tests aren’t optional.
January 23, 2025 at 7:45 AM
Once, for a "small change", I overlooked writing unit tests.
That "small change" broke production for two days.
Lesson learned: Tests aren’t optional.
That "small change" broke production for two days.
Lesson learned: Tests aren’t optional.
Debugging Tip.
Before diving in, always ask yourself: What changed?
Most bugs hide in the most recent edits.
Before diving in, always ask yourself: What changed?
Most bugs hide in the most recent edits.
January 22, 2025 at 6:00 PM
Debugging Tip.
Before diving in, always ask yourself: What changed?
Most bugs hide in the most recent edits.
Before diving in, always ask yourself: What changed?
Most bugs hide in the most recent edits.
Feeling like you’re not making progress?
Remember: learning to code is a marathon, not a sprint.
Every bug you fix is proof that you’re improving.
Remember: learning to code is a marathon, not a sprint.
Every bug you fix is proof that you’re improving.
January 22, 2025 at 12:00 PM
Feeling like you’re not making progress?
Remember: learning to code is a marathon, not a sprint.
Every bug you fix is proof that you’re improving.
Remember: learning to code is a marathon, not a sprint.
Every bug you fix is proof that you’re improving.
What was one of your biggest 'aha!' moments in programming?
Share it below - for me, it was realizing that functions can return functions (thanks to JavaScript closures) 🙂
Share it below - for me, it was realizing that functions can return functions (thanks to JavaScript closures) 🙂
January 22, 2025 at 7:45 AM
What was one of your biggest 'aha!' moments in programming?
Share it below - for me, it was realizing that functions can return functions (thanks to JavaScript closures) 🙂
Share it below - for me, it was realizing that functions can return functions (thanks to JavaScript closures) 🙂
I spent hours debugging, only to realize I was editing the wrong file.
Always triple-check the basics - it saves time and frustration!
Always triple-check the basics - it saves time and frustration!
January 21, 2025 at 6:00 PM
I spent hours debugging, only to realize I was editing the wrong file.
Always triple-check the basics - it saves time and frustration!
Always triple-check the basics - it saves time and frustration!
What's one coding tool or library you've discovered that you can't live without?
I'll start: Docker.
I'll start: Docker.
January 21, 2025 at 12:00 PM
What's one coding tool or library you've discovered that you can't live without?
I'll start: Docker.
I'll start: Docker.
Don’t just write code - write readable code.
A clever solution today could become a nightmare for your future self.
Simplicity wins.
A clever solution today could become a nightmare for your future self.
Simplicity wins.
January 21, 2025 at 7:45 AM
Don’t just write code - write readable code.
A clever solution today could become a nightmare for your future self.
Simplicity wins.
A clever solution today could become a nightmare for your future self.
Simplicity wins.
Using the website, can you identify the technology used on the backend?
So, why do you think your user will care about that?
So, why do you think your user will care about that?
January 20, 2025 at 10:30 PM
Using the website, can you identify the technology used on the backend?
So, why do you think your user will care about that?
So, why do you think your user will care about that?
Coding itself is straightforward; the real challenge lies in integrating all the different components smoothly.
January 20, 2025 at 12:30 PM
Coding itself is straightforward; the real challenge lies in integrating all the different components smoothly.
Endlessly watching coding tutorials is just a way to avoid taking action.
January 20, 2025 at 7:30 AM
Endlessly watching coding tutorials is just a way to avoid taking action.
Learning to code is like planting a seed that will eventually yield great rewards - it just requires a bit of time!
January 20, 2025 at 2:30 AM
Learning to code is like planting a seed that will eventually yield great rewards - it just requires a bit of time!
JavaScript can be used in nearly every field.
The real question is, should you really use it everywhere?
The real question is, should you really use it everywhere?
January 19, 2025 at 5:00 PM
JavaScript can be used in nearly every field.
The real question is, should you really use it everywhere?
The real question is, should you really use it everywhere?
Do you follow tech trends even if you don't feel you need to?
January 19, 2025 at 12:30 PM
Do you follow tech trends even if you don't feel you need to?
The easiest way to make your code cleaner is to write self-documenting code:
- Functions should describe what they are doing.
- Parameters should have types.
- Functions should have return types.
- Functions should describe what they are doing.
- Parameters should have types.
- Functions should have return types.
January 19, 2025 at 7:30 AM
The easiest way to make your code cleaner is to write self-documenting code:
- Functions should describe what they are doing.
- Parameters should have types.
- Functions should have return types.
- Functions should describe what they are doing.
- Parameters should have types.
- Functions should have return types.
most of my app's functions are first created on paper
January 19, 2025 at 2:30 AM
most of my app's functions are first created on paper
Great developers on your team can significantly boost productivity and creativity!
On the other hand, bad developers can stifle both in you.
On the other hand, bad developers can stifle both in you.
January 18, 2025 at 10:30 PM
Great developers on your team can significantly boost productivity and creativity!
On the other hand, bad developers can stifle both in you.
On the other hand, bad developers can stifle both in you.
I promised myself that I would write one article a week.
I chose Sunday as the day of publication.
Tomorrow will be published my 3rd article this year, I am proud of myself!
I chose Sunday as the day of publication.
Tomorrow will be published my 3rd article this year, I am proud of myself!
January 18, 2025 at 5:00 PM
I promised myself that I would write one article a week.
I chose Sunday as the day of publication.
Tomorrow will be published my 3rd article this year, I am proud of myself!
I chose Sunday as the day of publication.
Tomorrow will be published my 3rd article this year, I am proud of myself!
I decided to create a profile on Buy Me a Coffee 🙂
If you like my content and want to support me, here is the link:
buymeacoffee.com/michal.zakr...
If you like my content and want to support me, here is the link:
buymeacoffee.com/michal.zakr...
Michał Zakrzewski
I’m a software developer with 12+ years of experience in web development. I love creating and sharing content about programming, web development, and problem-solving in tech.Exploring new tools, langu
buymeacoffee.com
January 18, 2025 at 1:50 PM
I decided to create a profile on Buy Me a Coffee 🙂
If you like my content and want to support me, here is the link:
buymeacoffee.com/michal.zakr...
If you like my content and want to support me, here is the link:
buymeacoffee.com/michal.zakr...
What coding problem that you solved are you most proud of?
For me, it was achieving a 97% improvement in the process responsible for storing over 50 million records in the database.
For me, it was achieving a 97% improvement in the process responsible for storing over 50 million records in the database.
January 18, 2025 at 12:30 PM
What coding problem that you solved are you most proud of?
For me, it was achieving a 97% improvement in the process responsible for storing over 50 million records in the database.
For me, it was achieving a 97% improvement in the process responsible for storing over 50 million records in the database.
I don't have patience for devs who don't want to learn...
January 18, 2025 at 2:30 AM
I don't have patience for devs who don't want to learn...
How did you choose your programming language?
January 17, 2025 at 12:30 PM
How did you choose your programming language?