code logs -> 2018 -> Tue, 11 Dec 2018< code.20181210.log - code.20181212.log >
--- Log opened Tue Dec 11 00:00:07 2018
01:06 Derakon[AFK] is now known as Derakon
01:14 Degi [Degi@Nightstar-ude8gq.dyn.telefonica.de] has quit [Connection closed]
02:27 VirusJTG [VirusJTG@Nightstar-42s.jso.104.208.IP] has joined #code
02:27 mode/#code [+ao VirusJTG VirusJTG] by ChanServ
05:00 Vornicus [Vorn@Nightstar-sjaki9.res.rr.com] has joined #code
05:00 mode/#code [+qo Vornicus Vornicus] by ChanServ
05:12 himi [sjjf@Nightstar-1drtbs.anu.edu.au] has quit [Ping timeout: 121 seconds]
05:17 Derakon is now known as Derakon[AFK]
05:44 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
05:49 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
07:32 [R] [rstamer@genoce.org] has quit [Operation timed out]
07:38 mac is now known as macdjord|slep
09:25
<&Reiver>
Hexcells Plus: Fuck you, Question Mark
09:26
<&Reiver>
Oh, I get the idea. The tactic to avoid giving away too much info.
09:26
<&Reiver>
But half the gratification of clearing a hex is to be able to see the pattern form, so you can continue to puzzle the puzzle
09:27
<&Reiver>
A question mark robs you of this flow; you're a booby prize that takes the joy of clearing and makes it even less helpful than confirming a blue
09:27
<&Reiver>
And then you make /entire fucking walls/ of them
09:28
<&Reiver>
So now I'm back to playing Shitty Sudoku (And I know you're better than this, you had an entire level where you used almost nothing /but/ Sudoku Tactics to tease out which solitary hexes where what, that was brilliant)
09:32 * Reiver grumps. Could /probably/ figure this one out, but it is seriously trying his patience, and feels rather more like Debugging Code than Playing Puzzle Games at this point. Gimmie a hint? https://i.imgur.com/eCLHDzv.png
09:47
<~Vornicus>
on the down-right 5 line
09:48
<~Vornicus>
4 are marked already; the fifth must be one of the two atached to the 1 near the bottom
09:48
<~Vornicus>
So all the other cells in that diagonal are known clear
09:48
<&Reiver>
... oh, right, thanks
09:48
<&Reiver>
I got "So one of these two is a mine, but I dunno which"
09:48
<&Reiver>
I forgot "And thus none of the others either"
09:49
<&Reiver>
Hexcells Plus feels like it picked up in difficulty roughly where Hexcells 1 left off
09:56
<&Reiver>
phew, done
09:56
<&Reiver>
Levels like that /seriously/ feel more like debugging than puzzling, though >_>
09:58 [R] [rstamer@Nightstar-d7h8ki.org] has joined #code
09:58 mode/#code [+ao [R] [R]] by ChanServ
10:21
<&McMartin>
Reiver: Yes, very much so. Infinite backslides the difficulty a great deal on its designed ones
10:21
<&McMartin>
... I think
10:21
<&McMartin>
It's hard to tell because I'd just beaten Plus and was crackling with eldritch hexagonal power
10:24 Kindamoody[zZz] is now known as Kindamoody
10:31
<&Reiver>
Yeeess
10:31
<&Reiver>
I dunno
10:32
<&Reiver>
I still enjoy most of the levels
10:32
<&Reiver>
But the question marks are a pretty blatant "Go away and stop doing the bit you enjoy" thing
10:58
<&Reiver>
Other complaint: I really wish you could pause a puzzle instead of quitting it
10:58
<&Reiver>
Because I'm off to bed and I'm not finishing this sucker tonight ;_;
10:59
<@TheWatcher>
Slepwell
11:29 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has joined #code
13:41 celmin|sleep is now known as celmin|away
14:28
<@gnolam>
BWAHAHAHAHAHAHA
14:28
<@gnolam>
So. There is a bit of $HARDWARE that a company has been nagging us to implement in our software.
14:28
<@gnolam>
Unfortunately:
14:29
<@gnolam>
* We know that its performance is crap, and end users like to blame software for hardware flaws.
14:29
<@gnolam>
* Its drivers are literally the worst I have ever seen, so during the few moments it has worked /at all/, it hasn't really been /usable/, which makes testing pretty hard.
14:29
<@gnolam>
So it's been put off until such time as there's actual customer demand and we have spare time to allocate it.
14:30
<@gnolam>
The stars finally aligned for that to happen. Actual customer demand plus a new hire who had time to deal with the manufacturer's shit.
14:30
<@gnolam>
An email has arrived from said new poor sod.
14:30
<@gnolam>
He has experienced an anomaly with his dev unit.
14:31
<@gnolam>
It just exploded.
14:33
<~Vornicus>
That.... counts as an anomaly.
14:34
<@TheWatcher>
Yep, sounds like a proper anomaly that. Even SpaceX use that term for that event.
14:35
<@gnolam>
And I mean actually, literally exploded.
14:35
<@gnolam>
There was a video attachment of the still smoking debris. You can hear the voice of our sales manager somewhere off camera going "GOD DAMN!".
14:35
<@TheWatcher>
I have to ask, what does this unit actually /do/? >.<
14:42
<@gnolam>
Waste dev time? :P
14:43
<@TheWatcher>
Actually, no, what does it do when it doesn't undergot rapid unplanned disassembly? >.>
14:43
<@TheWatcher>
*undergo
15:21
< Emmy>
sounds like a printer
15:21
< Emmy>
also, are you allowed to share that video fragment?
16:29 Degi [Degi@Nightstar-fhsu08.dyn.telefonica.de] has joined #code
17:20
<@gnolam>
TheWatcher: measures stuff.
17:20
<@gnolam>
And no, not TNT equivalent.
17:44
<@Tamber>
Clearly, when they send a replacement dev-unit, the camera needs to be set up and recording *before* the first power-on.
19:13
<@gnolam>
https://twitter.com/GossiTheDog/status/1072549780998578177
19:49
<&McMartin>
Bomb calorimeter
20:35
<@Reiv>
those burn things to see how much energy was in them, right?
20:40
<&McMartin>
Correct
20:41
<&McMartin>
They are not in fact supposed to explode
20:48
<@Tamber>
It's a little less than optimal when they do that.
21:26 himi [sjjf@Nightstar-1drtbs.anu.edu.au] has joined #code
21:26 mode/#code [+o himi] by ChanServ
22:58 Vorntastic [uid293981@Nightstar-6br85t.irccloud.com] has joined #code
22:59 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
23:03 Degi [Degi@Nightstar-fhsu08.dyn.telefonica.de] has quit [[NS] Quit: Leaving]
23:26 Emmy [Emmy@Nightstar-9p7hb1.direct-adsl.nl] has quit [Ping timeout: 121 seconds]
--- Log closed Wed Dec 12 00:00:09 2018
code logs -> 2018 -> Tue, 11 Dec 2018< code.20181210.log - code.20181212.log >

[ Latest log file ]