|
|
|
|
|
|
by dathinab
1369 days ago
|
|
|
> You need auto scaling to evaluate an idea works?! But you don't "just" show that something works. Once you did show that you are expected to make a MVP and then a MVP which works in production and then add features etc. With fly you can just use the same basic setup to go through all of this steps reducing a ton of friction. I have seen startups fail because of this friction. I also have seen internal proposals being abandoned because of this friction. |
|
|
I think something happened with a generation of programmers that completely missed the basics and went straight to abstractions.
They know react but not JavaScript, they know k8s but not linux… and they barely know how a computer works. They read a lot of stuff online in blogs but no books. They think moving fast is what some company marketing material says it is.
Look anything you build on top of the basics will be more complex than the basics. It’s worth it to abstract complexity when that arises, when you don’t have it, it’s not necessary and only causes you to move slowly.
Nothing will be faster to iterate than a file on disk if you’re working alone and want to validate an idea. You can literally rsync the folder you’re dev-ing from on a git tag and change a symlink in a single command. That will take you very far with no friction.
What I’ve seen failing is people who find the non existing problems they have more interesting than delivering value