<nuck>
You need to give locks a bj to come back or something
<ec>
what
<ec>
what
<ec>
what
<ec>
what
<incomprehensibly>
loksC
<nuck>
what what, what, what
<ec>
what
<ec>
goddamnit elliott
<ec>
*always*
<ec>
*always* squat URLs you stop using
<nuck>
Why are we singing Thrift Shop
<ec>
but still, what
<ec>
nuck: wat.
<purr>
beep.
<ec>
wat'ing is harder for me now, 'cuz sophie
<ec>
chick a while back got *really* frustrated at how often I typed ‘wat’ in everyday conversation instead of bothering to construct a real reply
<mkroman>
haha
<nuck>
ahaha
<ec>
so she went into my device and set up a text-replacement from ‘wat’ to something else
<ec>
which was dumb, so I changed it to ‘can't parse plz restate’, which is basically a literal translation of how I use ‘wat’
<ec>
so now every time I try to can't parse plz restate it can't parse plz restate's instead, which makes it hard to use can't parse plz restate to can't parse plz restate the bot with something somebody said that was very can't parse plz restate-y
<incomprehensibly>
ec: it's so so weird to me that
<incomprehensibly>
tumblr culture is this incredibly definite thing
<incomprehensibly>
and you were very active on tumblr like, 8 years ago or something
<incomprehensibly>
when that culture didn't exist whatsoever
<incomprehensibly>
and it was probably over on livejournal or something
<incomprehensibly>
in a similar form
<incomprehensibly>
can't parse plz restate are you talking about
<nuck>
ec: Solution: make the bot handle "can't parse plz restart"
<nuck>
Guys how to murder Ruby
<ec>
incomprehensibly: ugh i love you lol
<purr>
lol
<nuck>
I'm missing an entry in the inheritance chain
<ec>
ec: “so now every time I try to can't parse plz restate it can't parse plz restate's instead, which makes it hard to use can't parse plz restate to can't parse plz restate the bot with something somebody said that was very can't parse plz restate-y” wat.
<purr>
beep.
<nuck>
It just... stops
<ec>
nuck: codeplz
<ec>
I've been using fantasque as a coding font for a while now
<incomprehensibly>
In evolutionary biology, the term is also applied to males who are unwittingly investing parental effort in offspring that are not genetically their own.[1]
<ec>
cuckolding is making your husband watch while you fuck other individuals
<ec>
oh, what, really
<incomprehensibly>
lol i mean
<purr>
lol
<incomprehensibly>
that sense is derived from the initial one which is a husband being unwittingly cheated on
<incomprehensibly>
derived from cuckoo bird who lays its eggs in other birds' nests
<ec>
so hey unrelated to anything:
<ec>
I want to build a giant vim switchboard
<ec>
kinda thing
<ec>
well not literally vim, but, like,
<ec>
I want to try programming with a bunch of physical switches and knobs and controls
<ec>
partially as an aesthetic steampunk fun thing,
<incomprehensibly>
ec: modular synth style?
<ec>
yeah
<ec>
but partially because I'm not convinced that keyboard-exclusive programming is irl better, in the same way that touchscreens in cars turned out to be suuuuper dangerous and inefficient
<ec>
we all want a knob for the volume and another knob for the heat in our cars ... maybe it'd be equally ‘feel-better’ to program with a knob for font-size, and a physical switch for highlight-search-results, and a toggle for light/dark background
<ec>
oyou know?
<ec>
I already have a lot of the background for this started, because I've got a weirdly-specific HOTAS setup with about ten thousand billion little knobbly buttons on various HID devices
<incomprehensibly>
oh you just mean like
<incomprehensibly>
editor controls
<ec>
not *just* editors
<ec>
like a big red button for *rerun tests*
<incomprehensibly>
like wha ti want
<ec>
and a physical LED indicator of current test-status
<ec>
and, you know
<ec>
all that
<incomprehensibly>
is a kind of limited-on-purpose modular synth styl
<incomprehensibly>
e
<incomprehensibly>
thing for making games on an oscilloscope screen
<ec>
'kept maybe nuck, I'm not convinced he's a real perfson
<nuck>
lol
<purr>
lol
<nuck>
u drunk bro?
<nuck>
>perfson
<nuck>
I can assure you that I am not a perfson
<ec>
new keyboard.
<ec>
*insists*.
<ec>
that every forty-second word, precisely, *must* include an f.
<ec>
as far as I can tell, if the f happens to be absent when that period rolls around again, it finds the nearest s (including adjacent words, possibly.)
<ec>
I dunno dude this keyboard is fukt.
<ljharb>
what kind of keyboard is it
<nuck>
Get a better keyboard
<nuck>
I'm on a pretty boss CODE Keyboard
<ec>
I had a Das Keyboard for a while
<ec>
gave it to nexxy
<nuck>
Supposedly it's $120 though I'm not sure why anyone would pay that much for a keyboard
<ec>
ljharb: a Magic keyboard
<nuck>
I won this sucker at a hackathon event a while back
<ec>
I've been using the stupidly-rare mini-wired-Apple-keyboard for a long time, because I *hate* the form-factor/angle and lag of their bluetooth one, and I *hate* numpads
<ec>
fucking accountant illuminati bullshit
<ljharb>
btw "Magic" was the 42nd word and it didn't have an "F" in it
<ljharb>
i counted
<nuck>
ec: wat.
<purr>
beep.
<ec>
ljharb: yes, but no other word in the same string had an 's'
<ec>
I think maybe that escaped judgement thusly
<ec>
but wait what does that do to the count
<ljharb>
lol k
<purr>
lol
<nuck>
Might have also been the phase of the moon
<ec>
does it reset the count? or does the count start from the next 'f'? ugh
<ec>
Y UR GHOSTLY ALGORITHMS NO MAKE SENSE
<ec>
#spookyalgorithmics
<nuck>
GHOOOOOOSTLY ALGORITHMS
<ec>
nuck: wat.
<purr>
beep.
<ec>
-what
<purr>
<alexgordon> if you're a wizard then bake me a cake
<ec>
I would if you were still here >':
<nuck>
RIP
<ec>
-RIP
<ec>
GNU Terry Pratchett >':
<ec>
man I write some weird code /=
<ec>
I'm always on a knife-edge between pride and shame
<J-Wiggs>
Better than mine ;)
<nuck>
I can proudly say my code as of late has been incredibly boring
* ec
pats nuck
<ec>
v-dot-adult
<nuck>
Nah too late I'm already into horrifying SQL
<nuck>
No more boring stuff
<nuck>
woooo migrations
<ec>
I'm fucking around with Travis build-matricies
<ec>
for ... reasons unknown
<nuck>
Oh right we still need to abuse those on HB >_>
<ec>
hb?
<nuck>
We have two projects in one Repo, each with separate test suites
<nuck>
Hummingbird.me
<nuck>
Weebsite I work on
<ec>
I'm currently parallelizing the build-matrix
<nuck>
Isn't it by default
<nuck>
I'm pretty sure it is
<ec>
no like
<ec>
basically, splitting Mocha tests (and coverage-generation), bats tests (and integration tests), and `check` invocations (Rulebook conformance-testing) into three separate jobs
<nuck>
If you figure out how to do this, please tell me
<ec>
it's easy
<nuck>
That's basically what we need to do for HB — separating Ember from Rails tests
<ec>
as it is *all* of that effort happens in one go in my tightly-integrated test suite
<ec>
it's just envvars
<nuck>
oh right
<ec>
so you need a run-my-tests script that only runs the rails tests, or only runs the ember tests based on a var, lol
<purr>
lol
<ec>
not complicated
<nuck>
I always forget it's way less magical than it seems
<nuck>
hah
<ec>
it's only complicated for me because I've got this insanely complicated testing setup
<ec>
because I have to test 1. units, 2. integration of units at the API level, 3. integration at the *CLI* level, and then 4. the language specifications themselves
<ec>
el oh el writing a programming language el oh el
<nuck>
I swear someday when I'm 70
<ec>
and it takes three different toolchains to do that; *without* considering 1. debugger-support, 2. filesystem-watching / auto-running, or 3. test *coverage* reports
<nuck>
I'll find you
<ec>
all of which my system supports
<nuck>
And you'll still be working on paws
<ec>
guaranteed.
<nuck>
"Even now?" "Always."
<ec>
but yeah my *own* matrix of 1/2/3/4 and 1/2/3 there is like, then compounded by Travis's matrix,
<ec>
so it's a ... meta-matrix? I dunno but it's hellish
<ec>
I hate this busywork
<ec>
want to go back to writing code ;_;
<nuck>
three-dimensional build matrix?
<ec>
four-dimensional, maybe?
<nuck>
yeah you're fucked
<ec>
no wait it's higher-order than that, because it's a three-dimensional matrix but the third dimension *is* a matrix no wait I don't know math
<ec>
fuckit
<ec>
nah I'm almost done
<ec>
my current PROBLEM is that I'm doing all of this effort on top of a long-running refactor branch ...
<ec>
which was a huge mistake ...
<ec>
because the refactor branch is in an incomplete state where the entire *reactor* has been ripped out of the language, bye-bye, ded ... and so the test-suite is, like, indefinitely / intentionally failing in a particular way.
<ec>
so there's no way for me to know if the work I'm doing now, actually works, because the test suite won't succeed even once I ship this all up to Travis :P
<nuck>
I find that getting sidetracked on refactor branches is both inevitable and a disaster
<ec>
UGH SO TRUE
<ec>
I'm actually pretty goddamned git-disciplined in every other way
<ec>
but backing out of current work to start a new branch off of *an earlier branch* is just, beyond me, somehow
<ec>
despite all of my other successful coding-discipline habits, that one has eluded me for years
<ec>
I just can't stand to go back and look at the old state of the code, even if the benefits would be huge. I get too sad at the things I see missing. >':
<ec>
I imagine working *with* people would help with this.
<ec>
if, y'know, I, y'know, ever worked with people.
<ec>
instead of working completely alone.
<ec>
on a giant project.
<ec>
that nobody cares about.
<ec>
#omegaventure
<nuck>
I just end up building the stuff
<nuck>
On the refactor
<nuck>
And by the time I realize the mistake I've made it's hard to copy it over to the other branch
<ec>
yep yep ditto
<ec>
I care deeply about the git-history though, so I actually *do* always do that work
<ec>
I just usually do it after I've completed both tasks on top of a single branch
<nuck>
hah
<ec>
spending about an hour, on average, to track back through my granular commits, and carefully untangle them into two imaginary threads of work
<nuck>
I've stopped caring as much about the history after working with a team
<nuck>
I discovered the harsh reality: nobody actually looks at it
<ec>
yeah fuck that I will bash some *heads* in if people fuck up my beautiful git-log
<nuck>
I can make awesome commits, and I try to stay pretty granular
<nuck>
Occasionally I have to make a monolith because of intertangled messes
<ec>
yes, I'm OCD af; no, I don't think it's a bad thing
eligrey has quit [Quit: Leaving]
mkroman has left #elliottcable [#elliottcable]
<ec>
caution-yellow pelican at the bottom is my chew-lab gear, bottom right is the infosec safe, pick-bins are all cords and adapters and weird input devices
<ec>
lol the middle shelf that's all cluttered up is video-gaming gear. looks a little out-of-place :P
<purr>
lol
<ec>
love-affair with a label-maker
<nuck>
hah
<nuck>
I'm relatively OCD but I'm also recovering from packrat tendencies
<nuck>
They kind of cancel eachother out right now
<nuck>
Newer parts of my room, where I've cleaned out old shit, are clean and perfect
<nuck>
But older parts are a mess
<nuck>
In git repos, how big is too big?
<nuck>
Ours is about 100MB
<ec>
that's not that big
<ec>
> git clone git@github.com:WebKit/webkit.git
<nuck>
oh god
<nuck>
Their history is like 20 years though
<nuck>
They imported from SVN
<nuck>
And there's probably commits dating back to KHTML in there