The author suggests one "symptom" of using git wrong is
>Have you ever did a code review, and gave feedback that was longer than doing the fix yourself, while you’re at it?
But this seems to neglect the utility of teaching people to do things correctly. Sure, I could always just fix junior programmers' mistakes, but it seems better to educate them in the first place.
Sending the fixes back down doesn't seem like it would have the same impact.
Depending on the kind of mistakes they've made, better again would be to provide a style/implementation guide for the code etc. so that instead of having to review code or have arguments break out over how something should be written, you can just point to a definitive guide beforehand, and avoid the troubles.
I say this, unfortunately, from experience. It has become common in our team for a new developer's first commit to be met with a blasting review, telling them everything they've done wrong, and most of it is capitalisation/whitespace etc. stuff.
Better yet, replace the style guide with a script (à la go fmt). You'll save everyone time and make the new person's experience a million times more pleasant!
Not if the new person disagrees or prefers a slightly different style. Reviews at least provide a chance of discussion and a possibility of change. Not everyone wants to work in an authoritarian environment of "do it this way or leave."
Gofmt, or rustfmt or whatever language fmt are really one of the best things that happened to modern development. Even if you don't agree with the style, which nobody does fully, it's much better than having discussions about style all the time and having to format the code manually. Formatting just happens when you save the file, so you can forget spaces and everything when writing and your code will look fine when you save it.
> Gofmt, or rustfmt or whatever language fmt are really one of the best things that happened to modern development.
Funny way to state that. There is this formatting tool `indent' for C and C++.
It was already well known and rather rarely used back in 2003. Code formatters
have not happened to "modern development" by any stretch.
I remember submitting an early preview F# bug directly to dev email which I got together with compiler crash message related to some obscure attribute handling situation. I remember being very surprised that I could do it, and more so when I got a response! That was the first time I realized there are people like me behind this faceless Microsoft machine.
Funny, wildly different times, I don't think github was even popular (existed?) back then.
This is great. Although part of me has a desire for the person to be outed so Trump can lose yet another horrendously baseless first amendment lawsuit.
GiveDirectly's previous work involves finding the poorest communities in the world and targeting the poorest members with direct cash transfers. I was turned on to them a few years ago by GiveWell (unrelated), which attempts to evaluate charities based on cost effectiveness and capacity for more funds.
In addition to the GiveWell reports, GiveDirectly also document and publish their work and research. It's exciting to see the impact that they are having (and how minimal the systemic abuse of the money is):
>Muscle cells require more energy to maintain than fat cells, so people with a higher muscle to fat ratio tend to have a higher BMR.
and
>Muscle tissue burns more calories than fat tissue, so increasing your muscle mass will help you lose weight.
It doesn't seem to address this discrepancy, though (that by exercising to build muscle mass one can affect their BMR and thus the lion's share of the calories burned).
The "MegaGame Society" is sort of the over-arching organizing group (they licensed Watch the Skies from the UK group, updated it significantly, and are recruiting more groups to run it locally).
They're definitely the folks to follow for information on games outside of the UK.
There's a guide (in development) at eyesonthesky.com[1] aimed at newcomers, who may be using poor telescopes in poor atmospheric and lighting conditions. I've been following it quite successfully from my back yard in Seattle. It focuses on the brightest galaxies and nebulae, interesting clusters, and binary stars.
>Have you ever did a code review, and gave feedback that was longer than doing the fix yourself, while you’re at it?
But this seems to neglect the utility of teaching people to do things correctly. Sure, I could always just fix junior programmers' mistakes, but it seems better to educate them in the first place.
Sending the fixes back down doesn't seem like it would have the same impact.