@cwebber "thread"
@rocx Yep, classic. The "Higher Authority" gambit; chapter 7 of Roger Dawson's excellent "Secrets of Power Negotiating".
@rocx Yep! Negotiation is a set of strategies to be learned and practiced, with very nice rewards for doing so.
I know companies model support as a loss to be minimized, but it's especially frustrating in billing. @DigitalOcean has made it easier for me to move to a new host (and learn NisOS along the way) than contact support about a billing bug.
Reminder to job candidates not to give a current or expected salary number first... a dev I know just got himself a 50% raise at his new job.
@pushcx Today you'll be making a human-sized bookshelf... and your largest piece of lumber is 2' square particleboard... and you have no saw. Good luck, contestants!
You know those cooking contest shows where they give them random ingredients and they have to make a meal? I want one of those where handymen have to do home improvement projects with miscellaneous lumber and random tools.
Alternate hed: "Chicago Developer Salaries Likely to See 20-50% Rise Over Next Five Years" https://www.afr.com/real-estate/tech-behemoths-facebook-google-planning-big-chicago-office-expansions-20180607-h113h4
@cwebber Are you still in Chicago? Should I bring my drill over?
Bridge suffers from ludonarrative dissonance: everything in the game design points you to communicating hand contents with your partner; the rules forbid it.
@nightpool Yeah, and I'm actually one of the three people who've studied mnemonics, use method of loci, anki, etc. It's a useful set of skills outside of games, too.
@nightpool Then I guess our group has a really different set of preferences from the folks who design and play those games. Maybe the rule is an adaptation to "fix" a genre we'dotherwise enjoy significantly less.
@cwebber Might be an overloaded term here, too. When I say "mistake" in the post I only mean "error in judgement", not "made an illegal play". If you mean the latter, yeah, whoever recognizes announces it and we try to offset it or shrug and go "eh, that's the first couple plays of any game, now we know for next time".
@cwebber Yeah. Yes Take-backsies isn't something I've imposed, it's something we've grown to to be normal behavior for everyone over the years so everyone is comfortable saying "oops". I get where you're coming from, though.
New blog post on house rules for tabletop games, which is not-so-secretly a post about friendship and trust: https://push.cx/2018/house-rules
New Lobsters sister site for German-language computing, technology, and science: https://g33kz.de/
Going to be chewing on this one a long while, but this dichotomy of decouplers and contextualizers and a shift from former to latter as programming grows might help explain a lot of the cultural upheaval the last decade or so. https://quillette.com/2018/05/25/groups-groups-idw/
This sounds silly, but since it took me 20 years to internalize as a programming skill: use copy-and-paste all the time, or at least autocomplete. Do not retype things. Retyping is a constant source of preventable hassles and bugs, especially in the shell and dynlangs.
I'd like to see a Sliders reboot, but maybe that's nostalgia talking because the world feels like a mid-season-five filler episode.
@cwebber I had that feeling until I started regular prioritization + planning sessions, and explicitly thought through the consequences of what I was choosing not to do. Now I'm not haunted by vague fears of what I could be doing instead. Happy to talk in more detail if it'll help.
