this hopefully won't break all the things we've ever built
integration tests passed
I don't know if I should be happy or sad
On the release of AWS Edge Location in Vienna
schnitzel shops rejoice
def emoji = color == 'good' ? '♥' : '☕'
"always available sharepoint" sounds far worse than a zombie apocalypse
turns out if you type
/remind listslack will tell you how awful you are at planning anything and sticking to it : '(
after reverting back to NAM & STS coming back this fall
by then it will be fall at least, so I'll have other sources of happiness in my life
oh god
is there a "please chill" button on pagerduty?
i've named my work folder "y" just so I can call it
$HOME/y
could also call it "r" for$HOME/r
scott: i'm just surprised you'd go for $HOME over ~ all in the name of punning
integers are a language design bug
i feel bad watching this gitlab livestream. not bad enough to turn it off though.
i’m in the “I have no idea what i’m doing” part of the project.
TIL: every podcast i like is in us-east-1.
On the encore ticketing elasticsearch endpoint
i wonder if we could write to it.
ill stop.
yeah, fastlane is the slow part .
do we need a patent? how did passport work? is this real life?
janus_qe_dev definitely doesn’t have woo
i just got a call from a telemarketer and hit the 4 to acknowledge like pagerduty
when im running
pbpaste | base64 --decodei know im in a bad mood.
you broke janus’ golden rule: never link anyone to AWSAccount.js
This bans the Taiwanese IP that is scanning us.
i have a script setup to monitor that file and DDoS us if you didn’t alphabetize [humans.txt] correctly. just fyi
we should scale logout button size proportionally with the support queue length
can we mechanical turk log reviews?
don’t quote me on that
IBM blockchain commercials in world cup coverage. i hate everything
I don't laugh about passport.
jqis my back office
i use the escape key liberally
yesterday: gimme a P
today: gimme a C
tomorrow: gimme an I
yeah, apparently i killed all our prod UI servers just by opening my laptop
InternalError: too much recursioni didn’t know there was such a thing
blowing up catastrophically in prod considered harmful
somehow i’m going to blame jquery
we should also all move to SA and work at one desk
there is a slight eventual consistency issue
going to go do some deadlifts and think about it
it's friday, what could happen
it's either going to work the first time or be seriously borked
i'm pretty close on that dump -- if you're close too, feel free to keep going and we can hope we get the same answers 🙂
we could just stop using AWS and deploy everything on the proxy servers
to func or not to func
more like a zero uptime deploy
you might want to use a headless firefox selenium docker container?
it's always the notwork
I get loopy then I get ghetto
It will be magical. Probably not but it will be less terrible than nothing.
I blame eclipse
the ide, not the celestial event
(also, here are some more commas, because I haven’t used enough today: ,,,,,,,,,)
Bochi's Second Law of Naming stands. Given enough time, every concept is doomed to have at least two names referring to it
Tomorrow is a German holiday. The Brazilians will be out.
beware the staging
I think it’s a GCP issue. They need more cloud
</shover joke>
Campbell: Let me explain that....