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.
The CSS for this is indeed tricky. I figured out this layout 5 years ago in the v1 and forgot how it works, just took it over as it looks good. The key is that not all rows are exactly the same height. There are small differences that allow photos to fit horizontally.
I also tried the vertical masonry layout, which looks good, but makes no sense if your photos have a chronological order...
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.
Totally get that, most of us don't want a full app for something we use rarely. That's why I kept it as a PWA as it installs in KBs and doesn't take real storage.
On the "having to remember" part: if you've uploaded a receipt once, SlipCrate sends expiry nudges (30, 15, 7, and 1 day before). I can include the app name in the notification so it's obvious where it came from.
I'm also exploring light-touch options so you don't have to remember at all: optional monthly email/push "bought anything new?" reminder, email-forwarding of receipts, or a unique upload address. If you had to pick one "least annoying" flow, which would it be?
reply