How much time do you actually lose to infra setup before writing a single line of product code?
Every developer I talk to has the same story. The idea is clear, the stack is decided, but before anything real gets built there's 3 hours of AWS configs, Dockerfiles, environment variables, and CI pipelines that have nothing to do with the actual product.
AI coding tools made writing code faster. Nobody has solved what comes after.
Working on something early stage in this space. Not ready to share details yet but want to understand how real this pain is for other builders before going too deep.
How do you currently handle infra setup? And what part of it do you hate the most?
155 views
Replies
the framing that infra is the slow bit is half right. the actual time sink is decision cost, not setup cost. picking a queue, picking secrets management, picking how to do migrations, picking observability. once the choices are made the typing is quick. the teams i see ship fastest pick a default stack on day one and refuse to revisit any of it until revenue justifies the rewrite. opinionated defaults are worth more than any new tool, because the tool only saves you typing and the decision is what was bleeding the week.