StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I don't think there's a clear answer on this, and wouldn't be surprised if the question is closed because of it. I'll offer up my views in any case.</p> <p>Your example of a counter vs. a social media platform is much too contrived to be in any way realistic. But even if it was a reasonable example, I'd say application size or complexity (perceived or otherwise) has very little to do with your decision. In fact, I think you're creating a problem you very likely don't have yet.</p> <p>Instead of thinking of the tools needed to implement your application, think about what it is that you're trying to achieve with it. Some call this business logic, call it whatever you will, but if you're spending time thinking about tools rather then how to get to market, it's very likely you're focusing on the wrong things. Tools, and when to use them, should never be your primary concern.</p> <p>Here's what I think you should do. Jot down two lines about why your application makes sense and why it's existence is justified – don't mention any tools! Bake them in to a fortune cookie and open it a few days later. If you read it and it still makes sense, then figure out what the minimum feature set is – don't mention any tools! Look at it again a couple of days later, does it still make sense? Excellent! Now build a prototype – don't care about what tools to use, just use <em>whatever works</em> to prove your idea. Show it to someone else, is it a useful demo? Yes? Superb, you've got a project!</p> <p>Nowhere in this does it matter whether it was your own pure javascript, polluted by libraries or whether it was a completely different environment. The tools are not important. What's important is what you're trying to achieve and how to get it out there. The tools are peripheral, secondary. They are whatever you need to use to get where you're going. If that means using libraries that provide the moving parts to get your app rolling – fine! If it means using coffeescript over javascript – fine! In the end, what really matters is what you're trying to achieve, the tools you use to get there can't ever be the primary concern. </p> <p>Figure it out as you go along. You'll probably get it wrong a bunch of times before you get it right, that's just the way the cookie crumbles.</p> <hr> <p>You may also find this video useful. It's a talk about clean architectures, although it's mostly a recount of how <em>not</em> focusing on tools helped build a better product, and is likely what you want to do.</p> <p><a href="https://vimeo.com/43612849" rel="nofollow">https://vimeo.com/43612849</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload