Skip Navigation

Posts
0
Comments
129
Joined
2 yr. ago

  • I can't stop laughing. Did you tell him, or did he just sit there grinding more and more pepper into your lap?

    My wife and I went to an Italian restaurant in Vegas a few years ago. The waiter asked if we wanted Parmesan, pulled the tiniest cube of cheese out and held it up like a magician, and then never broke eye contact while he grated it. It was unnerving.

  • A tuna sandwich?

  • Yep. Our friends flew one for a 4th of July party and one of the party guests took them aside and explained what it looked like to a casual observer.

  • "Captain's Log, supplemental."

  • I figured out what's missing. He needs a shiny H on his forehead.

  • Yeah we finally got a decent used record store in town and it's awesome. Before that, I had to dig through a lot of John Denver to find any ELO and Blue Oyster Cult

  • Vinyl records and playing cards (Western, Hanafuda, and Tarot decks.) The vinyl collection started when I got my parent's old record player and started hitting thrift stores for bargains.

    The card thing was sort of an accident; my wife (gf at the time) and I played a lot of Hwatu and cribbage and kept finding decks we liked.

  • I had zero plan beyond "live on my own, away from my parents, and try to sustain that." The churches I went to as a kid emphasized getting married as soon as you're old enough and having a ton of kids, so I did the opposite and was a feral stoner nerd/wook for a decade and a half. One day I was doing a hungover stumble from my apartment back to my car and saw a guy my own age playing with his small daughter at the playground. She'd fallen off the swing and he was hugging her until she stopped crying. I still can't fully describe the feeling I had there, but I shrugged it off immediately as "that ship sailed. I'll just dedicate myself to hobbies and non-serious relationships."

    Now I'm married, have a kid, and live in a house. Life's weird.

  • Larry Ellison from Oracle had a cameo too. It was gross.

  • Yep, world 5-3. I dimly remember being able to Luigi superjump onto the birds in 7-1 and short-circuit a bunch of that level.

  • That utter bastard made one side of Lazaretto play backwards: you have to put the needle in the center of the record and it spins out to the edge. First time I tried to listen to it I was very high and it was hell.

  • "I should make sure my software architecture mirrors our org's communication structure."

    Conway's law exists

    "Holy shit I am already so good at this."

  • Ok, hear me out. Her last name is Jones and she hates snakes....

  • I went to the live riff and they just looked defeated at the end of it. This part was pretty good though.

  • Yep! Good point.

  • I've been a dev for 20+ years and yeah, learning a new repo is hard. Here's some stuff I've learned:

    Before digging into the code:

    • get the thing running and get familiar with exercising it: test happy path, edge cases, and corner cases. We're not even looking at code yet; we're just getting a feel for how it behaves.
    • next up, see if there's existing documentation. That's not an end-all solution, but it's good to see what the people that wrote the thing say about it.

    Digging into the code:

    • grep is your very best friend. Pick a behavior or feature you want to try and search for it in the codebase. User-facing strings and log statements are a good place to start. If you're very lucky, you can trace it down to a line of code and search up and down from there. If you're unlucky, they'll take you to a localization package and you'll have to search based on that ID.
    • git blame is also your very best friend. Once you've got an idea where you're working, use the blame feature on github to tie commits to PRs. This will give you a good idea of what contributing to the PR looks like, and what changes you'll have to make for an acceptable PR.
    • unit tests are also a good method of stealth documentation. You can see what different areas of the code look like in isolation, what they require, and how they behave.
    • keep your own documentation file with your findings. The act of writing things down reinforces those things in your mind. They'll be easier to recall and work with.
    • if there's an official channel for questions / support, make use of it. Try to strike a balance here: you don't want to blow them up every five minutes, but you also don't want to churn on a thing for days if there's an easy answer. This is a good skill to develop in general: knowing when to ask for help, knowing when an answer will actually be helpful, and knowing when to dig for a few minutes first.

    There's no silver bullet. Just keep acquiring information until you're comfortable.