More recent screens.
@laura I mean, at least temporarily. 😄 (These things happen, nothing to worry about. Ima just mark them all as read, and my RSS reader will have purged most older entries by the morning. Still curious, though: why include all of your blog posts in your feed, rather than, say, the 10 or 20 most recent items?)
Hebben we in Antwerpen ook. “There’s a Wire Above Manhattan That You’ve Probably Never Noticed” https://getpocket.com/explore/item/there-s-a-wire-above-manhattan-that-you-ve-probably-never-noticed
Looking to start a personal wiki to save all sorts of little bits of knowledge, for use at a later time. Like information I come across online, on a particular guitar model or arcade cabinet. Or code snippets—why not? Then again, those are all things I _could_ just write about right here.
Blogging ain't dead. This is my story of running a blog for 20 years (https://beko.famkos.net/b/_VJ)
Should look into stopping Aperture from removing things like tables and figures. One day.
I’d registered the name ages ago, for my, well, “crowdsourced ‘TripAdvisor’ for nerds.” Figured I’d use it on something that could actually work.
(I'd guess "yes," twice, to keep things sort of standard and more easily extendible. I.e., use a sort of calendar table. But I'm kinda dumb, so.)
So, when you're designing a (calendar-like) application where, say, an event can have multiple (rather random) dates, and a date multiple evens, do you (1) use a pivot table, and (2) prepopulate a dates table with every possible date for the next 20 years or so? I was wondering if one can't simply skip the dates table, which would only hold _dates_, or rather, use it itself as a pivot table. (Would it matter? Also, stuffing multiple dates in a serialized array or JSON will not do.)
I don't particularly care much, in this case, but I may be setting up a somewhat more business-critical service in the near future, and now I'm wondering if I should. Although I think if I'm able to spin up a second instance from a snapshot or so really quick, that'd be okay. Or run it locally, should things really go to shit. (It'd be a pure back-end thingy, most likely, like fetch data, render to files, push to server.)
My OVH VPS became irresponsive last night—not sure what happened, haven't had a chance to look. So I rebooted it from their control panel, and it got stuck at 25%, and nothing worked anymore: "A process has already been initiated." And then eight hours later someone on their end picked up my ticket and just rebooted it.
He said, fully aware that no such thing would ever happen.
Says the fellah whose biggest monthly expense is ... stocks.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!