We're attending SIM Conference: why events like this still matter
We'll be attending the SIM Conference this year. Not just for the talks - but for real conversations with people working on real problems.
We'll be attending the SIM Conference this year - and we're genuinely looking forward to it.
Not just for the talks or the agenda, but for something that's harder to replicate elsewhere: real conversations.
What is SIM Conference?
The SIM Conference brings together startups, investors, and teams building technology across different domains - from software and AI to hardware and infrastructure.
The focus is not just on presentations, but on creating meaningful connections between people working on real problems.
For us, that's the most interesting part.
Why we're going
Most of the work we do happens deep inside systems:
Debugging complex interactions
Tracing failures that emerge from how components interact, not just how they work individually
Analyzing code paths that are hard to observe
Finding execution paths that only become visible through deep static and dynamic analysis
Testing behavior that only appears under specific conditions
Reproducing failures that depend on timing, load, or environment
It's easy to get lost in that world.
Events like SIM create a different kind of space - one where you step back and see how others approach similar problems from completely different angles.
What we're interested in
We're especially curious about how teams deal with:
Systems that behave unpredictably in production
Behavior that looks fine in testing but breaks in real-world conditions
Bugs that are hard to reproduce
Issues that depend on timing, state, or environment and resist standard debugging
Gaps between "what should work" and "what actually works"
The space between specification and reality - where most real engineering happens
These are not edge cases anymore - they're part of everyday engineering.
Why conversations matter more than talks
You can read about technologies.
You can watch talks online.
But you can't easily recreate the moment where someone casually describes a problem - and you realize it's exactly what you've been seeing too.
That's usually where the most useful insights come from.
What we've been working on
Over the past months, we've been focusing on:
We recently shared some of this thinking in a series of articles:
Embedded systems testing: methods, challenges and best practices
Static vs dynamic testing: differences, use cases and best practices
Software testing for complex systems: challenges and strategies
If you're going too
If you'll be at SIM - feel free to reach out.
We're always interested in hearing how others approach testing, reliability, and system behavior in real-world environments.
Final thought
The more complex systems become, the harder it is to understand them in isolation.
Sometimes, stepping outside your own context is exactly what helps you see things more clearly.