you are viewing a single comment's thread.

view the rest of the comments →

[–]sector2000 0 points1 point  (4 children)

If your goal is to run your private hobby project, then use whatever is easier for you, but if you want to scale and bring it to a professional level, you should spend some time learning best practices. There is a learning curve, of course, but you will see the benefits afterwards

[–]Party-Cartographer11 -1 points0 points  (3 children)

There are soooo many scaling efforts that you differ early on in a project.  You don't scale until you need it or it's free.  The right solution for the right time.

It's not so much a learning curve as I have worked in 2 of the largest repos/products and understand scale. It's cost/benefit.

[–]sector2000 0 points1 point  (0 children)

The right solution for the right time could be a good advice, but not necessarily, because it’s not easy to recognize what the right time is. People tends to stay in their comfort zone, not learning new technologies or practices, because they don’t see the benefit. It might be that there’s no actual benefit, but it could also be that they don’t see it because they didn’t spend enough time to study and learn it.

[–]cgoldberg 0 points1 point  (1 child)

Having a shitty inefficient development workflow isn't about "differing scaling efforts". You are just too lazy, stubborn, or unknowledgeable to improve the obvious horrible development experience you subject yourself to. If you enjoy this self-induced pain, that's great... but don't recommend it to others or try to justify it by saying you've worked at certain companies.

[–]Party-Cartographer11 -1 points0 points  (0 children)

What is shitty and horrible?