From Gamer Curiosity to Team-Centered Craft: Denis Husidic (ABP PATENT NETWORK) on Creativity, Support Collaboration, and a Grounded Testing Culture

What stood out to the DevJobs.at editors

In the session “Denis Husidic, Software Developer bei ABP PATENT NETWORK” with speaker Denis Husidic from ABP PATENT NETWORK GmbH, we heard a concise, quietly confident account of what a developer’s day actually looks like when it’s anchored in customer feedback, team alignment, and disciplined testing. There’s no theatrics—just clear principles: collaborate closely with support, write things down, look at the code together, and combine manual with automated tests. Add to that a mindset of creativity, problem-solving, and curiosity, and you get a practice that runs from the first user request to a validated change.

One sentence at the very beginning sets the tone:

He’s “always been interested in computers,” he tells us—first and foremost through games. That candid origin story becomes a throughline: passion leads to deliberate training, which becomes professional practice.

The first steps: from games to a structured track

After finishing high school, Denis explored educational options and found a clear path: a computer science track at a technical college in Leonding. He enrolled, completed his program, and with that, the base layers were set. We hear no drama or overstatement here—just the essential progression from interest to structured learning, to applied work.

What matters in this part of his story is the sequence: curiosity, formal training, and then practice. It’s a simple pattern, but it often underpins resilient careers in tech. Structured learning doesn’t replace passion—it converts it into tools, frameworks of thought, and the ability to reason about problems methodically.

Day-to-day reality: it’s software—and everything around it

Asked what he does now, Denis starts plainly: software development. But he immediately makes it clear that coding is embedded in a larger workflow with several interlocking responsibilities.

A key player in that workflow is the support team:

Support stays close to customers, gathers feature requests and suggestions, and translates them into work items—user stories. They also collect bugs and try to reproduce them. That’s the foundation of a clean pipeline: concrete user stories instead of vague asks, reproducible bugs instead of loose reports.

From there, Denis describes a collaborative loop with the development team: they write things down, discuss the items, look into the code, and review specific issues in a developer round—checking what deserves special attention. The process blends documentation with collective scrutiny.

One line crystallizes the spirit of this approach: “several eyes see more.” It’s the principle behind peer review, shared ownership, and collective learning. It’s not just about catching mistakes—it’s about reducing blind spots and transferring knowledge in the process.

Closing the loop with tests: manual and automated

Denis emphasizes that testing isn’t an afterthought. He points to a mix of manual and automated checks—different things are in use—without naming specific tools. That absence of tool talk is telling: the emphasis is on the habit, not the brand names.

Manual tests bring context, exploratory depth, and the human feel for an edge case. Automated tests bring regression safety, repeatability, and speed. Used together, they form a protective layer that allows teams to change code without fearing the unknowns. When your pipeline starts with well-shaped user stories and reproducible bugs, and continues through shared reviews, testing becomes the natural conclusion rather than an external hurdle.

The social glue: everyday conversation matters

In a short aside, Denis mentions the “normal daily business coffee chat.” We took that as a reminder that social micro-moments are genuine productivity infrastructure. They create quick feedback loops, surface tacit knowledge, and seed small pairing sessions. Many practical fixes begin with “I noticed something…” said in a kitchen, not a meeting.

The developer mindset: technical interest, creativity, problem-solving, curiosity

Denis offers a clean checklist for attitude:

• Be technically interested.
• Treat creativity as a core skill.
• Have a problem-solver vibe.
• Stay hungry to learn because the field moves fast.

His definition of creativity is memorable. He likens programming to an artistic activity: you start from zero, with your tools, and make something out of nothing. That isn’t a claim for unbounded freedom; it’s a reminder that within constraints, there is room to design: to choose structures, craft readable code, and compose a solution that holds up.

On problem-solving, the implication is practical: form hypotheses, reproduce issues, trace code paths, iterate until things make sense. This is where the earlier workflow compounds: well-written user stories, reproducible bugs, shared code reviews, and tests focus the problem-solver’s effort where it matters.

And on curiosity, Denis is direct: the field evolves quickly, and it helps to enjoy learning new things. That mindset keeps you employable and resilient. It also creates a reinforcing loop—learning makes you better, and being better makes learning easier.

A full, quiet process: from request to validated change

Put together, Denis describes a complete yet understated process:

• Customers speak to support.
• Support shapes the input into user stories and reproducible bug reports.
• Developers and support collaborate closely, documenting and discussing.
• The team looks into the code and examines specific issues together.
• Manual and automated tests close the loop.

What’s striking is the lack of gimmicks. This isn’t a “framework pitch,” but a grounded practice—repeated small steps that consistently produce quality. When everything is written down, reproducible, and seen by multiple eyes, the overall system becomes robust without grand ceremony.

Practical takeaways for engineers

Denis’ short statements translate into habits any team can adopt:

1. Turn customer input into user stories

• Use a consistent shape—context, goal, acceptance criteria. Clarity reduces thrash and accelerates prioritization.

1. Make bugs reproducible

• Steps to reproduce, expected vs. actual behavior, environment details. Reproduction is half the fix.

1. Institutionalize developer rounds

• Short, focused discussions around concrete items increase quality. Keep them small, specific, and outcome-oriented.

1. Embrace the “several eyes” principle

• Treat peer review as knowledge exchange and risk reduction—not just a gate.

1. Balance tests thoughtfully

• Manual for exploratory and UX-near checks; automated for stability and regressions. Together they create confidence.

1. Keep documentation concise—and reliable

• Writing things down doesn’t mean writing a lot. It means capturing what the next person needs to move forward.

1. Protect social micro-moments

• Coffee chats or quick pings often unlock stuck work. They’re a legitimate part of the engineering system.

1. Cultivate creativity as craft

• Within constraints, design for readability, structure, and evolvability. Small design choices compound.

1. Train your problem-solving process

• Hypothesize, isolate, measure, adjust. Make it a repeatable method, not an ad hoc struggle.

1. Feed your curiosity

• Integrate small learning loops. It’s not about chasing trends—it’s about expanding your toolbox steadily.

None of this requires special permission or a grand reorg. These are habits teams can grow from wherever they are.

Creativity as a disciplined practice

The artistic analogy is more than a metaphor. Starting from zero and making something out of nothing frames the developer’s work as design under constraints. The constraints are real—time, scope, compatibility, expectations—but within them, good engineering is a series of considered choices. It’s craft. And the craft becomes effective when supported by the quiet rigor Denis describes: user stories, reproducible bugs, shared reviews, and testing.

Guidance for early-career developers

If you’re at the beginning, Denis’ path sketches a reliable sequence: find the spark (games, curiosity), choose a structured training path, and enter a practice where support, documentation, team review, and testing are normal. What makes this blueprint durable is its simplicity. There’s nothing to mythologize—just consistent steps that convert interest into capability.

Ask yourself:

• What genuinely sparks your curiosity—and how will you turn that into learning goals?
• Which educational setting will give you fundamentals and practice with feedback?
• How will you embed yourself in a workflow that connects user input to tested, shippable changes?

His answers point to a steady professionalism: nurture your interest, use structures that help you learn, and work in teams that share context and validate code with tests.

Lines that linger

A few compact statements from Denis carry far:

• Programming “starts from zero,” and with the right tools, “you make something out of nothing.”
• “Several eyes see more” captures the essence of peer review and shared ownership.
• Even the everyday “coffee chat” is part of how teams move knowledge.
• Stay “hungry to learn” because the field evolves quickly.

Taken together, they describe a developer’s craft centered on collective intelligence, design-minded coding, social glue, and continuous learning.

Conclusion: grounded habits, durable quality

In “Denis Husidic, Software Developer bei ABP PATENT NETWORK,” speaker Denis Husidic (ABP PATENT NETWORK GmbH) outlines a grounded practice of software development: keep customers close through support, turn input into clear written artifacts, examine the code together, and balance manual with automated tests. Wrap that in a mindset of technical interest, creativity, problem-solving, and curiosity, and you get a repeatable pathway from request to reliable change.

What impressed us is the quiet completeness of the approach. Nothing is sensationalized; everything is practical. It’s the everyday, repeatable steps that produce quality. Work this way and you won’t build castles in the air—you’ll ship. Think this way and you’ll stay adaptable—to new topics, tools, and challenges. That’s the kind of professionalism that makes teams resilient today.

• 

  

  Fokus auf IP

  Daniel Holzner von ABP PATENT NETWORK gibt in seinem devjobs.at TechTalk einen Überblick über die im Unternehmen entwickelten Projekte und deren Challenges.

  Watch now

• 

  

  Stefan Wöhrer, Product Manager bei ABP PATENT NETWORK

  Product Manager bei ABP PATENT NETWORK Stefan Wöhrer spricht im Interview über das Support Team des Unternehmens, wie dort das Recruiting gehandhabt wird und welche Technologien im Fokus stehen.

  Watch now
• 

  

  Alessandro Aichmann, Teammanager Software bei ABP PATENT NETWORK

  Teammanager Software bei ABP PATENT NETWORK Alessandro Aichmann gibt im Interview Einblicke in die Software Abteilung im Unternehmen und auf was dort bei einer Bewerbung geachtet wird.

  Watch now