5 ms·
Being autodidactic myself the best method I've found is to simply over-engineer your personal projects for the sake of learning. I have side projects that I've
by have_faith 5y ago
Being autodidactic myself the best method I've found is to simply over-engineer your personal projects for the sake of learning. I have side projects that I've never even launched that are built using whatever I could find as "best practice" for solving that particular problem at scale.
- tyingq 5y agoIf the original poster's goal is just to learn about things, this seems like a good answer. I would recommend trying one new thing at a time, though, rather than trying to do it all in one experiment. So if you want to move from your current vanilla html/js/css to a multi-tier-with-database, some framework (react/vue/whatever) and containers...pick one to start with. You could, for example, deploy your existing simple stuff using k3s, a single-host, local, simplified kubernetes. Or spend $10-$30/month on a cheap hosted k8s instance, like digital ocean. Or, leave your deployment as-is, and just tackle moving from vanilla html/css/js to vue or react.
- Veen 5y agoThis how I learned various technologies. I often re-implement my personal invoicing system (I'm a freelance copywriter) in whatever technology I am interested in: i) PWA with a react front-end, ii) AWK-based invoice processing iii) massively overcomplicated system based on Elixir and Phoenix Liveview, etc. I've also done something similar with a personal flood monitoring app (I live near a river prone to flooding). I'll never be a real developer, but it helps me to understand the technologies a little and know when they might be useful for something I want to make.
- fellellor 5y agoIf you’ve done all this then how in this world are you not a “real” developer?