Newest at the top
| 2025-05-06 17:04:44 +0200 | tromp | (~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) |
| 2025-05-06 16:55:59 +0200 | ttybitnik | (~ttybitnik@user/wolper) (Quit: Fading out...) |
| 2025-05-06 16:54:01 +0200 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 244 seconds) |
| 2025-05-06 16:40:37 +0200 | fp | (~Thunderbi@2001:708:20:1406::10c5) (Ping timeout: 276 seconds) |
| 2025-05-06 16:32:54 +0200 | tromp | (~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-05-06 16:25:06 +0200 | ColinRobinson | (~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org)) |
| 2025-05-06 16:19:43 +0200 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2025-05-06 16:16:27 +0200 | euleritian | (~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) |
| 2025-05-06 16:16:10 +0200 | euleritian | (~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-05-06 16:09:08 +0200 | <df> | but time has never been very reliable for that anyway, that's why we invented vector clocks etc |
| 2025-05-06 16:08:25 +0200 | <yin> | wait no, that was Doc Brown |
| 2025-05-06 16:08:25 +0200 | <yin> | "quickly, there's no time!" |
| 2025-05-06 16:08:15 +0200 | <df> | yin: made life easier for a bunch of programmers? ordering events might be tricky though, I admit |
| 2025-05-06 16:07:33 +0200 | hughjfchen | (~hughjfche@vmi2417424.contaboserver.net) hughjfchen |
| 2025-05-06 16:07:26 +0200 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-05-06 16:07:08 +0200 | comerijn | (~merijn@77.242.116.146) (Read error: Connection reset by peer) |
| 2025-05-06 16:06:16 +0200 | hughjfchen | (~hughjfche@vmi2417424.contaboserver.net) (Ping timeout: 244 seconds) |
| 2025-05-06 16:05:47 +0200 | <df> | ... c'mon, somebody's gotta complete the douglas adams quote |
| 2025-05-06 16:05:09 +0200 | <yin> | won't we miss async communication though? oh no what have we done? |
| 2025-05-06 16:02:13 +0200 | <df> | time is an illusion anyway |
| 2025-05-06 16:02:08 +0200 | <df> | good work, we can synchronise the entire world if we try |
| 2025-05-06 16:02:03 +0200 | danza | (~danza@user/danza) (Remote host closed the connection) |
| 2025-05-06 16:01:30 +0200 | <yin> | we'll all be on the same time... soon |
| 2025-05-06 16:01:20 +0200 | <yin> | done. they also wrote it down and will spread the word |
| 2025-05-06 16:01:03 +0200 | danza | (~danza@user/danza) danza |
| 2025-05-06 16:01:01 +0200 | <yin> | wait |
| 2025-05-06 16:00:49 +0200 | <yin> | i'm also telling all my contacts |
| 2025-05-06 16:00:46 +0200 | <df> | ok, so we're sychronised, problem solved ;) |
| 2025-05-06 16:00:24 +0200 | <yin> | df: ok i wrote it down too |
| 2025-05-06 15:58:59 +0200 | <df> | it's 11:27:23 AM |
| 2025-05-06 15:58:32 +0200 | <df> | yin: easily solved, I looked up the time earlier and wrote it down |
| 2025-05-06 15:58:25 +0200 | <haskellbridge> | <maerwald> you can become an LLM input engineer |
| 2025-05-06 15:57:58 +0200 | <yin> | there's that concept again |
| 2025-05-06 15:57:30 +0200 | <haskellbridge> | <maerwald> time for a career change |
| 2025-05-06 15:56:39 +0200 | <yin> | maerwald: i have come to accept that programming is boring any way |
| 2025-05-06 15:55:12 +0200 | <yin> | messy UTC is just a result of that |
| 2025-05-06 15:54:52 +0200 | <yin> | like the need for two people to independently agree on "what time it is now" |
| 2025-05-06 15:54:02 +0200 | <yin> | tomsmeding: oh i mean "time" in general |
| 2025-05-06 15:53:42 +0200 | <haskellbridge> | <maerwald> programming is boring this way |
| 2025-05-06 15:53:32 +0200 | <haskellbridge> | <maerwald> but collaboration in professional setting is mostly dead... people always get pieces of work that they can implement independently and then every team member gets their epics and your grind on your own without any real design or code collaboration |
| 2025-05-06 15:53:18 +0200 | tomsmeding | will be afk for a while |
| 2025-05-06 15:53:06 +0200 | <tomsmeding> | the communication itself is separate |
| 2025-05-06 15:52:59 +0200 | <tomsmeding> | and in any case, if there is a connection, it's between messy time and _planning_ |
| 2025-05-06 15:52:41 +0200 | <tomsmeding> | yin: I never connected messy UTC time to synchronous communication :p |
| 2025-05-06 15:52:27 +0200 | <yin> | true |
| 2025-05-06 15:52:07 +0200 | euleritian | (~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) |
| 2025-05-06 15:51:59 +0200 | <haskellbridge> | <maerwald> pair programming, brainstorming together, etc. does not work on github |
| 2025-05-06 15:51:57 +0200 | euleritian | (~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 276 seconds) |
| 2025-05-06 15:51:51 +0200 | <yin> | did i just ping haskellbridge? :p |
| 2025-05-06 15:51:21 +0200 | <haskellbridge> | <maerwald> no |