Live data from Hacker News

Startup Anti-Patterns

itamarnovick.com

101–102 of 102 posts

Re: Startup Anti-Patterns

#101
post #11

Such anti patterns are like Nostradamus’s prophecies - you see a company flopping then curve fit a narrative to justify the antipatterns. How do I, as a founder, know that I am falling into an anti pattern? I don’t believe it is possible to know. You can only “know” in hindsight and that makes these anti patterns useless.

[dead]

Re: Startup Anti-Patterns

#102

Some seem to treat microservices as a sign of good engineering when it's often just premature complexity. You can always split a monolith later, but you're stuck maintaining that complexity from day one

You can have microservices inside a monolith. It has the advantage of always deploying in a synced state.

Yes. One of the better startups I worked for did it that way. There was a single, mono-repo style code base with multiple services. Some were more micro than others. They shared common code like model definitions.

Everything was built/deployed in a single release (unless there was a hot patch, emergency bug fix, in which case we "could" work around it if needed.)

Post reply on HN