4 ms·
> Endless discussion over which server-side framework to use, which folder structure makes the most sense, which client-side package management system to use, h
by k3n 13y ago
> Endless discussion over which server-side framework to use, which folder structure makes the most sense, which client-side package management system to use, how to bring everyones preferences together.
It sounds like the challenge is dealing with different people that have differing opinions on what to use, and with this project you're just saying "Use this, trust me!" and hoping that nobody objects? The answer to the problem is to prescribe as much as you can beforehand, so that there is effectively no room for discussion around these points?
It doesn't seem to actually solve any problems around gaining consensus, it just pushes one very opinionated view. Or perhaps I've misunderstood completely.
- matt_creager 13y agoA number of challenges exist, one of them as you mentioned is just a matter of people having different opinions, another is peoples specializations, if you don't frequently work with client-side tools you might not have been introduced to LiveReload for example. Prescribing an approach beforehand is exactly what I'm advocating, the best way I know how, with an example :) I think what we need right now is opinions, mine, yours, anyone with expertise and the willingness to apply it to this problem really, so we can begin the process of iterating on it, improving it. It won't be the best tool for every hackathon, but we can create a solid foundation.
- k3n 13y agoOk, that does make more sense in the context of dealing with those unfamiliar with the problem space. And I agree that it's good to have something to bring to the table, as it can demonstrate the fitness of the proposed solution, or if nothing else, provide a starting point.