Live data from Hacker News

Choose Shipping Over Using the Latest Shiny Framework

shoganai.io

1–10 of 21 posts

Re: Choose Shipping Over Using the Latest Shiny Framework

#4
Agree! Like they say: You're probably going to be the only one bleeding on the bleeding edge.

Choose whatever takes you to MVP the quickest. Avoid the #beliebers in the echochamber[like this one!]. Choose something that you're familiar with, and probably aren't immersed deep enough yet. So that there is still ground to cover. Usually there is always much to learn.

Focus must be on the MVP and not on the quality of the framework or the hipness of stack. Those things are unimportant until you're ready to hire. Once a bit more stable then play around. Contribute into the system. Push it forward. Avoid stagnation. Have beer. :)

Re: Choose Shipping Over Using the Latest Shiny Framework

#7
post #6

Nothing is absolute. For new, small projects, choose a new unknown. For a big, important one you obviously don't just jump into something brand new.

Why would you choose an unknown though when there are tons of battle tested frameworks out there? The only reason I can think you would do this is if the framework offered something totally unique or revolutionary, but I really haven't seen that in many frameworks for a long time now.

Re: Choose Shipping Over Using the Latest Shiny Framework

#8
post #6

Nothing is absolute. For new, small projects, choose a new unknown. For a big, important one you obviously don't just jump into something brand new.

Why would you choose an unknown though when there are tons of battle tested frameworks out there? The only reason I can think you would do this is if the framework offered something totally unique or revolutionary, but I really haven't seen that in many frameworks for a long time now.

Perhaps to learn and be ready if that new and untested framework is ideal for a larger project in the future?

Re: Choose Shipping Over Using the Latest Shiny Framework

#9
Here's a confession: I'm afraid to ship. I'm afraid of being rejected and of being dismissed, and of being seen as a failure. So I bullshit myself that "doing the thing" in the latest and greatest new framework, new language will at least mean that I "learnt something". Failure sounds less irredeemable when you count the dividends of new frameworks learnt!

It has taken me decades to confront this thinking in myself and even now, at times, I run into this logic. It's automatic thinking.

I like the article. You have to be 100% crystal clear that you are interested in the delivery of the finished concept and not the tools you used to build it.

Post reply on HN