So Recently I've been working on a FullStack MERN Webapp. Just to give an idea I have done a few mini projects and even worked collaboratively whil...
For further actions, you may consider blocking this person and/or reporting abuse
Nice point of view there friend, but I disagree with the 3rd one.
In my opinion you should avoid libraries and packages when you can and use them when you need to save time.
Actually coding your own solution will help you better understand how this particular solution works and also you do not depend on someone elses code, which I consider a very big PLUS.
Long story short, I personally use packages and libraries only to save time, but on personal projects where the goal is to LEARN, I avoid them.
Anyway, nice post!
Oh yeah, I agree. The reason i did not want to use any packages or libraries was solely for the purpose of learning. But eventually it started to fire back, as I had hard time keeping track of where everything was.
So I reckon we can use packagaes/libraries to save some time and make our code be tad bit cleaner.
I think this is one of those marks of maturing as a developer; Developing a sense of nuance around when to use a library and when to avoid it.
I second this.
If you need to prototype mobile app quickly: Flutter + Dart;
If you need to prototype web app quickly: Svelte + TailwindCSS;
If you need to prototype desktop app quickly: Electron (if you already know web technologies) or C# etc.
Thanks for taking out time and explaining it. Tbh I'm still a beginner in Web development. So jumping right into huge frameworks or working with multiple different libraries doesn't really seem that productive to me.
However, the points that you have written will help me eventually and I will make my way to become better at it.
Also I do know Postgres and have worked with server side rendering, it truly is a work of art xD
Biggest mistake is not using a fullstack framework like RedwoodJS.
I will definitely check it out. Thanks for the suggestion
I agree with point 1, 3 ,and 4.
I would say it takes 1-2 years to build a solid application with everything from unit test to deployment (CI/CD), etc....
You should read clean architecture.
Well it was a project for educational purposes. So it doesn't really have to scale that high. But I agree, it definitely needs time to get everything into a structure.
And thanks for the suggestion. I will definitely read it.
I agree. The concepts won't really change. I'll switch it up a little and try to learn Rails
I see. What would you suggest for let's say a MERN app?
Also I meant the project design and workflow
Sorry but can you explain it a bit?