I used to be of mindset where I used to think why did people take months or years for something which I thought would have considerably less time. Until I started building my own product. Building something with insights, care, robustness and building something right is function of time and money. Therefore as an indie dev, take your time to build it. Rushing a solution and doing a half ass job often backfires when you reveal it to the world.

In brazilian portuguese we have an expression called "engenheiro de obra pronta" (something like "engineer of a completed construction").

It means that's easy to talk about a finished work, it's faults, how it could've been done better and, if one were to replicate it, he would take a lot of less time.

Of course he would, someone else took the trouble to plan everything and fix the all the problems to reach a reasonable architecture/design. And obviously, that person will never do it because "it's trivial".

I think it's easy to overlook all the little things.

Sure, you could probably whip something up in an hour that did a large part of of what it needed to do, but it would be kinda crappy and half-assed.

You almost always do 80% of the work in the first 20% of the time, the rest is a lot slower, but every bit as important.

People absolutely can tell when they are using something that has thought and effort put into it, and you can't fake that.

I think it usually is a combination of lack of experience and a deep desire to impress others. In other words: they are immature and lack self confidence.

I think it’s because some people grew up having to make time estimates and deciding whether to do something based on the estimate.

If they were in the same boat, they might have not done it if they expected it to take a weekend.

I guess it could be either: Different constraints or ignorance.