Leica Geosystems Zbigniew Jasinksi: From Hobby to Career—Creativity, Recipes, and Pierogi as a Framework for Application Development

A DevJobs.at portrait of a grounded devstory

In the session “Leica Geosystems Zbigniew Jasinksi,” Speaker Zbigniew Jasinksi of Leica Geosystems, part of Hexagon, offered a concise, human-centered snapshot of his path into tech. The themes he touched—creativity, daily hands-on work with computers, supporting the application development process, and a cooking analogy about recipes and variation—land with uncommon clarity.

He describes himself as a creative person for whom computers are “a big part of life.” He loves working with a computer every day and managed to turn a hobby into an office job. Professionally, he focuses on “support in the application development process.” Along the way, he compares software development to cooking: you start with a recipe and a goal to create something—and even with a recipe, you can change things. His most memorable line arrives with a smile: “The secret of good pierogi is that you have to make the meat very quickly.”

No grandiose claims, no buzzword fireworks—just a straightforward journey: a friend’s referral, an email, the question if he could travel for an interview, a quick process, and “here I am.” He closes with a balanced verdict: there’s a lot to do, it’s really nice, and he has no problems living where he is now.

Creativity as a developer’s baseline

Jasinski sets the tone early:

For developers, that’s not a throwaway line—it’s the baseline. Creativity in application development means:

• turning incomplete information into useful next steps;
• shaping solutions that work and can evolve;
• finding joy in the daily craft of refining and building.

When he adds that he loves “working with a computer every day,” it’s a quiet nod to the power of routine. This is the cadence that transforms curiosity into competence—ticket by ticket, iteration by iteration.

Turning a hobby into a job

There’s a pivotal moment in his story: translating a hobby into professional work. In his words:

We see three takeaways for tech talent:

• Passion is the spark, professionalism is the engine. Daily practice builds reliable skills.
• The shift from hobby to job means embracing both flow and duty—sticking with the craft on good and ordinary days.
• Professionalization puts you on a sturdy learning curve: each ticket reinforces the foundation, each iteration sharpens your feel for quality.

Supporting the application development process

Jasinski’s focus is crisp:

Support roles are essential, even if they’re not always center stage. They unlock flow by reducing friction—answering questions, unblocking builds, clarifying steps, stabilizing pipelines. From what he shares, we draw a few grounded truths:

• Good support converts interruptions into continuity—so work keeps moving.
• Quality shows up not only in code but in throughput: how smoothly a team turns ideas into features.
• Being a force-multiplier means caring about the process as much as the product.

Even without tool-specific details, it’s clear he operates at the heart of delivery—where ideas become shippable outcomes.

Cooking as a metaphor: recipes, goals, and variation

Jasinski’s most memorable framing is his cooking analogy:

Why this works:

• Recipes are like specifications or backlog items. They provide structure, not dogma.
• The goal—“to create something”—is the anchor; the path is adjustable.
• Variation is competence: experience tells you when a deviation improves the outcome.

“Even with a recipe, you can change something”

Many teams are tempted to treat specs as unbendable. His line flips that script: a good recipe tolerates variation—because conditions evolve, better ideas emerge, or risks become visible. Practically, that suggests:

• Iteration is not a concession—it’s the method.
• Use feedback loops early: what works, what’s missing, what’s too much?
• Quality rises when teams are empowered to decide, not just execute.

The pierogi punchline

Then there’s the quirky, unforgettable twist:

It’s oddly specific—and that’s why it sticks. We read it as a reminder that:

• Timing and tempo shape results; some steps require a specific cadence.
• Certain “secrets” are learned by doing, not by specification.
• In product work, there are phases where speed supports quality—short iterations can lead to better decisions.

No, it’s not a sprint manifesto. But it’s a crisp picture of how craft, experience, and tempo interact.

Career momentum: a referral, an email, an interview, and pace

How did he arrive at Leica Geosystems, part of Hexagon? Jasinski keeps it plain:

Then things accelerated:

Three grounded insights:

1. Referrals open doors. They don’t make choices for you, but they enable opportunities.
2. Momentum matters. When the invitation arrives, a timely yes often helps.
3. Decisiveness counts. “I agreed, and here I am” captures an informed, simple commitment.

Settling in: “It’s really nice here”

Jasinski closes with a clear, calm statement of fit:

We read this as a practical barometer: the work and environment align. Not grandiose, simply workable. That balance—meaningful tasks, an agreeable setting, friction-free living—is often the steadiest platform for doing good work.

Practical takeaways for developers

Surprisingly much can be put into practice from a few lines. Here’s what we’d highlight:

• Keep creativity in your baseline. See problems as spaces for design, not just tickets to close.
• Make routine your tool. Loving the daily hands-on work is how you compound skill.
• Support the flow. In the “application development process,” every friction reduced is time returned.
• Treat specs like recipes. Structure is essential, but variation may lift quality.
• Learn by doing. The “pierogi” image hints that timing and tempo can be part of the craft.
• Use referrals—and decide promptly. When opportunities arise, clarity and pace help.
• Check for fit. Work becomes sustainable when “it’s really nice here” is true in your day-to-day.

What stood out to us

• The clarity and restraint. No overpromising—just the essentials of motivation and role.
• The kitchen metaphor. Simple images make complex processes intuitive.
• The tone of calm resolve. “Here I am” as the end of a choice chain—steady and unpretentious.

It’s an authentic mix: passion without theatrics, professionalism without posturing.

A compact guide: from hobby to team contribution

Distilled into steps, Jasinski’s story becomes a practical guide:

1. Find joy in the daily craft. Routine is the soil where skill grows.
2. Turn curiosity into responsibility. Support the process, not just features.
3. Work with recipes, think like a cook. Vary when it serves the outcome.
4. Recognize when pace matters. Not everything should be fast—but some things must be.
5. Say yes to the right openings. Referral, invite, decision—step by step.
6. Pay attention to environment. Sustainable work needs a place you can live well.

Closing thoughts: Start, iterate, arrive

“Leica Geosystems Zbigniew Jasinksi” is a devstory without spectacle—and that’s its strength. Zbigniew Jasinksi of Leica Geosystems, part of Hexagon, shows how a creative mindset, steady routines, and the courage to vary the “recipe” can turn a personal hobby into a meaningful contribution to the application development process. His images—the recipe and the pierogi—remind us that strong results rarely come from rigid adherence alone, but from a thoughtful mix of plan, experience, and situational judgment.

No drumroll at the end, just a simple line that doubles as an invitation: “I agreed, and here I am.” For many in the tech community, that may be the nudge to embrace opportunity, treat specs as starting points, and move forward with calm, tempo, and pride in the craft.