Staudt Engineering

Most systems are designed to be used by people. Designing systems in a way that they become truly helpful for those who interact with them has been my favourite and most challenging task in the last years.

Here are the core principles I try to apply:

1. Tools shall be unobtrusive
2. No Bullshit Metrics™ – because they are just a game
3. Balance simplicity and flexibility
4. Creating data has no inherent value, it’s all about using it in a clever way
5. Use algorithms for the complicated things and humans to deal with complexity
6. Create room for mastery

Basically, I crave for excellence, for my users, my clients, fellow developers and myself, because we ain’t no monkeys!

Would like to hear more about that? Get in touch!

I’m a polyglot software developer and have been told to master C# and JavaScript. Also, I’m pretty good with C, C++, Java and a bunch of more exotic programming languages. I actually started writing code at age 11.

Beyond that workmanship part of building software, I consider myself to be a software architect, in the way that I successfully implemented well fitting, scaling and maintainable solutions significantly more often than I failed.

I’m proficient with both Windows and Linux as OSes (before you ask, I prefer vim over Emacs, but let’s not fight about that) and use both on a daily basis. Building custom Linux distributions is something I occasionally do.

When it comes to databases I’ve worked extensively with MySQL/MariaDB, Microsoft SQL Server and Postgres on the relational side of things. On the NoSQL front I’ve made excellent experiences with MongoDB, Redis and InfluxDB. All of them are great and have their applications.

I’m familliar with multiple CAD (PRO/Engineer, Fusion 360) and ECAD (Altium Designer, OrCAD, KiCAD, Designspark PCB) systems and I use some of these on a daily basis.

I love to make others more efficient. I’ve done so by introducing teams to better coordination practice and modern development methods (the usual indefinitely long list of catchy words like “continuous integration”, “continuous deployment”, “automated testing”, “containers”, etc…). I’ve seen leaps in productivity occur with practices like pair development. And did I tell you I love Kanban?

On the non-technical side, I speak German, French and English fluently, with the former two being my native languages. Finally I’m a self-admitted coffee aficionado, a rather talented cook and a vinyl-geek.