11–19 of 19 posts
These roadmaps (especially frontend) might be helpful: https://roadmap.sh/roadmaps
Laravel is even more popular now. I'd checkout Laravel again, Laracasts.com might be a nice place to start. If you liked Angular checkout Vue and Alpine js. Good luck with your SaaS.
You haven’t missed anything and your skills are still relevant if you want to solve problems . Laravel or Python with server-side rendered pages is still perfectly valid and will be better than the majority of websites today. People who say otherwise have their career at stake because they know nothing but React and need to use it everywhere (regardless of whether it’s necessary) to ensure their survival. You don’t n…
Laravel is still awesome and VueJS is really popular with Laravel devs right now (afaik). Vue is super easy to work with and there's a ton of documentation and examples for integrating it with Laravel. If I were in your position, I'd go with that stack.
I find Django a good place for rapid development, Laravel is also great and cranking out new features all the time, but I feel the rate of change is too high for me. There's lots of options for frontend but since you wrote "Mobile accessibility (PWA or native) and having a nice design are a must", there's no way around than digging deeper into frontend / design. I haven't seen a no-code tool (a la Webflow) that trans…
way more complicated how?
Id start with Freecodecamp - you dont have to complete the modules but chose the ones relevat to you
Fundaments haven't changed much. Pick a JS framework and go from there. It's gotten more complicated, indeed. But, if you're building projects of your own, you're free to ignore it as there are not that many palpable benefits, and your users / customers couldn't care less about underlying tech stack.
Fundaments haven't changed much. Pick a JS framework and go from there. It's gotten more complicated, indeed. But, if you're building projects of your own, you're free to ignore it as there are not that many palpable benefits, and your users / customers couldn't care less about underlying tech stack.
Eactly. I was targeting personal ease of use. I remember that handling authentification in JS was a pure nightmare, so I have a strong bias towards frameworks handling that for me.