From Game Modding to .NET Full‑Stack: Michael Blank, Full Stack Developer at WKO Inhouse, on Learning, PoCs, and Staying Motivated

A devstory worth studying: What stood out in Michael Blank’s path

In the session “Michael Blank, Full Stack Developer bei WKO Inhouse,” curiosity becomes a career strategy. Michael Blank sketches a clear, grounded journey: growing up with computers, attending an HTL program focused on business informatics with friends, narrowing in early on JavaScript as his favorite language, expanding into object‑oriented programming with C# and Java, and then stepping into a full‑stack role at WKO Inhouse while studying computer science at TU Wien.

Several lines stay with you. He says he “grew up with computers,” that early on JavaScript was his favorite language, and that today his work spans the full stack “from CSS adjustments in the frontend … down to SQL database calls.” He also gets pulled into proof‑of‑concepts—including an AI topic—to “find out whether it’s worth it at all or how we want to integrate it.” Adding to that is a workplace setup that supports focus and balance: good location and commute, the option to work from home, and flexible hours especially during exam periods. Together, it’s a portrait of full‑stack practice that’s wide in scope, pragmatic in choices, and squarely centered on solving real problems.

Early imprint: “I grew up with computers”

Michael calls himself part of the digital generation. From early on he wanted to understand how things actually work—especially games. That curiosity wasn’t a side note; it set the pace. He and a few friends joined the HTL track for business informatics and got exposed to “a lot of programming.”

• Early focus on JavaScript: “That was my favorite language.”
• Later, object‑oriented programming: “mainly C‑Sharp, but also Java.”
• Practice‑driven motivation: figure out how games work and add features via mods.

His modding story is telling. Instead of consuming passively, he built add‑ons. There’s a lasting developer lesson here: if you want to grasp software, work where your curiosity is strongest. Mods are small, contained, and instantly rewarding—perfect for learning APIs, OOP patterns, and the build‑test‑iterate rhythm that carries you forward.

Education: HTL for business informatics, then TU Wien

After the HTL, Michael doubled down—“I’m so interested in it, I’ll do a degree.” He started a bachelor’s in computer science at TU Wien. While studying, he searched for a job and joined WKO Inhouse. That put theory and practice side by side: lectures and exams on the one hand, real codebases and team delivery on the other.

What’s striking is how naturally his timeline blends “education” and “work.” The degree gives structure and depth; the job shows how ideas hold up under production constraints. The parallel makes his learning resilient. He experiences technology in context and gets better at judging whether something “pays off”—a line of thinking that resurfaces in his proof‑of‑concept work.

Full‑stack at WKO Inhouse: Broad responsibility, clear tools

As a Full Stack Developer, Michael is “active on all levels of development.” He puts it plainly:

That breadth isn’t about collecting buzzwords. It’s about connecting the user experience with the system’s behavior and delivering value end to end. The stack he mentions anchors his day‑to‑day:

• He works as a C‑Sharp developer and “a lot with .NET.”
• On the frontend, the team uses jQuery and the standard web toolbox: HTML and CSS.

It’s a stable, pragmatic setup: .NET/C# in the backend, SQL as a reliable data layer, jQuery for focused DOM work, and CSS for the visible experience. For full‑stack profiles, the message is direct: if you cover language fundamentals (C#, JavaScript), web basics (HTML, CSS), and relational databases (SQL), you can contribute across the board—bug fixes, new features, UI polish, performance, and data flow.

Proof‑of‑concepts and AI: Exploring without losing your footing

Michael is “often pulled in for proof‑of‑concepts,” small, almost research‑like programs. One example he shares is an “AI topic,” where his task was to “find out whether it’s worth it at all or how we want to integrate it.”

That stance is crucial for teams that don’t want to adopt technology for its own sake. The implications are clear:

• Insight before rollout: test what a new approach actually delivers.
• Integration in focus: embedding is not an afterthought—it’s the core of viability.
• Keep it lightweight: PoCs keep investment small and learning high.

Especially in the AI space—where the urge to productionize early is strong—this approach restores balance. Michael resets expectations: the question isn’t whether a topic is “hot,” but whether it’s worth it and practically integrable.

Work environment: Location, home office, flexible hours

Michael’s take on the work setup is refreshingly concrete. “The location is pretty good,” the commute works—small, daily realities that ease the week. He also has “a good amount of home office,” and his “working hours were relatively flexible.” During exams, shifting a workday wasn’t a problem. For students, that flexibility is a game changer—aligning learning and delivery instead of forcing a trade‑off.

In engineering teams, this is what supportive environments look like. Flexibility isn’t a perk; it’s a precondition for sustainable growth. Michael’s experience shows that such setups exist—and that they pay off.

Learning today: Formal education helps—but isn’t strictly required

Michael is candid: formal education helped him, but “nowadays it’s probably not that important.” There are “so many online courses,” even “YouTube tutorials,” that “go so deep into the subject that you can already start your career with them.”

The point isn’t that HTL or university is obsolete. The point is that learning paths are plural. With structure and persistence, you can build depth outside the classroom. Michael’s own trajectory doesn’t contradict that—it underlines it. Motivation, real needs, and consistent practice form the base on which any learning route can deliver.

Motivation that lasts: Solve your own problems

Michael’s best advice is anchored in two crisp examples:

• “A website has no dark mode … I’ll write my own dark mode if I use the site enough.”
• “I play a game—why isn’t this feature there? Then I’ll write a mod for it.”

Behind that is a tough but simple insight: “The most important thing is probably to challenge yourself.” Solving a real, personal need keeps you engaged—and accelerates your learning. It mirrors his whole story: modding, HTL projects, and now full‑stack tasks and PoCs.

Actionable takeaways for developers

Michael’s devstory translates into practical, no‑nonsense steps:

• Start with your own needs: Pick problems you genuinely care about (dark mode, missing game features) and fix them. Motivation compounds.
• Learn across layers: HTML/CSS for the surface, JavaScript for behavior, C#/.NET for backend logic, SQL for data. A full‑stack view multiplies your impact.
• Practice with mini projects: Mods and small tools are ideal: scoped, tangible, and instructive.
• Validate with PoCs: Before adopting new tech, ask Michael’s questions—“Is it worth it?” and “How do we integrate it?”—and test in a small, focused way.
• Leverage flexible learning: Formal education helps, but online courses and YouTube can be deep enough to get started. Consistency is the main differentiator.
• Seek environments that enable learning: Home office, flexible hours, and a manageable commute aren’t luxuries—they make long‑term growth possible.

Broad over narrow: Why full‑stack fits Michael

Michael’s range—“from CSS adjustments … down to SQL database calls”—adds up to a coherent skill set. Many developers find this compelling for good reasons:

• End‑to‑end understanding: knowing frontend and backend exposes dependencies earlier.
• Team flexibility: full‑stack profiles plug gaps and accelerate delivery.
• More ways to help: UI tweak, SQL optimization, or a new .NET endpoint—everything moves the product forward.

For Michael, this breadth seems like a natural fit—aligned with early tinkering and the habit of building what’s missing. It dovetails with his PoC work: both demand cross‑layer thinking and pragmatic execution.

Tools, used pragmatically: .NET/C#, jQuery, HTML/CSS, SQL

What stands out in Michael’s description is its calm. No exotic detours, no buzzword races—just proven tools. Three notes are worth underlining:

• Start with stability: .NET/C# and SQL have underpinned enterprise software for years.
• Frontend pragmatism: jQuery still shines where precise DOM and UI adjustments are needed—especially in established codebases.
• Fundamentals matter: HTML/CSS are the engine of visible quality—“CSS adjustments” aren’t trivial; they shape user experience.

Michael’s example shows that mastery of these blocks keeps you productive, no matter which new framework trends next.

A PoC mindset for everyday work: Three questions we took from the session

Michael’s AI PoC condenses into a simple decision frame:

1. Is it worth it? What impact, what effort, what measurable benefit?
2. How do we integrate it? Which interfaces, data flows, and dependencies?
3. What can we learn small? Which minimal experiments yield maximum insight?

Those questions balance openness to new ideas with a realistic delivery focus. They guard teams from hype while unlocking grounded innovation.

Studying while working: Realistic enablers

Michael’s experience with flexible hours and home office is worth highlighting. If you study and work, constraints are part of the deal. Three enablers stand out in his story:

• Time flexibility: shifting workdays around exams reduces stress and preserves focus.
• Place flexibility: home office creates pockets of deep work and saves commute time.
• Everyday logistics: a “good connection” sounds mundane, but it compounds weekly.

The takeaway is straightforward: conditions like these aren’t perks; they’re productivity levers—for companies and for students.

The thread running through it all: From tinkering to team impact

Across Michael’s milestones, a consistent pattern emerges:

• Early curiosity becomes making (mods and add‑ons).
• Education (HTL, TU) provides structure and depth.
• Professional work (WKO Inhouse) turns it into impact—full‑stack ownership plus PoCs.
• Learning philosophy: “challenge yourself,” solve your own problems, keep going.

The result isn’t a narrowly specialized track, but a robust generalist profile. In teams covering multiple areas—“backend development, frontend development, database, and also AI topics”—that breadth amplifies impact.

Lines we’ll remember

• “I grew up with computers … part of the digital generation.”
• “Early on I focused a lot on JavaScript—that was my favorite language.”
• “… from CSS adjustments in the frontend … down to SQL database calls.”
• “I was able to … find out whether it’s worth it or how we want to integrate it.”
• “The most important thing is probably to challenge yourself.”

These lines capture Michael’s stance: curious, pragmatic, self‑driven.

Practical next steps for readers

If you want to act on Michael’s story today, start small and specific:

• Pick an everyday problem: A tool you use a lot but that frustrates you (no dark mode?). Implement a minimal, working fix.
• Build a mini PoC: Take a topic that intrigues you (algorithm, UI experiment, data access) and define a sharp question: “Is it worth it?” or “How do we integrate it?” Explore it in a week.
• Tighten your stack: Deepen one layer—C# backend design, clear SQL queries, CSS cascade mastery, or targeted jQuery usage.

Keep projects scoped so you can finish them. That creates progress cycles that reinforce motivation—true to Michael’s approach.

Conclusion: A full‑stack career built on curiosity and follow‑through

“Michael Blank, Full Stack Developer bei WKO Inhouse” shows what a modern developer’s path can look like: sparked by the question “how do games work?”, strengthened by education (HTL and TU Wien), grounded in practice (end‑to‑end work from CSS to SQL), and open to new ideas (PoCs, AI topics). The work environment—good location, home office, flexible hours—makes learning and delivering mutually reinforcing.

His core advice is simple and powerful: “challenge yourself,” ideally by solving your own problems. Do that, and you’ll build both skills and the mindset full‑stack work thrives on: take responsibility, prioritize impact, and evaluate new tech with pragmatic experiments. That mix makes Michael’s devstory a helpful compass for aspiring and experienced developers alike.

• 

  

  KI in der Software Entwicklung

  Dominik Amon von WKO Inhouse demonstriert in seinem devjobs.at TechTalk mit einer Live Coding Session wie KI im Development Alltag eingesetzt werden kann und beleuchtet die Vor- und Nachteile.

  Watch now

• 

  

  Dominik Amon, Senior Software Engineer bei WKO Inhouse

  Dominik Amon von WKO Inhouse gibt im Interview Einblicke in die Teamstruktur des Unternehmens, die eingesetzten Technologien und erläutert den Ablauf des Bewerbungs- sowie Onboardingprozesses.

  Watch now