Monkey Works: Where Everything Started

Note: This article was written retrospectively, years after the project took place in 2012. While it captures my experiences and challenges from that time, it's enriched with insights and understanding I've gained since then.

TL;DR

  • Technologies: Java, Eclipse RCP, OPC UA for industrial automation
  • Role: Software developer implementing sensor and actuator interfaces for industrial control systems
  • Key learning: The fundamentals of professional software development - from Scrum processes to product thinking, and the joy of seeing code affect the physical world

Every developer remembers their first job, but mine was particularly special. Monkey Works wasn't just any company - it was an EXIST-funded startup where I would learn not just how to write production code, but how to think about products, work in teams, and bridge the gap between software and the physical world.

Making lights turn green

My primary responsibility was implementing a sensor and actuator interface for controlling industrial equipment using OPC UA (Open Platform Communications Unified Architecture). Working with Java in the Eclipse environment, I connected industrial control systems through OPC UA and abstracted them using a predefined domain model.

There's a moment that remains etched in my memory: successfully commanding a traffic light to turn green through the interface I'd built, then seeing the confirmation through the connected video camera feed. That feeling of euphoria when digital instructions manifested in the physical world was unforgettable. It wasn't just about writing code anymore; it was about making tangible changes in the real world through software.

In the Monkey Works office, watching founder Stefan Hennig explain his master plan from his doctoral thesis

A universe of firsts

Starting at Monkey Works meant experiencing everything for the first time. It was my first encounter with Scrum, and suddenly I was part of daily standups, sprint plannings, and retrospectives. My first company Christmas party showed me how a team celebrates together. The first refinement session taught me how to break down complex problems. My first planning and review meetings revealed how software development is as much about communication as it is about code.

I attended my first professional workshop, learning from experienced developers and realizing how much there was still to discover. Product thinking became part of my vocabulary - understanding that we weren't just building features, but solving real problems for real users. Even the administrative side was new: creating my first invoice and applying for a tax number introduced me to the business aspects of being a developer.

These experiences, though over a decade old now, remain vivid. Each "first" shaped my understanding of what it means to be a professional developer. The lessons learned during those early days at Monkey Works continue to influence my approach to software development today.

The perfect storm of learning

Looking back, I realize how fortunate I was to land at Monkey Works as my first employer. Three crucial elements came together that would become cornerstones of my professional philosophy:

Product thinking was embedded in everything we did. We weren't just coding; we were solving problems, understanding user needs, and thinking about the bigger picture. This early exposure to product-focused development set a standard I've carried throughout my career.

Modern software development with cutting-edge technologies meant I was learning best practices from day one. Working with OPC UA for industrial automation wasn't just technically challenging; it was working at the forefront of Industry 4.0 before the term became mainstream.

People who wanted to change things surrounded me. The startup environment attracted individuals who weren't satisfied with the status quo. Founder Stefan Hennig's vision from his doctoral work wasn't just academic theory - it was a mission to revolutionize industrial automation. This culture of innovation and ambition was infectious.

The foundation of everything

Monkey Works gave me more than just technical skills. It provided a foundation for understanding software development as a discipline that combines technical excellence, collaborative processes, and product vision. The startup environment meant wearing multiple hats, seeing the full picture, and understanding how individual contributions fit into larger goals.

That first job taught me that the best software isn't just well-written; it's software that makes a difference. Whether it's turning a traffic light green through an industrial interface or building the next generation of web applications, the principle remains the same: we write code to solve problems and create value.

The memories from that small office, watching Stefan explain his master plan, working through our first sprints, and celebrating small victories together, remind me why I fell in love with software development.