From Turtle Graphics to Team-First Delivery: “Sylvia, Senior Agile Developer bei Österreichische Lotterien” on End-to-End Work, Java/React, and Containers

A start at twelve: programming as a real discovery

We joined the session “Sylvia, Senior Agile Developer bei Österreichische Lotterien” and heard a familiar spark that often marks enduring engineering careers: early curiosity and immediate feedback from code. Sylvia began programming “around twelve” at school. A voluntary computing class wasn’t about games—it was about actually programming on “old, slow machines.”

Her first projects were small but formative: moving a turtle on the screen and leaving a trail, and a text adventure with prompts and selectable answers. These visible results cemented her interest. She doubled down in school and then moved on to study, carrying forward the excitement of making things that others use.

That core motivation—to build software that serves others—anchors the way she approaches the craft today.

The spark that lasts: joy in building

Frameworks change; the compass remains. For Sylvia, lasting motivation doesn’t come from chasing novelty for its own sake. It comes from the satisfaction of building and delivering something people actually use. That perspective naturally leads to end-to-end thinking: understanding what it takes to make a feature work in the real world and caring about its full life cycle.

Role and workflow: Senior Agile Developer in a cross-functional Scrum team

Sylvia describes her role plainly: Senior Agile Developer. The teams work in Scrum and are deliberately mixed in skill sets to cover all aspects of a feature.

What that means in practice is end-to-end execution:

• analyzing and thinking through the requirements,
• deciding how best to implement the feature,
• handling database changes and whatever else the feature needs,
• testing thoroughly beforehand,
• and taking the feature into operation.

This isn’t just a process map—it’s a mindset. Responsibility does not end at the commit. It extends to live use, where the value becomes real.

The stack: Java in the backend, React in the frontend

Sylvia is specific about the technology choices:

The stack is pragmatic, stable, and widely used. It supports the team’s end-to-end ownership with tools that are productive and maintainable, without inflating complexity.

Team cohesion as an execution advantage

What Sylvia highlights most vividly is the collaborative fabric of her team.

That is more than a nice-to-have. End-to-end ownership only scales when knowledge and responsibility are shared. Sylvia’s team makes this explicit: a mix of skills, a shared commitment, and a willingness to step in when needed.

Variety over routine: back office processes and Win2D frontend

Topics shift frequently. Sometimes the work leans toward the backend and internal back office processes, and other times the team builds new UIs for the “Win2D frontend.” That shift brings variety in subject matter and introduces new collaborators across the company.

The result is clear: even with Java as a constant, the work never feels dull.

Variety, in Sylvia’s telling, isn’t just about switching frameworks. It’s about engaging different problem spaces—from business process logic to user interface concerns—and working with different stakeholders.

Containers as leverage for both delivery and testing

Sylvia also points to a major shift in recent years that changed how they build and deliver:

The dual benefit stands out. Containerization supports both operations and development. For a team that carries features from analysis to go-live, reproducible environments and easier setup are force multipliers.

Quality as a continuous practice

She doesn’t use buzzwords, but her description makes the point: testing happens “in advance” so that “when it goes live, everything works well.” Quality is embedded, not bolted on. In an end-to-end model, requirements, implementation, database changes, tests, and go-live form one system—and gaps become visible. Sylvia’s tone suggests a grounded, repeatable approach rather than heroics, which is what sustainable quality sounds like.

Learning and entry: joy, tutorials, and lasting fundamentals

Sylvia turns to learning—how to start, and how to build a career that endures.

From there, she recommends dipping into online tutorials. She mentions a personal example: her nine-year-old son is into Minecraft, and with a tool he can also move a “turtle” and begin with graphical programming. That visual start lowers the barrier; you can “click together” building blocks first and then look at the generated code.

For those who want to turn it into a profession, Sylvia recommends considering a university of applied sciences or a university degree. The rationale is clear: theoretical foundations endure longer than the latest coding trend.

This is a strong case for fundamentals over fads—and it aligns with her end-to-end practice. Carrying features to live environments benefits from stable, transferable concepts.

Actionable takeaways for engineers

Sylvia’s story translates into practical steps:

• Embrace end-to-end ownership: Plan from requirements to go-live. Ask, at every step, what it takes for it to “work well when it goes live.”
• Build cross-functional depth: Encourage breadth in the team. Share responsibilities so that work doesn’t stall when one person is out.
• Keep the stack pragmatic: Java in the backend, React/TypeScript in the frontend—stability and productivity over hype.
• Seek variety in problem spaces: Alternate between back office processes and UI concerns to broaden your perspective and keep engagement high.
• Use containerization as a developer tool: Reproducible environments reduce friction and make testing and delivery smoother.
• Put quality early: Treat testing as part of the feature, not an afterthought. The goal is simple: it should “work well when it goes live.”
• Nurture joy: Small, visual projects—like moving a turtle or building a simple adventure—are powerful motivators that sustain learning.
• Start accessible, then go deeper: Use tutorials and graphical programming to lower the entry barrier; then read the code to bridge into text-based programming.
• Invest in fundamentals: Consider formal education to acquire patterns and concepts that remain useful over decades.

Quotes that stick

A few lines from Sylvia that capture the essence of her journey:

What we learned at DevJobs.at

From “Sylvia, Senior Agile Developer bei Österreichische Lotterien,” we take three clear themes:

1) Ownership that reaches production: Features are carried from requirements to operation—with testing and database changes included—so that real users benefit.

2) Team-first delivery: A cross-functional Scrum setup, Java and React as a pragmatic stack, and a culture where someone steps in when needed. That’s how end-to-end ownership becomes sustainable.

3) Learning that lasts: Joy fuels curiosity, tutorials lower the entry barrier, and formal education strengthens the foundations—patterns and concepts that outlive trends. Containerization, meanwhile, makes both development and production workflows smoother, closing the loop from idea to live software.

Sylvia’s path connects early curiosity with mature, team-centered practice: stay curious, share responsibility, deliver together. It’s an instructive blueprint for modern software development—and a reminder that joy in building is a powerful engine for lifelong learning.

• 

  

  Recommendation Engine

  Patrick von den Österreichischen Lotterien gibt in seinem TechTalk Einblicke in die grundlegenden Hintergedanken bei der Entwicklung der hauseigenen Recommendation Engine.

  Watch now

• 

  

  Martin, Abteilungsleiter Development bei Österreichische Lotterien

  Der Abteilungsleiter Development bei den Österreichischen Lotterien Martin gibt im Interview einen Überblick über die wesentlichen Eckpunkte der selbst organisierten Devteams, wie dort das Recruiting abläuft und mit welchen Technologien gearbeitet wird.

  Watch now

• 

  

  Oscar, System Engineer Backup & Storage bei Österreichische Lotterien

  Oscar von den Österreichischen Lotterien spricht im Interview über seinen Weg in der IT bis hin zu seinem aktuellen Job neben dem Studium und gibt Tipps für Beginner.

  Watch now
• 

  

  Philipp, System Engineer Linux bei Österreichische Lotterien

  Philipp von den Österreichischen Lotterien erzählt im Interview über seine Anfänge in der IT, den Arbeitsalltag in seinem Beruf als System Engineer und was seiner Meinung nach für den Einstieg wichtig ist.

  Watch now
• 

  

  Andreas, System Engineer Digital Workplace bei Österreichische Lotterien

  Andreas von den Österreichischen Lotterien erzählt im Interview über seinen technischen Background in der Schule, was seine Arbeit als System Engineer Digital Workplace umfasst und gibt Tipps für Neueinsteiger.

  Watch now