2026/03/22

2026-03-22 00:00:34 +0100haskellbridge(~hackager@96.28.224.214) (Read error: Connection reset by peer)
2026-03-22 00:07:00 +0100haskellbridge(~hackager@96.28.224.214) hackager
2026-03-22 01:30:19 +0100down200(~down200@shell.lug.mtu.edu) (Ping timeout: 268 seconds)
2026-03-22 01:31:17 +0100down200(~down200@shell.lug.mtu.edu) down200
2026-03-22 01:40:08 +0100 <liskin> Maybe we just care too much
2026-03-22 01:41:22 +0100 <liskin> You're not meant to read the code, just like you don't read the generated assembly unless you're not getting the vector instructions you hoped for
2026-03-22 01:41:51 +0100 <liskin> Don't think I can rewire my brain for that just yet
2026-03-22 01:42:15 +0100 <liskin> Also it's sunny so fuck computers let's attach wheels to feet and drink
2026-03-22 02:53:46 +0100tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2026-03-22 05:06:57 +0100rekahsoft(~rekahsoft@bras-base-orllon1103w-grc-20-76-67-111-168.dsl.bell.ca) (Remote host closed the connection)
2026-03-22 05:09:22 +0100portnov(~portnov@79.134.10.7) portnov
2026-03-22 08:38:31 +0100 <haskellbridge> <g​alactic_starfish> liskin: I tend to kick off a GitHub cloud agent whenever I find a bug in software I use myself. And then if it works OK after I go and build it later, then I consider contributing a more clean version back to the main repo. But yeah, slow af
2026-03-22 08:39:24 +0100 <haskellbridge> <g​alactic_starfish> or edge in my usecase *
2026-03-22 08:43:53 +0100 <haskellbridge> <g​alactic_starfish> I have been enjoying copilot + good design / architecture efforts and APOSD principles in prompt form... It has been working well professionally, as well as in my hobby projects.
2026-03-22 08:45:06 +0100 <haskellbridge> <g​alactic_starfish> I also review everything manually... But most of it tends to be a skim. I also have the agent pause after every TODO step and I'll either adjust its implementation or give it clarifying details that it missed or I didn't specify.
2026-03-22 08:45:43 +0100 <haskellbridge> <g​alactic_starfish> Subagents are also crucial... Long running agents have too much context drift / rot... It quickly goes off the rails if it's anything but CRUD.
2026-03-22 08:46:11 +0100 <haskellbridge> <g​alactic_starfish> That said, these experiences are mostly in C#, Java, Typescript and Nix... Not Haskell.
2026-03-22 09:17:07 +0100hiecaq(~hiecaq@user/hiecaq) hiecaq
2026-03-22 12:12:05 +0100portnov(~portnov@79.134.10.7) (Ping timeout: 244 seconds)
2026-03-22 12:27:10 +0100portnov(~portnov@79.134.10.7) portnov
2026-03-22 12:34:21 +0100portnov(~portnov@79.134.10.7) (Ping timeout: 246 seconds)
2026-03-22 12:46:54 +0100portnov(~portnov@79.134.10.7) portnov
2026-03-22 12:49:12 +0100mkoskar(wut@user/mkoskar) (Ping timeout: 255 seconds)
2026-03-22 12:51:27 +0100portnov(~portnov@79.134.10.7) (Ping timeout: 255 seconds)
2026-03-22 12:58:09 +0100mkoskar(wut@user/mkoskar) mkoskar
2026-03-22 13:03:52 +0100portnov(~portnov@79.134.10.7) portnov
2026-03-22 14:06:09 +0100tremon(~tremon@83.80.159.219) tremon
2026-03-22 15:03:01 +0100rekahsoft(~rekahsoft@bras-base-orllon1103w-grc-20-76-67-111-168.dsl.bell.ca) rekahsoft
2026-03-22 15:30:46 +0100rekahsoft(~rekahsoft@bras-base-orllon1103w-grc-20-76-67-111-168.dsl.bell.ca) (Remote host closed the connection)
2026-03-22 17:03:15 +0100hiecaq(~hiecaq@user/hiecaq) (Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.2))
2026-03-22 18:14:16 +0100vados(~vados@46-133-38-139.mobile.vf-ua.net) (Read error: Connection reset by peer)
2026-03-22 18:19:31 +0100vados(~vados@46-133-0-118.mobile.vf-ua.net)
2026-03-22 18:56:27 +0100Digitteknohippie(~user@user/digit) Digit
2026-03-22 18:56:51 +0100Digit(~user@user/digit) (Ping timeout: 255 seconds)
2026-03-22 19:07:39 +0100Digitteknohippie(~user@user/digit) (Ping timeout: 255 seconds)
2026-03-22 19:30:37 +0100Digitteknohippie(~user@user/digit) Digit
2026-03-22 19:40:22 +0100Digitteknohippie(~user@user/digit) (Ping timeout: 276 seconds)
2026-03-22 19:44:15 +0100Digitteknohippie(~user@user/digit) Digit
2026-03-22 19:50:36 +0100DigitteknohippieDigit
2026-03-22 20:25:02 +0100 <haskellbridge> <S​olid> liskin: Yeah, I'm definitely not ready for that :D
2026-03-22 20:25:55 +0100 <haskellbridge> <S​olid> Maybe it's because I don't do this for a job (yet, I guess, with the current situation in academia…), but I was always a bit of a "the path is the goal" type of person
2026-03-22 20:26:47 +0100 <haskellbridge> <S​olid> So using these things for most (all? some?) of my coding just feels like I should rather change the kinds of projects I'm working on, if they're that boring I want to outsource them
2026-03-22 20:28:24 +0100 <haskellbridge> <S​olid> That said, trying to clone "wayland-rs" does sound like something I might want to try next week-ish (from some preliminary tests it's not going super well though… it wanted to use "peek" and "unsafePerformIO" for reading the wire protocol from a bytestring :D Three more cleanup commits it is)
2026-03-22 20:49:25 +0100 <geekosaur> write the core, aibro contrib? 😛
2026-03-22 20:51:10 +0100 <geekosaur> the real question isn't about protocols anyway, it's how do you replace things we use a lot but barely exist (if that much) in wayland. like ManageHooks really wanting Xrm foo that nobody uses even in the X11 world these days
2026-03-22 21:01:04 +0100werneta_(~werneta@71.83.160.242) werneta
2026-03-22 22:19:19 +0100 <haskellbridge> <g​alactic_starfish> Solid: For me, it's less boredom, more that I have so many ideas that implementation speed becomes a very real bottleneck. It's more of a design process, and less of a coding one.
2026-03-22 22:19:22 +0100 <haskellbridge> I totally get enjoying the fine-grained details though. For the longest while I've enjoyed surmounting direct implementation hurdles.
2026-03-22 22:38:08 +0100portnov(~portnov@79.134.10.7) (Remote host closed the connection)
2026-03-22 23:29:07 +0100elarks(~elarks@user/yerrii) (Quit: WeeChat 4.7.1)
2026-03-22 23:38:38 +0100elarks(~elarks@user/yerrii) yerrii