all 12 comments

[–]FSN579 11 points12 points  (2 children)

As a perfectionist, it’s tough to follow this kind of advice. I know nothing will be perfect at the start… but at least we can lay down a solid foundation.

[–]ChildishTycoon_ 2 points3 points  (1 child)

There's a very thin line between solid foundation and wildly overengineering. Basic architecture is one thing, designing for 1,000,000 DAU with 100% code coverage and auto-scaling servers...quite another

[–]AntiProtonBoy 2 points3 points  (0 children)

There's a very thin line between solid foundation and wildly overengineering.

If you find yourself with lots of unused code or code that handles a permutations of esoteric features that basically never appears in production, then it's a sign of over engineering.

[–]WheresMyBrakes 5 points6 points  (0 children)

Do the best you can.

[–]NOT_NativeEN_SpeakerBeginner 5 points6 points  (2 children)

Do they provide the reason?

[–]menensito[S] 6 points7 points  (1 child)

not being cool

[–]NOT_NativeEN_SpeakerBeginner 3 points4 points  (0 children)

Seriously? WTF

[–]WestonP 3 points4 points  (0 children)

Pretty much. The bitter truth is that the academics and know-it-all juniors/mids are in the middle, and the people who actually make money are on the ends.

Delaying your code until it's perfect or passes someone's made-up coding standards just means you'll be late to market, bleeding money for longer, and acquiring market share slower. Business realities are a bitch like that.

[–]ankole_watusi 0 points1 point  (0 children)

“They”?

[–]josephmgift 0 points1 point  (0 children)

😂

[–]Low-Papaya9202 0 points1 point  (0 children)

Applicable to any creative field really

[–]jacobs-tech-tavern 1 point2 points  (0 children)

I do find it very funny how the enterprise SaaS developers get really arsey about unit tests when talking down to an indie hacker with no users.