Boring on purpose
Every technology page here states when we reach for it and — more usefully — when we don’t. A stack page with no opinion is a logo grid with paragraphs.
Ask what your project needsFour questions, asked before any stack decision
None of them is “is this interesting”. Interesting is a cost, and it is paid by whoever is on call at 3am — rarely by the person who chose it.
Hiring pool
Could you hire someone in Ahmedabad to maintain this without us? If not, we have handed you a dependency rather than a system.
Support window
Is there a published end-of-life date, and is it far enough away that your system will not need a runtime migration in year two?
Boring by default
Does this solve a problem you actually have? Novelty is a cost paid by whoever is on call, and it is rarely paid by the person who chose it.
Exit cost
If this turns out to be wrong in three years, what does moving off it cost? We avoid choices that are cheap to adopt and expensive to leave.
Backend
- Node.jsOne language across the stack, which matters most on small teams where the same engineer owns a feature end to end.When we use it, and when we don’t
- .NETWhere the estate is already Microsoft, or where a long-lived line-of-business system needs a platform with a twenty-year support story.When we use it, and when we don’t
- Laravel & PHPFast to a working admin surface, cheap to host, and the most common thing we are handed when someone asks us to take over a system.When we use it, and when we don’t
Mobile
- React NativeOne codebase for iOS and Android when the app is mostly screens, forms and lists — which is most business apps.When we use it, and when we don’t
- FlutterWhere the interface is custom-drawn and identical on both platforms by design, and the team wants one rendering model to reason about.When we use it, and when we don’t
What we will not pretend to do
A capability list that includes everything is a capability list that means nothing.
We do not do embedded firmware, game development, blockchain protocol work, or data science beyond the applied end of it. We have no depth there, and hiring a contractor and reselling them to you at a margin is not a capability — it is a markup.
We are also cautious about putting language models inside a product where a rule would do the job. That position costs us work, and we would rather lose it than build something we would not run ourselves.
If your project needs one of those things, say so on the first call. We will tell you straight away rather than three weeks into a proposal.
How we workNot sure which stack your project needs?
That decision is part of discovery, and it is one of the cheapest things to get right and most expensive to reverse. We put the reasoning in writing before anyone commits to it.