Mytos
Home / Development & design blog / We Don't Accept 'It Can't Be Done'
Web Apps

We Don't Accept 'It Can't Be Done'

Most 'impossible' requests are just unsolved engineering problems. Here is how we break a hard problem down to first principles and engineer a direct solution instead of a workaround — the mindset behind everything we build.

MWritten by the Mytos teamJun 8, 20265 min read
We Don't Accept 'It Can't Be Done'

'That can't be done' almost always means 'nobody here has solved it yet'. The two are easy to confuse, and the difference is the entire reason our clients come to us. When we hear a hard request, we do not look for a reason to say no — we look for the problem hiding inside it.

So we break it down to first principles. What is actually being asked, underneath the assumptions? Strip away 'the way it's usually done' and most walls turn out to be conventions, not laws of physics. Once the real constraint is on the table, it is almost always something we can engineer around.

We also refuse the lazy workaround. It is easy to bolt on a hack that appears to work and quietly rots six months later. We would rather spend the extra day designing a direct solution that holds — one we would be happy to maintain ourselves, because usually we will.

This is the mindset behind everything we build: hard is not the same as impossible. Give us the problem everyone else flinched at, and let us show you what a direct, engineered answer looks like.

Have a project in mind?

Let's engineer your solution

From a rough idea to a shipped, self-running product — we build fast, reliable digital products and solve the hard problems along the way.

Start a project