One thing i undervalued for most of my career was just reading code.
Get into the habit of digging into open source repos that catch your curiousity, and try to grok the way the project is layed out, what namespaces/files exist, what some of the core functions are, where the complexity is housed.
It’s all about getting exposure to patterns, especially if there aren’t other people to work with in your day to day.
Not a direct answer, but for an explanation and history of CORS, this was a fun talk at stangeloop last year: https://youtube.com/watch?v=0YJ-yhoJh2I
I did this with apollo a few times, but changed the icon to reset my eye/muscle memory. Going to leave it for a while during the mourning period
I’m liking wefwef, as a PWA it feels pretty much just like Apollo
I knew I'd seen something like this, and was very happy to find this in my notes from a few years ago: https://devchallenges.io/
There are a few full-stack 'challenges', ultimately building up to a twitter and then trello clone. Maybe it's the kind of thing you're looking for? I'm not sure if the submit + review portion of the site is still a thing, but w/e, you can still take the ideas and build your own thing.
Here's a quick article on it from the creator: https://dev.to/nghiemthu/8-projects-with-modern-designs-to-become-a-full-stack-master-2020-14j9
One thought I had when looking through these is that keeping the project small (e.g. an image uploader that adds a filter and renders it) might be preferrable to an otherwise larger/never-ending project. OR you could do more design work for a larger site if that's the part of software you want to practice.
You might also look into coding 'kata' or something like advent of code, tho that's definitely a different direction and lower-level scope.
Building stuff is fun! Good luck with it!
So glad this landed! One of my all-time faves!
Maybe you could dig into a few open-source clients to see how they work with it?
E.g. someone shared a basic lemmy viewer in godot the other day: https://github.com/sevonj/gdlm - it’s rough but probably not too much to read through. Was posted in /c/godot: https://programming.dev/post/48482
I'm curious about this even outside of a mlem perspective - do beehaw posts accumulate downvotes but just not display them, or are they accumulated and shown to downvote-enabled instances, or are they just thrown away?
i think it’s all good for growth, good or bad - learning to evaluate it can start any time. Even if you don’t know whether it’s good or bad, you’re learning to recognize patterns, evaluate quality and build up opinions. If it’s bad, why, what would you change? If you don’t know it’s bad, you’re just noting a new pattern to try/compare to the others.
You’ve got to develop your own opinions about things anyway, might as well get better at reading/evaluating code sooner than later