Hi, I’m Ines Panker. I take complicated systems and find the arrangement that makes them work like poetry.
I’m a software engineer by trade, an explorer at heart, and a poetry reader by night. I’m good at taking something tangled and finding the version of it that fits best. I believe that anything knotted, a codebase, an argument, a hard idea, has a shape that makes it feel obvious, and the work is finding it.
If you’re reading this, you probably clicked through from a blog post and wondered who’s behind it. (Or you’re a conference organizer checking whether I’m a real person: hi, I am, and I promise to be more fun in person than a bio can manage.)
I’ve been building software for almost two decades. I started with Java, surfed the PHP wave, and for the past decade Python has been my weapon of choice. I’ve written the code, shaped the architecture, and led the teams. Long enough to learn that the hard part is almost never the code. It’s making the system, and the reasons behind it, legible to the people who have to build on it, use it, and live with it.
That’s where my real interest sits: at the seam between the technical and the human. Great software systems are like well-designed cities, thoughtfully planned, easy to navigate, built to scale gracefully, and the key is building solid foundations and focusing relentlessly on what genuinely matters to the people inside them. Software reflects the people who build it, the people who use it, and the society it lives in, and I like exploring how technical decisions and human dynamics keep quietly shaping each other.
Poetry does the same thing: it arranges words so something complex suddenly feels simple. That’s what I’m after every time I explain a system, give a talk, or write one of these posts, blending technical depth with a focus on the people around the code.
What I’m looking for these days: the work I want more of is helping teams, and the people who build for them, make sense of complex systems. Advising on architecture, translating deep technical ideas for the people who need to act on them, untangling a codebase that’s outgrown itself, or the kind of developer-facing work where explaining clearly is the job.
I’m based in Ljubljana and I work remotely. If that’s the sort of thing you’re building, I’d genuinely love to hear from you: reach me on LinkedIn.