Development

Failure Driven Development: We Fail to Succeed

Compiler messages guide us through programming challenges. Each error reveals missing elements like packages or imports.

Glenn Jacobsen

Glenn Jacobsen

Glenn Jacobsen is a seasoned senior developer at Munu in Stavanger, with over 15 years of professional software development experience.

His journey in tech began with the spark of his first code—typing out a bouncing ball in BASIC2.0 code from a book rented at the Klepp library in the 1980s—laying the groundwork for a lifelong passion for technology

When he's not coding, Glenn embraces his love for Viking culture—often channeling that spirit through his attire and approach—while enjoying gaming, hiking, and exploring ancient history.

His unique blend of technical expertise and personal interests brings a distinctive depth to his work and presentations.

1 / 3

Programming is hard: every day we compile and only to run into a red wall of compiler errors and runtime exceptions. In this session, you’ll see how Odin’s compiler messages become our roadmap: each failure path reveals exactly what’s missing—packages , imports, main procedure, or type definition. we look into the “fail → code → run” loop.