It's frustrating not being able to send email for my hobby projects even if I follow all the rules and have the correct headers. I enjoyed reading jeremyevan's post on self hosting email, but it's only for receive and not send https://code.jeremyevans.net/2021-07-29-running-my-own-email...
It changed the cost/benefits for papercuts. Instead of thinking, that's annoying, but not annoying enough to fix, I can spend a few minutes running things specific to my configuration. Fixing bluetooth, fingerprint readers were recent ones.
I used to have a floppy and a mini-cd boot version of these. The mini-cd looks like a credit card and fit into a standard size cd drive. Reading the history of the project is a bit of a bummer, but still love the project ethos.
Correct and performant way to calculate historical value of a portfolio. I want a pure function, but taking a date as input is insufficient because users can edit holdings, and securities can split.
Weighing the tradeoffs of doing this calculation server or client side. That'll be an architecture shift away from my current set of background jobs fetching state and towards something more functional and on-demand.
I like reading to my kids and try to read to them in English and Mandarin. My Chinese is conversational, but I have a hard time finding books for them because I’m not good at writing. Something like this with language learning tools would be awesome.
I also like making up stories when we go on hikes. Long, rambling stories about unicorns befriending spiders and flying to faraway lands.
Like the layout tiles you have for the photo thumbnails. Will dig through and learn some css. Have struggled with different size content to create a compact masonry layout.
Living in hongkong for a few months, and absolutely love exploring the different neighborhoods. I’d love something like this or walkscore but for local guides to contribute.
Radio is so much fun to learn. It’s liberating to learn for curiosity and joy rather than commercialization. The community is welcoming, and while not directly translatable for most paid work, it does teach general problem solving skills.
Redesigning investment holdings for wider screens and leaning on hotwired turbo frames. Thankful for once-campfire as a reference for how to structure the backend. The lazy loading attribute works great with css media queries to display more on larger viewports.
Enjoying learning modern css in general. App uses tailwind, but did experiment with just css on the homepage. Letting the design emerge organically from using it daily, prototype with tailwind, then slim it back down with plain css.
Looks good! Appreciate that it’s a pwa instead of an app because it’d be something I use rarely. My issue isnt with the app, it’s that I’d have to remember to upload a receipt and also to find it in this app if I needed it again.
3 years. Left work because I felt comfortable with finances and family life, but wanted to try something different. It’s been fun working on personal projects and sharpening old tools. Still figuring out what I want to do long term. Some ideas include becoming a CFP because I like helping people with their finances, working for a tech company in that domain, or expanding the personal project (jch.app) and building more community.
In a good headspace now, right after the first year was feeling lost on where to go next.
Ya, no need comments or updates to it either. But thought it was an interesting piece of web development that's come up in every web framework and server, but has not been pushed into the browser. Would be interesting as a js polyfill even.
Thanks for touching on accessibility. I believe that good accessibility leads to a better design. The nice thing about starting with HTML is there are good defaults.
I wrote another post about building a search form about progressively enhancing a search form (https://jch.github.io/posts/2025-01-30-building-modern-searc...). Starting with semantic <search> and <input> elements gives sane browser and screenreader behavior.
Perhaps my title came on too strong, but I'm not advocating against javascript. It's more about understanding capabilities HTML and CSS can handle, and what is better suited for JS.
The guide is concise and well written. I like how it builds in the same sequence I blogged about: HTML, CSS, JS, and introduces each in a small way with links for further study. I like how it starts with a static site, but I think the end of the guide could include an example for server side processing. It was clever to use 3rd party example like search with fetch, but an example with a small JS backend to process a form and persist to a database / file would tie it together. It sounds like server-side is out of scope for the framework, so perhaps a few examples of small backends and how to plug in?