Post B2W0aASvjyZuI3Ebh2 by b0rk@social.jvns.ca
(DIR) More posts by b0rk@social.jvns.ca
(DIR) Post #B2W0ZsPmqvMuJ5cqIK by b0rk@social.jvns.ca
2026-01-20T14:34:00Z
1 likes, 0 repeats
i like to make websites and I've been slowly realizing that my requirements for making websites might be a little weird- I have maybe 20 websites (mostly static but not all)- I want to spend basically 0 time maintaining them, maybe 5 minutes every 2 months at most- I need to be able to ignore a project for 3 years and then come back and be able to develop it easilyi feel like all of this stuff makes my choice of tech stack different than if I worked on one site full-time
(DIR) Post #B2W0a1LrcsZu1WrKvg by b0rk@social.jvns.ca
2026-01-20T17:22:13Z
0 likes, 0 repeats
a few people have been asking what my typical setup is for "running websites that I can completely ignore and spend 0 time maintaining" so I wrote down a few thoughtshttps://gist.github.com/jvns/5bd9283d7abd5ceb26eb7ed28afe3030
(DIR) Post #B2W0aASvjyZuI3Ebh2 by b0rk@social.jvns.ca
2026-01-20T17:29:17Z
0 likes, 0 repeats
it feels hard to talk about how to write websites that feel manageable to maintain with like 0.5% of my brain because there are a thousand tiny and not always logical decisions like "use bash scripts to run my local dev server, because then it's `bash scripts/run.sh` no matter what programming language the project is in" or "refuse to use any database other than SQLite because I had a bad experience operating Postgres once and I feel more comfortable with sqlite"
(DIR) Post #B2W0aJEj89Z3UbetIu by b0rk@social.jvns.ca
2026-01-20T18:52:44Z
0 likes, 0 repeats
though I guess a big part of "how to make website in a way where it will keep working and be easy to develop in the future" is figuring what kind of backwards compatibility guarantees various software has (which I have realized is really a question about human processes and priorities and culture, and so isn't really straightforward)(4/?)