Priyankar Pal

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

When you're just starting, those boring details are exactly the things you should be practicing. Frameworks automate the boring stuff Frameworks are great at automating all that boring stuff, like boilerplate code, authentication, and database migrations. When you use a framework, you're missing out on all that good stuff.

If You're Learning Back-end, Don't Start with Frameworks

Frameworks are easy to learn, that's the whole point

I made the mistake of starting with Django

How far down the rabbit hole do I need to go?

Lastly, full-stack and back-end development are different

I don’t agree at all. Starting with frameworks helps you focus on 1 thing at the time and build something without having a global understanding. Plus the framework teaches you solid principles, good architecture and code organisation. I have learned so much reading and understanding the framework I was using

Controversial article, as the author states that he started using Django framework before learning from scratch.
He only knew what he needed to pay attention to BECAUSE he started using a framework that gave him the basics

I would probably say that as a beginner, you need to start with a framework. But once you’re successfully able to complete a project, try to re-do it without using the framework. This helps you figure out why the framework is indeed needed.

According to this I will have to learn assemble and machine before any thing 😂😂

Use a framework, don’t use a framework, it doesn’t matter. As long as you understand the shits and not just copying them.