Ask HN: Important nonobvious startup/business lessons you've learned?
As a dev i&#x27;ve always known my hunch when it comes to compromises. Never let the business team ruin your experience building cool rock-solid code. I&#x27;d rather resign than to compromise anymore. I know there should be a sweet spot between &quot;perfect&quot; and &quot;working&quot;. Even a junior can pull-off a &quot;working&quot; app. But when it starts to scale, all those hasty bad decisions will bite your ass. Never skip planning, plan as long as you need. Nowadays i start coding only after i have 100% visibility into what i&#x27;m building: diagrams, dependency graph, schemas, types and data structures, documentation, user flows, everything. As the say goes: if i have 24h to chop a tree, i&#x27;d sharpen my axe 23h. And we haven&#x27;t yet  taken into account infrastructure, devops, ci&#x2F;cd, security, releases, logging, and all sorts of tooling. I need around 2 months just for initial planning, setting everything up and laying out the codebase structure.