Lawyers all dragging screenshots of excitebike into court and counting the wheels.
This dovetails nicely with my theory that Jesus hasn't come back yet because we invented the nailgun.
Yeah I'd argue that creativity starts after the idea, when you roll your sleeves up and see it through to completion. Ideas are easy. Everyone has them. Doing the work by using your skills and tools is the actual creative process. Everything else is mindless ideation.
Or to put it another way, imagine a high-level executive telling the art department to come up with something cool for the next product line. He fires an email off, waits for the result, maybe sends a couple notes back. When he unveils the product, he says "look how creative and artistic I am." Is he? I'd argue he isn't. He just had the idea. Other people executed that idea. The best you can say about him is he guided the process along, but nobody in the art department needs him to be there.
Bones is, as usual, thrilled to be there.
This is my favorite thing I've seen today.
Nah it's just flat-out racist. C'mon, people.
Imagine being the ruler of that city and letting him get "cured" instead of having him infodump / give daily reports about this.
"Captain's Log, supplemental."
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.
That would be pretty easy.
return "Why are you even trying to do it this way?\n$link_to_language_spec\nThis should be closed.;
Yeah, the goddamn wooden spoon. I remember being noisy in a crib and my mom storming into the room screaming and busting the spoon in half on the side of the crib. She'd already hit me with it so I knew exactly what it meant. I got spoons, open hand, and hairbrushes for most of my childhood. Hair pulling, pinching, and ear-twisting too if we were in a situation where she couldn't just haul off and hit me.
The funny thing is, she called me up about a decade ago and asked if I could remember anything about my childhood that was bad. And rather than list everything off, I told her about the time she broke the spoon on the crib. That's when I found out that it hadn't happened at all, and in fact if it had happened it was because the spoon was old and brittle and if she'd done anything at all it would have been a light tap on the side of the crib to get my attention, and now that she remembers it yeah that's exactly what happened. It just fell apart in her hands. We didn't talk for a few years because of that and other things.
After my daughter was born, she sent us a package that included two beautiful olivewood spoons from Israel. I use the fuckers when I'm making pasta. She calls or texts every once in a while warning me about protecting my daughter dark, evil things in the world. This usually happens when she sees a picture of my kid playing with a toy spider or a halloween skull. And I just chuckle and agree that there are dark, evil things in the world and I'm doing my damndest to protect her from them.