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 hit compile and are greeted by a wall of red: compiler errors, runtime exceptions or syntax errors. In this session, we’ll explore how Odin turns that frustration into guidance. Its compiler messages act like a road-map. Each failure points directly to what’s missing, whether it is a package, an import, a main, or a type definition. We look into the “fail → code → run” loop.