code logs -> 2021 -> Fri, 23 Jul 2021< code.20210722.log - code.20210724.log >
--- Log opened Fri Jul 23 00:00:52 2021
02:01 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has quit [Connection closed]
02:34 Degi [Degi@Nightstar-6bfmnj.pool.telefonica.de] has quit [Operation timed out]
02:41 Degi [Degi@Nightstar-dboejl.pool.telefonica.de] has joined #code
05:12 abudhabi- [abudhabi@Nightstar-6jffjl.adsl.tpnet.pl] has joined #code
05:13 abudhabi [abudhabi@Nightstar-eofdma.adsl.tpnet.pl] has quit [Ping timeout: 121 seconds]
06:37 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has joined #code
06:37 mode/#code [+qo Vorntastic Vorntastic] by ChanServ
07:54
<@sshine>
TIL: Don't name something after a single customer.
07:54
<@sshine>
I've always thought it was aesthetically unpleasing, but at this point, it is downright inconvenient.
07:58
<&McMartin>
That sounds nearly as unwise as naming it after yourself
08:01
<@sshine>
Malkovich/Malkovich.c
08:02
<@sshine>
"We'll give this one customer early access and name their access point something obscure. Oh, wait, we need to give others early access, too!" -- the funny thing, six months ago, one of my first tasks was to merge an old early-access customer's private instance of an application into the main one, and it was quite tedious. now I'm being asked to make special cases again, and name them quite short-sightedly.
08:03
<@sshine>
:-D
08:11
<&McMartin>
This seems like the reverse of the Insufficiently Fluffy Kitten Error, early in my career
08:52 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection closed]
11:48 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
13:54
<&ToxicFrog>
Insufficiently Fluffy Kitten?
14:31 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
14:31 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer]
14:59 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
14:59 catalyst_ [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection reset by peer]
15:00 Vornicus [Vorn@ServerAdministrator.Nightstar.Net] has joined #code
15:00 mode/#code [+qo Vornicus Vornicus] by ChanServ
15:00 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Connection closed]
15:00 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has joined #code
15:01 catalyst_ [catalyst@Nightstar-2h5n93.dab.02.net] has joined #code
15:04 catalyst [catalyst@Nightstar-ejd4sd.cable.virginm.net] has quit [Ping timeout: 121 seconds]
17:17 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has joined #code
17:23 catalyst_ [catalyst@Nightstar-2h5n93.dab.02.net] has quit [Ping timeout: 121 seconds]
17:26 catalyst [catalyst@Nightstar-2h5n93.dab.02.net] has joined #code
17:27 Vorntastic [uid293981@Nightstar-h2b233.irccloud.com] has quit [[NS] Quit: Connection closed for inactivity]
17:33 macdjord [macdjord@Nightstar-q03cd9.dsl.bell.ca] has quit [[NS] Quit: Deep inside, every housecat believes themself to be just a temporarily embarrassed tiger.]
17:34 catalyst_ [catalyst@Nightstar-lq7qg8.dab.02.net] has joined #code
17:36 catalyst [catalyst@Nightstar-2h5n93.dab.02.net] has quit [Connection reset by peer]
17:38 catalyst_ [catalyst@Nightstar-lq7qg8.dab.02.net] has quit [Ping timeout: 121 seconds]
17:55
< Yossarian>
07:03:44 <&ToxicFrog> Insufficiently Fluffy Kitten? --> ya, what's that?
18:28
< abudhabi_>
A new code? https://http.cat/
19:02
<&McMartin>
Many years ago I worked for a company that provided business software to much larger companies, many of which had individual needs.
19:03
<&McMartin>
So we needed logs for what we were doing and we also wanted logs to make sure that we weren't doing things in the wrong place and definitely did not want customers seeing logs that revealed process information about other customers, etc.
19:04
<&McMartin>
And so I instructed the team that we should have our log values regarding customer specific behavior be extremely generic or opaque, like an insufficiently fluffy kitten error rather than not finding a certain company name in the config file or what have you
19:05
<&McMartin>
Except then one of us actually put *in* a *literal* insufficiently fluffy kitten error and of course every customer noticed this in the logs *immediately* and started calling support asking about kitten fluffiness
19:07
<&McMartin>
Being older and more cynical: I am now assuming that those clients assumed that an obviously weird kitten-related error was a license enforcement trap designed to get users to tell on themselves, and that they were asking about the kittens with their license agreements open and ready in the next window.
19:10
<@gnolam>
With the paper-thin barrier between me and sales: I think you are correct.
19:15
< Emmy>
418 still the best http response
20:26 Kindamoody[zZz] is now known as Kindamoody
23:03 Kindamoody is now known as Kindamoody[zZz]
23:48 Emmy [Emmy@Nightstar-l49opt.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Sat Jul 24 00:00:52 2021
code logs -> 2021 -> Fri, 23 Jul 2021< code.20210722.log - code.20210724.log >

[ Latest log file ]