952 karma · joined December 19, 2019
> Because "obvious" refactors often introduce bugs (e.g. copy/paste errors), and if developers can't be bothered to write tests to catch them, they're going to screw over the other team members and users who will be forced to deal with their bugs in production.
In my opinion, useful tests should be able to survive a refactor. That is the only sane way I've ever done refactoring.
If I'm doing a large refactor on a project and there are no tests, or if the tests will not pass after the refactor, the first thing I do is write tests at a level that will pass both before and after refactoring.
Rewriting tests during refactoring doesn't protect from regression on my experience.
>Major League Baseball chose not to pause the season to allow its biggest stars to play in Tokyo, with the Americans made up of minor league players.
Without the ability to rewrite local history, you're either not commiting often (risky) or leaving long streams of poorly documented "work-in-progress" commits in the main project history.
>Perimeter of the cut square (4) matches the circumference of the circle (pi)
Calculus will show that the area of the fractal approaches the area of the circle. But it will not show that the perimeter of the fractal approaches the circumference of the circle. It remains 4 at every step in the iteration, so the limit is still 4.
I don't think it's that straightforward; proofs in papers are a mix between explanation in natural language and mechanical steps. Not every step of deduction can feasibly be written out. That's part of why computer aided proofs are not that popular in math.
I found a reference [0] where Wilson discusses slavery, but he's talking about slavery in ants. The only actual quotation [1] I've found anyone bring up in this discussion shows Wilson had views the exact opposite of what you imply.
[0] https://www.jstor.org/stable/2407145
[1] https://twitter.com/LSMitchell/status/1476447156118638594?s=...
My experience in other provinces with private insurance companies was much better.
The cyclist in this case averaged 37.5 km/h, which is really impressive over 24 hours. 5-10x slower would be 3.75-7.5 km/h, so somewhere between a very slow walk and a very, very slow jog.
Plus, the skateboards they are using are not going to be regular ones but purpose built and similar to downhill longboards.
You can't even organize your library aka "liked songs" by artist any more. Instead they introduced a separate (initially empty) Artists section, which isn't synchronized with your library of liked songs, or the albums page. It's insane.
I miss the UX of Napster/iTunes/winamp/rythmbox etc so much.
With credit card fraud it won't get to the point -- you dispute the charges before paying them back.
Brainfuck is an unrelated, separate programming language.
Even if they they did, once they change the history change, other developers working with the repo would be alerted of the remote branch changing out from under them next time they try to pull. And even if the change doesn't result in a conflict, and each of those other devs blindly accept the resulting merge, the original authors' commits will still be in the history resulting from the merge. So if those developers ever pushed anything, the original commits would be re-introduced.
Now, it could be abused if a single developer inherits a project that nobody else has checked out. But it's still a high risk strategy for the unscrupulous dev.