Development: It is a systematic cycle of thinking, plotting and working.
According to me, working is the easiest part of the development cycle. Thinking and plotting the ways to work on the things you wanna make will be tired some and time consuming.
Most of the beginner developers skip initial two stages of development and jump start into development for faster results. But they will end up with dissatisfaction of their planned work or give up facing lot of challenges on the way due to no planning.
People start as coders, writing code to achieve their desired product or solve a problem. But coders become software engineers when they understand the mindsets of development.
Software engineer or i call them developers solve problems by thinking and plotting [in software terms we call it Requirements gathering and design. boring stuffs for software engineers out there but these blog is for rookie coders 🙂 no insults buddy ]
This will give u the blueprint to handle the project and how to split the project into segments [ technically called units ] to work on them, so you can relate them when you’re working and makes sense to you.
As a coder [rookie] i find myself satisfied to spend a lot of time searching for best possible tech stack [ rookie: best possible frontend framework is NextJS check ✅, best possible UI library Mantine.dev check ✅] by spending 14 billion hours spending to research them feels satisfactory.
But the thing is that end user [customer] doesn’t give a f**k about what stack you use. For a SDE, a tech stack is a tool for him to solve the problem he/she wanna solve. The thing matters most for him is to solve the problem not the tech stack.
So bro / sis, next time you wanna start with a project, make a blue print like create a DB design and stakeholder roles [for my SDE friends out there] and pick of the tech stack you’re familiar or if you find new to coding start with the top search results like MERN, MEAN or whatever. Choose the beginner friendly stuff when u start instead of a cachy one.
Learning to code requires hardwork. Becoming a better SDE requires smartness and working less.
— Myself