7 ms·
Skeletons and frameworks should be avoided at all costs. Frameworks are sometimes useful if you know one well but if you're new to it its gonna be a huge time
by waheoo 5y ago
Skeletons and frameworks should be avoided at all costs.
Frameworks are sometimes useful if you know one well but if you're new to it its gonna be a huge time sink.
Skeletons are similar issue to frameworks, they give you a whole lot of boiler plate and distract you from solving the problem tying you up with the authors picky conventions.
The best framework is a .PHP file running on Apache.
- vbsteven 5y agoI would like to nuance your statement a little bit. I agree that learning a new framework alongside building your project is a bad idea. But if there is a framework that you know well and it fits the project then definitely use it. I have my standard stack of backend/frontend/database/infra tools that I know inside out and fit most web projects. So whenever I have a new project idea it takes me 20 minutes to get hello world from frontend through backend to db and back. And then I can start building using the FE/BE frameworks I already know. Edit: I now see you mentioned this in the second paragraph so my comment is redundant.
- tr1ll10nb1ll 5y agoYou are right about frameworks taking a lot of time and stall your idea if you aren't already good at one. However, if you are alright with not being to able to build your idea right then and there and are willing to extend the timeline by a few weeks, you might learn something new for ideas later. Last year, it took me 8 weeks to build something that could've been done in 4 weeks max but I'm glad I did that because I learnt Django quite well and now I'm using it to build my other ideas.