I don't know if it's possible to get a good answer to this but: if you learned how to make websites with, like, users who can login and do things where the website stores stuff in a database, without doing it as a job, how did you do it?
I feel like in principle I know all of the basic pieces (HTTP, HTML, CSS, SQL, CORS, various programming languages, etc), but also somehow it still feels extremely hard to me
(no more replies please there are enough)
@b0rk It kinda became a job, but wasn't when I read Learn Python the Hard Way and Two Scoops of Django.
I think I get what you say about knowing the constituent parts... "but then what?!". I guess the way to go is to not be so concerned with all the nitty-gritty stuff (until you actually *need* that depth). Like, why design authentication from the ground-up when you get it for free with $FRAMEWORK?
@b0rk I want to add that I think the web dev beat is very very very hard to follow. So many new things, like, say, "what's bun even? do I need it?"
The fact that I'm struggling to concisely describe what I'm confused about is very telling. But basically JS build pipelines. Wanted to call it "frontend code", but there's stuff like SvelteKit and Nuxt now so that's actually not true...
Luckily I'm not in the customer-facing end of things but I tend to stick with htmx/alpine for web2.0 behavior
Julia Evans
Jens Christian