code logs -> 2019 -> Fri, 25 Jan 2019< code.20190124.log - code.20190126.log >
--- Log opened Fri Jan 25 00:00:59 2019
00:29 Degi_ [Degi@Nightstar-naa.dp5.104.185.IP] has quit [Connection closed]
00:36 celmin|away is now known as celticminstrel
00:43 Degi [Degi@Nightstar-r9m2o8.dyn.telefonica.de] has joined #code
01:17 Degi [Degi@Nightstar-r9m2o8.dyn.telefonica.de] has quit [Ping timeout: 121 seconds]
02:25
<&[R]>
<nulluser> Teth: Code Rodeo. The players write programs that can survive random bit mutations the longest and still produce correct output. Size limited.
02:42
<&Reiver>
um
02:43
<&McMartin>
Isn't that going to be golfing mixed with a buffer you never check for the rest of the limit?
02:43
<&McMartin>
And then a lottery based on that to see who wins~
02:44 * Reiver ponders. You could defeat the lottery by having multiple random tests done per bit of code, but then it becomes golfing again, with size limits determined by dint of statistical analysis instead of just counting.
02:45
<&Reiver>
OTOH I do wonder if you could instead write code to be parsed in similar ways to bit padding, but... yeah, you still need /something/ to be read once to understand how to read the rest.
02:45
<&McMartin>
My operating principle here is that any bit that can be changed without altering the output didn't need to be there in the first place.
02:46
<&McMartin>
And therefore is just padding
03:02
<&Reiver>
I was thinking more from the point of view of something akin to souped up parity bits and/or RAID configurations
03:03
<&Reiver>
This might, granted, require whole new languages to be written, at which point the compiler is the thing doing the real work and should be target to the bit-flips... but then again, code golf languages don't require their interpreters to be measured in the limit, either.
03:04
<&[R]>
I'd just ablatively pad the entire program, let the random bias itself into my maxed size padding
04:46 Derakon is now known as Derakon[AFK]
05:10 celticminstrel is now known as celmin|sleep
05:16
<@iospace>
so one of the jobs I was felt I made a lot of qualifications for was "thanks but no thanks"
05:16
<@iospace>
uuuuuurgh
05:41
<&McMartin>
boo :(
05:50 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has joined #code
05:50 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
05:54 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
06:00 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
06:44 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has quit [Connection reset by peer]
10:12 Kindamoody[zZz] is now known as Kindamoody
10:30 Kindamoody is now known as Kindamoody|out
12:17 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
12:17 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
12:33 Reiv [NSkiwiirc@Nightstar-ih0uis.global-gateway.net.nz] has quit [[NS] Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
13:17 Kindamoody|out is now known as Kindamoody
13:55 celmin|sleep is now known as celmin|away
15:57 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
15:57 mode/#code [+qo Vornicus Vornicus] by ChanServ
16:39 Kindamoody [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has quit [[NS] Quit: bbl]
17:10 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
17:11 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
18:00 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
18:27
<@iospace>
well
18:27
<@iospace>
i'm starting to dig into "software engineer" jobs
18:27
<@iospace>
I think I exhausted all the embedded/firmware openings
21:30 Kindamoody|autojoin [Kindamoody@Nightstar-eubaqc.tbcn.telia.com] has joined #code
21:30 mode/#code [+o Kindamoody|autojoin] by ChanServ
21:31 Kindamoody|autojoin is now known as Kindamoody
23:24 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Operation timed out]
23:50
<&McMartin>
iospace: Just heard back from my contact with zero leads :/
23:50
<&McMartin>
Have a pretend cup of tea in sympathy
--- Log closed Sat Jan 26 00:00:00 2019
code logs -> 2019 -> Fri, 25 Jan 2019< code.20190124.log - code.20190126.log >

[ Latest log file ]