Grid is fine, snow is melting, everything is business as usual. CenterPoint had 99.9% deliverability for the past 24 hours, and ERCOT has 14,781 MW in reserve power available (https://www.ercot.com/gridmktinfo/dashboards/gridconditions). Source: I live in Houston.

I know this was tongue in cheek, but c'mon, we can respect each other, right? :)

Don't? He controls our government, not our behavior.

I'm doing my best not to, but we can all observe that Donold has made it acceptable for many people

Unrelated to the discussion of JMAP, but I had the pleasure of helping host the mentioned Inbox Love conference, assisting Josh Baer and Jared Goralnick. That conference was such a fun one!

Targeted, focused conferences like Inbox Love, with 150ish or fewer attendees, are by far my favorite because you can actually get to know folks, ideas flow more easily, and everyone is focused on approximately the same thing. Much better than huge, multi-track conferences. We should host more of those as an industry.

I have two Kasa light strips (KL400) and anecdotally I’ve noticed that its performance degrades every other day or so to the point where it stops responding to change commands.

The fix? Blocking all inbound and outbound WAN (internet) traffic to it. Now works flawlessly, just like you think a light strip would. I only ever want to issue commands locally anyway, and why it should be talking to the broader internet in that case is beyond me.

Still not much, realistically 4096 bytes or less.

Browsers aren’t as much the issue as they’ve been in the past, but I’ve hit snags with proxies, old servers, etc.

How does pagination in urls work nowadays? You'd need ~3 bytes to index a reasonable number of pages naively, no?

But curious what current art is re: performance optimizations between frontend and backend. Or is it simply page indices?

If you do limit/offset on database side, page number is enough. Though this doesn't work well for bigger page numbers. There's other ways to do pagination, e.g. with "cursors", where cursor is simply id of last record on previous page. SQL query is very efficient, but jumping to page X is impossible. In this scenario storing cursors for past pages is needed

There are libraries for Ecto that help with this.

https://github.com/duffelhq/paginator

Careful that this library last I used it (2020 or so) used a particularly insecure encoding of the cursor that basically allows remote execution. Not sure if they ever addressed it.

Here's the fork I created at the time to work around some of these issues: https://github.com/1player/paginator

This looks like it was fixed

* https://github.com/duffelhq/paginator/blob/main/lib/paginato...

* https://github.com/duffelhq/paginator/blob/main/test/paginat...

Thanks to thread for the informative responses! (And the useful README on your fork/the upstream)

I try to assume someone's thought of better than the best I could, or at least learned the hard way what edge cases need to be handled.

Thanks for pointing that out.

I agree that the main takeaway is knowing when to switch. Having a mental model for this makes many future discussions and decisions much easier, because this seems to be a conundrum that comes up frequently (even for me inside of a large tech organization!).

Based on my experience, I'd suggest the pivot point occurs before even starting: it should pivot around who is building and maintaining the system. If you have the experience needed to quickly develop a solution in code, do it in code. If not, because this is a non-technical team without technical resources, do it in low code. Simple as that.

My team does Wednesday to Wednesday for many of the same reasons mentioned in the article, and it works great. We switch at 11am and hold a hand-off meeting at that time, and invite the whole team.

Hand-off meetings with the whole team work really well (in my opinion!) when you have a relatively small team--we have 9 FT teammates. Often someone else may have been delegated the page or bug that arose and can discuss how they handled it, or someone who wasn't involved may have insight for how to handle a situation better the next time. Since we're all going to be on rotation at least once during a quarter, it's great to know what happened in case a similar page pops up later.

Finally, we also fill out a running Doc before/during the meeting with links to the pages/bugs, along with short descriptions of how they were handled. This forms a great living memory of how to deal with incidents, and is also often the birthplace of new playbooks for handling new types of incidents.

Same here. Except we do a two week rotation, and it aligns with our sprints. The active on-call engineer doesn’t have any assigned sprint work and focuses their effort on fixing bugs or cleaning up the backlog when they’re not actively triaging an incident.

I love astronaut.io! Open it in an incognito window so that your YouTube watch history doesn't get too crazy.

Or maybe its a good way to reset it

If I visit Youtube without being logged in, all I see is junk.

Why would a regular user of YouTube ever want to reset their watch history?

Some people don't like living in a personalized bubble.

I only ever watch youtube or view web pages in incognito/guest mode or other browser profile that deletes all cookies when I close it (which I do at the end of every day).

Some people don’t like that YouTube knows too much about them

I watched a few videos then opened YouTube in another tab and checked my watch history. It doesn't show the videos from this site. I think in general it doesn't track embeds from other sites.

Better would be to stop using Youtube's algorithm for discovery - then your watch history is irrelevant.

You can pre-select multiple tabs to add to the group when creating a new one. It will also automatically add newly opened tabs originating from a grouped tab in the same group. Not vertical like TST, but a very nice quality life improvement in the native browser.

Haha! For those unsure, this is one of the co-founders of Figma, and he also maintains esbuild. See the root domain (https://madebyevan.com/).

Just saw his WebGL water running on HaikuOS Firefox this morning. It's quite a strange thing to see the same name like this.

I second that. I've only had a chance to buy one PC from them (I usually run Macs), but the level of attention to detail and customer service from Puget was bar none the best I've had from any tech outfit.