Skip to content

DevMindset

  • Programming
  • Linux
  • Developer mindset
  • Tools & Workflow

Piotr Karasiński

# Hi, I'm Piotr. ====================You don't look for ready-made solutions. You understand problems.I don't have an engineering degree before my name, I haven't been through the corporate assembly line, and I have no intention of pretending to be someone I'm not. I am a Python developer and an advanced Arch Linux user. Everything I know, I figured out myself—through thousands of hours spent in the terminal, debugging code late at night, and tearing systems down to their bare bones until I understood how they work under the hood.I built this blog because I know exactly what it feels like to hit a dead end as a self-taught developer.My Perspective (I use Arch, btw) ----------------------------------My approach to programming and operating systems was shaped by Arch Linux. When you configure a system from a clean TTY, you stop fearing the unknown and start controlling every single process. I apply the exact same rigor to code. I'm driven by raw performance, task automation (Meta-Prompting, AI Engineering), and squeezing the absolute maximum out of the tools at my disposal.Practical Areas| Domain | What I actually do | | :--- | :--- | | **Python Integration** | Writing clean, production-ready code (AsyncIO, advanced scripting, process automation) | | **Realtime Engines** | Developing projects using the Panda3D engine (optimizing real-time logic and rendering) | | **System & Workflow** | Arch Linux (Terminal-first approach, package management, repetitive task automation) | | **AI Workflows** | Building advanced prompts (Meta-Prompting) and code-level LLM integration via MCP |Who is devmindset.dev for? -----------------------------DevMindset.dev was built for developers and advanced self-taught programmers who have hit a plateau on their journey. It's for people who have already mastered the basics, can build an application, but feel like they've hit a wall and refuse to settle for "it just works."If you are tired of tutorials explaining for the hundredth time how a `for` loop or a Docker container works, this is the place for you. Here, we dive deep into topics that actually drive growth:Multi-stage builds and cgroups orchestration in practice. Analyzing process behavior under extreme load. Solving architectural problems that self-taught developers usually have to tackle alone.The blog is sustained by Google AdSense ads. This allows me to remain completely independent of any sponsors and publish exactly what I believe is valuable for your technical growth.Beyond Code ----------I carry the analytical mindset and determination of a self-taught developer into other areas that require absolute focus:Music: I play classical guitar (fingerstyle), dissecting pieces based on modal scales. Nature & Strategy: I practice spinning and ground fishing. Targeting pike and tench is a process full of variables for me—pure outdoor strategy. Dynamics: I clock miles on my bike, monitoring cadence and optimizing gear ratios for maximum efficiency.I believe that the precision required to master a complex piece of music or to rig the perfect fishing setup calls for the exact same type of focus that allows you to write flawless code.> Let's go deeper. If you've hit a wall in your learning, are looking for raw technical substance, and want to start understanding systems like an Arch user—you're in the right place.

Anatomy of a Segfault — From MMU Through Kernel to gdb Core Dump

2026-05-302026-05-29 by Piotr Karasiński

What exactly happens when a process touches a bad address. From the MMU and page table through the kernel page fault handler to core dump analysis in gdb — null deref, stack overflow, use-after-free.

Categories Linux Tags arch linux, C, gdb, linux, memory management, segfault Leave a comment

.bashrc — Anatomy of Shell Startup and Performance Optimization

2026-05-302026-05-28 by Piotr Karasiński

Your terminal takes 800 ms to start. Bash loading anatomy, lazy loading version managers, completion caching, PS1 without synchronous git status — and how to drop to 50 ms without compromises.

Categories Linux, Tools & Workflow Tags linux, performance Leave a comment

epoll vs io_uring — When the Event Loop Isn’t Enough

2026-05-302026-05-28 by Piotr Karasiński

Anatomy of two Linux I/O models. epoll vs io_uring, readiness vs completion, syscall overhead, SQPOLL — and when reaching for io_uring instead of an event loop actually pays off.

Categories Linux, Programming Tags kernel, linux, performance Leave a comment

The DRY Myth — When Code Duplication Is the Correct Architecture

2026-05-302026-05-26 by Piotr Karasiński

DRY has become a dogma that destroys more code than it saves. When duplication is the correct architectural decision — and how to recognize the moment when chasing “Don’t Repeat Yourself” stops being engineering.

Categories Developer mindset, Programming Tags clean code, design patterns, DRY, refactoring, software architecture Leave a comment

cgroups v2 as a Native Runtime Isolation Primitive — No Docker Required

2026-05-302026-05-25 by Piotr Karasiński

Skip the container abstraction layer. Enforce CPU, memory & I/O limits directly via cgroupfs — zero daemon overhead, no OCI ceremony. A deep dive into cgroups v2 on Arch Linux.

Categories Linux Tags arch linux, cgroups-v2, kernel, linux, processes, runtime isolation, systemd, systems programming Leave a comment
Older posts
Page1 Page2 Next →
  • Privacy Policy
  • Cookies Policy
  • Contact
  • About
  • About Me — Piotr Karasiński
© 2026 DevMindset • Built with GeneratePress