How do I plan out my software development projects (talks about agile development)

You get too small, there is no point of planning; you get too big and planning becomes like a small project.
What you've explained is the middle ground, which is cool IMO.

Love this. I'm always second guessing my build layout / structures etc. Especially if it's full stack.

So you're saying you don't use any structure?

Something I’ve recently learned is that a design you come up with is not the final one. Things change, requirements change, etc. for example, I learned about db migrations. I thought I had to have everything thought out for the db design, but thanks to db migrations, I can have the bare minimum or essentials in my design and use tooling to evolve its design as I build more features on the front and backend.

I just like to sit and describe some project features after that I just start to code and another features always arrive

For me it's event storming (it gives you all the queries and mutations) the wireframe it gives you a whole idea about the app and the design + the bpmn process

Being agile alone is worthwhile. I like the flow of 50% of work is producing it the other 50% goes to cleaning, documenting, testing.

However if you work with others, you have to be able to communicating strategies, ideas, flows. And truth be told, if you only stick to an "agile" mindset, you won't practice the communicational part of a job.

The good approach depends on your goals. For very small projects. Just smack some code.
For medium or large projects - consider maintainability as a priority. Coding in the long run is 80% reading and 20% writing. (A scaffolding/prototype project is a small project on its own where testing the idea should come as quickly as you can reasonably manage)

System design is not waterfall, please don't mislead your audience. In fact it's very common when interview for Sr/lead/architect roles. If more forethought was put into systems especially cloud systems we wouldn't have so much of the sh$t software we have today

Is it possible to create a video about this process in more detail please? I am actually this type which create a very large diagram every single time I create a project. For me, the problem of getting slowly futures to the specific project, is that sometime I forget which primary key will be in what table. It’s just an example.

I never used UML, honestly, it's wasting of time.

wow! I have been searching these kind of videos for long, Thank you for making this video! please make a video on "the process of developing a software" I mean, I want to see how the SDLC is executed and what problems might a developer face and everything. I wanted to see the whole process of making a software. from UI/UX design and everything, I don't know how to explain, I am just an amateur.

I think the "just code it" method is good if you know what you're doing, but if you're just learning, the flowchart method seems to work best.

thanks for sharing mate!

AMAZING, MAN! You're fantastic

Hey man, just seen a few videos of yours and just wanted to thank you for them, just loads of value and insights I haven't seen elsewhere, great work :)

What do you recommend/think the best way to get good/learn css is?

Doing my university dissertation at the moment and seriously struggling through the diagram section. I know they're not going to help me! I just want to build, and learn from that.

hey, do you ever use any other editor? like webstorm

Love your content! Question, how do the code refactoring projects get picked? I recently finished a mern stack app with redux and I’m curious how to make it better and cleaner. Is there somewhere I can send it for consideration?

Good job babe!!!!❤

Actionly, i love so much this type of content, Thanks bro

I agree but the diagram way is taught heavily in degrees. In mine they don’t even care about the code and care more about the diagrams

Thanks, great concept!

I find the mocks annoying because I'm never the one making them, in my job I've had management make the mocks but management doesn't know how to code so it's like, do we build to your mock that you wasted three hours on or do we do mvp and iterate as needed?

Agreed diagrams are for beta.

I totally aggree with your points. I recently caught myself overengineering in my project and now I always have to tell myself that if sth. is needed in the future, I'll implement it and don't need to care about it rn.

Doesn't mean the features shouldn't be thought through!
And a rough plan always helps - but that's it.

Totally agree, I use user stories and ship the necessary steps as soon as possible. Move fast, break fast mindset is how many got ahead at the time.

Please upload beginner project tutorials