2025/04/22

Newest at the top

2025-04-22 19:02:32 +0200sprotte24(~sprotte24@134.245.44.88)
2025-04-22 19:01:49 +0200tromp(~textual@2001:1c00:3487:1b00:81b9:54c7:add1:2ebe)
2025-04-22 19:00:13 +0200Square2(~Square4@user/square) (Remote host closed the connection)
2025-04-22 19:00:11 +0200Square3(~Square@user/square) Square
2025-04-22 18:52:25 +0200acidjnk(~acidjnk@p200300d6e71c4f31f097d80b541a7919.dip0.t-ipconnect.de) acidjnk
2025-04-22 18:51:52 +0200 <EvanR> would be nice if that meant it all still worked xD
2025-04-22 18:51:01 +0200rinaldo(~rinaldosu@2001:1c00:a01:bc00:f59:a3e2:b0c6:b85b) (Client Quit)
2025-04-22 18:49:29 +0200rinaldo(~rinaldosu@2001:1c00:a01:bc00:f59:a3e2:b0c6:b85b)
2025-04-22 18:42:10 +0200notdabs(~Owner@2600:1700:69cf:9000:116f:7547:e97e:51d0)
2025-04-22 18:37:11 +0200tromp(~textual@2001:1c00:3487:1b00:81b9:54c7:add1:2ebe) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-04-22 18:32:55 +0200econo_(uid147250@id-147250.tinside.irccloud.com)
2025-04-22 18:31:03 +0200dhil(~dhil@5.151.29.137) dhil
2025-04-22 18:30:45 +0200fp(~Thunderbi@2001:708:20:1406::1370) (Ping timeout: 268 seconds)
2025-04-22 18:21:03 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 276 seconds)
2025-04-22 18:20:55 +0200tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2025-04-22 18:17:53 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-04-22 18:17:50 +0200harveypwca(~harveypwc@2601:246:d080:f6e0:27d6:8cc7:eca9:c46c) (Quit: Leaving)
2025-04-22 18:17:27 +0200euleritian(~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de)
2025-04-22 18:17:09 +0200euleritian(~euleritia@dynamic-176-000-129-028.176.0.pool.telefonica.de) (Read error: Connection reset by peer)
2025-04-22 18:06:14 +0200 <haskellbridge> <Liamzee> last update in 2024
2025-04-22 18:06:08 +0200 <haskellbridge> <Liamzee> https://github.com/orgs/polimorphic/repositories
2025-04-22 18:05:25 +0200 <haskellbridge> <Liamzee> https://www.polimorphic.com
2025-04-22 18:05:25 +0200 <haskellbridge> <Liamzee> huh, they're still alive?
2025-04-22 18:04:13 +0200sprotte24(~sprotte24@p200300d16f2aeb0085c5313dace495b4.dip0.t-ipconnect.de) (Quit: Leaving)
2025-04-22 18:01:46 +0200inca(~inca@pool-96-255-212-224.washdc.fios.verizon.net)
2025-04-22 18:00:58 +0200xstill_(xstill@fimu/xstill) xstill
2025-04-22 18:00:07 +0200xstill_(xstill@fimu/xstill) (Ping timeout: 244 seconds)
2025-04-22 17:59:52 +0200UltraFuzzy(~UltraFuzz@c-24-12-96-73.hsd1.il.comcast.net) ()
2025-04-22 17:59:21 +0200euleritian(~euleritia@dynamic-176-000-129-028.176.0.pool.telefonica.de)
2025-04-22 17:59:21 +0200P1RATEZ(~piratez@user/p1ratez) P1RATEZ
2025-04-22 17:57:29 +0200euleritian(~euleritia@dynamic-176-000-197-007.176.0.pool.telefonica.de) (Ping timeout: 252 seconds)
2025-04-22 17:56:47 +0200Guest55(~Guest55@149.115.69.184) (Client Quit)
2025-04-22 17:56:06 +0200Guest55(~Guest55@149.115.69.184)
2025-04-22 17:53:49 +0200inca(~inca@pool-96-255-212-224.washdc.fios.verizon.net) (Ping timeout: 252 seconds)
2025-04-22 17:53:14 +0200UltraFuzzy(~UltraFuzz@c-24-12-96-73.hsd1.il.comcast.net)
2025-04-22 17:52:30 +0200chele(~chele@user/chele) (Remote host closed the connection)
2025-04-22 17:51:25 +0200 <tomsmeding> okay that makes sense
2025-04-22 17:51:18 +0200 <lambdabot> 0.1
2025-04-22 17:51:16 +0200 <tomsmeding> > 1/20 + 19/20 * 1/19
2025-04-22 17:50:40 +0200 <EvanR> lol
2025-04-22 17:50:39 +0200 <int-e> EvanR: That only works for binary answers.
2025-04-22 17:50:35 +0200 <tomsmeding> if only you could make wrong code right by passing it through a NOT gate
2025-04-22 17:50:15 +0200 <EvanR> I feel like monochrome should suggest taking the 100% wrong LLM and post process it with a NOT gate
2025-04-22 17:50:08 +0200amadaluzia(~amadaluzi@2a00:23c7:ed8b:6701:6e86:b77b:c1b:7762) (Quit: Hi, this is Paul Allen. I'm being called away to London for a few days. Meredith, I'll call you when I get back. Hasta la vista, baby.)
2025-04-22 17:49:46 +0200 <int-e> . o O ( 19 hoomans and one LLM )
2025-04-22 17:49:12 +0200 <int-e> But really... it becomes a modelling question. Maybe you have 20 programmers, and 19 of them are perfect while one of them produces faulty code all the time, and you assign two programmers to implement the two functions (one each).
2025-04-22 17:49:11 +0200 <tomsmeding> if f1 is faulty in 5% of the cases and f2 is also faulty in 5% of the cases, _at most_ 10% of the cases see one of the two functions being faulty
2025-04-22 17:48:42 +0200 <tomsmeding> no
2025-04-22 17:48:37 +0200 <EvanR> could you go below 90%
2025-04-22 17:48:34 +0200inca(~inca@pool-96-255-212-224.washdc.fios.verizon.net)