3,233 karma · joined February 1, 2013
I remember sitting on the floor of our living room programming this in character by character on that TI keyboard. It's the first BASIC program I ever wrote. Everything before that was js and html.
It's the latter action that's being addressed here.
- Pull up the commit history for the file to see what other files were modified along with it the last few times. This will give you dependencies and linkages.
- Make your change and then ask your ide/command line to find all typing/lint errors in your project which will help you find other dependencies you may have missed.
- If you get stuck, reach out to the authors or reviewers of previous PRs. (Hint: you may want to include them as reviewers. They'll give good feedback and you'll engender good will by keeping them in the loop when you touch their corner of the codebase)
- Write a few solid unit tests. Maybe even clean up the testing code a little bit while you're there.
- Write a concise but informative description of your changes in your PR. If you made two or more logical changes, split your PR and stack them. Your teammates will appreciate the shorter PRs and you will get feedback more quickly.
- Land the PR in a timely manner and keep an eye on it until it hits prod.
- Once in prod, test it yourself and keep an eye on the logs for a day or three.
- Bonus: put all changes behind feature flags to do slow rollouts and so you can quickly revert without waiting for a deploy. Make a task to remind yourself to remove the dead code behind the flag in month or so when you're pretty sure it's stable.
Some of the best data for branching ratios comes from e+e- (electon-positron) colliders such as LEP (literally, the Large Electron-Positron collider). In these colliders, we can fine-tune the energy to produce massive amounts of particles we care about. From that, we can see how they decay. Mostly, Upsilons decay into massive sprays of hadrons and leptons (called jets in particle physics). These can come from decaying Tau particles (the much much heavier cousins of muons and electons) or from quarks/hadrons decaying over and over and over again into things like Kaons, pions, muons, electrons, photons, and other lightish particles. In the relatively clean environment of a e+e- collider, we can reconstruct these jets and determine which may have come from Upsilons. Combining this with a whole bunch of other measurements (and some theory) lets us determine the branching ratio (how often a particle decays into certain things).
The point is, we cannot tell which pair of electrons/muons come from the decay of a specific particle, but we can tell how many extra occurred beyond what we would expect from all other known processes.
GraphQL is a little older than that. It was initially developed at Facebook in 2012. It says as much on the graphQL website right on the main page: https://graphql.org
It's a story of two Neils dealing with imposter syndrome. Every time I start feeling like I'm just the guy who goes where others point and I didn't actually accomplish anything, I go back and read this. To every new engineer I've worked with who has struggled with self-doubt, I have sent this. I cannot overstate how calming and centering this post has been to me.
What could change to make it more likely that the process would be followed? Could we put signs all around places with prion research? Could we implement a buddy system whenever we work with prions? Do metal gloves need to be hung in visible place throughout the lab? Do we keep containers of bleach accessible for when someone pricks their finger? Do we have enough of them and are they visible enough?
1) This is due to power consumption while idle, not overall power consumption. Nor is it a new regulation. [1]
2) This isn't just California. These same regulations apply in Colorado, Hawaii, Washington, Oregon, and Vermont.
[1] https://www.reuters.com/article/us-california-energy-compute...
I did use it while ignoring the game part for a bit. It was still useful, but I did just end up forgetting it later.
> Post-modern?!
> It's a joke. If neovim is the modern vim, then helix is post-modern.
Thanks for the info!
Mail issues can also be aggrevated by local policies. I know a former regional postmaster from Wisconsin. I've since learned that during the Scott Walker years, they changed the service in WI so that all mail in the entire state is sorted in Milwaukee. So if I'm up in NW WI and I send a letter to someone a town over, the mail needs to be driven all the way across the state to Milwaukee, sorted there, and then driven all the way back. He says it's making what use to be a 1-day delivery into 3+.
In reality, FB is just being highly transparent with issues and I should applaud them, but that's a lot of yellow and red.
I understand what you mean about the day job thing. I got about 60% of the way through Shenzhen before walking away. Fortunately, I'm not a chip-designer, so hopefully that horizon is farther away with Factorio.