I’ve been thinking about a learning + portfolio experiment and wanted to get some opinions from people who’ve tried similar things.
The idea is simple:
build the exact same small project in multiple web frameworks (frontend and/or backend), keeping the features as identical as possible.
The goal wouldn’t be to master every framework, but to:
- understand the trade-offs between them
- see how opinionated each one is
- compare setup time, DX, and code complexity
- get better at spotting patterns that transfer between frameworks
I feel like this could be a really good way to level up beyond just “learning one stack”.
The questions I’m stuck on
1. Is this actually a good idea?
Or does it end up being shallow learning compared to going deep into one framework?
2.…
I’ve been thinking about a learning + portfolio experiment and wanted to get some opinions from people who’ve tried similar things.
The idea is simple:
build the exact same small project in multiple web frameworks (frontend and/or backend), keeping the features as identical as possible.
The goal wouldn’t be to master every framework, but to:
- understand the trade-offs between them
- see how opinionated each one is
- compare setup time, DX, and code complexity
- get better at spotting patterns that transfer between frameworks
I feel like this could be a really good way to level up beyond just “learning one stack”.
The questions I’m stuck on
1. Is this actually a good idea?
Or does it end up being shallow learning compared to going deep into one framework?
2. What’s the best project to use for this?
I want something:
- small but real
- mostly CRUD
- not too UI-heavy
- easy to keep consistent across frameworks
Some ideas I’ve considered:
- a simple notes app
- a todo app with basic auth
- a link shortener
- a minimal blog (posts + editor)
If you’ve done something like this before, I’d love to know:
- what project you used
- how many frameworks you tried before it stopped being useful
- whether it helped long-term or just felt repetitive
Any advice appreciated