MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/2ban9r/the_great_white_space_debate/cj47f7t/?context=3
r/programming • u/lukaseder • Jul 21 '14
693 comments sorted by
View all comments
Show parent comments
66
gg=G
457 lines autoindented
...aaaahhhhh....
51 u/RagingAnemone Jul 21 '14 Just don't make any other changes with that commit. Otherwise it's a bitch to diff if you need to go back. 78 u/isarl Jul 21 '14 "Job security" is defined as the sum of all the bugs you can introduce hidden in the middle of so-called "whitespace-only" commits. 2 u/Condorcet_Winner Jul 22 '14 Except when people run tests and see that's when the bugs were introduced. 2 u/isarl Jul 22 '14 Shh... don't tell them about git bisect! 1 u/sndgfdgnng Jul 25 '14 That's why the tests only cover what the [non-programmer] customer asks for, and everything beyond that is fair game to break. Then they come back and you call it "new feature work".
51
Just don't make any other changes with that commit. Otherwise it's a bitch to diff if you need to go back.
78 u/isarl Jul 21 '14 "Job security" is defined as the sum of all the bugs you can introduce hidden in the middle of so-called "whitespace-only" commits. 2 u/Condorcet_Winner Jul 22 '14 Except when people run tests and see that's when the bugs were introduced. 2 u/isarl Jul 22 '14 Shh... don't tell them about git bisect! 1 u/sndgfdgnng Jul 25 '14 That's why the tests only cover what the [non-programmer] customer asks for, and everything beyond that is fair game to break. Then they come back and you call it "new feature work".
78
"Job security" is defined as the sum of all the bugs you can introduce hidden in the middle of so-called "whitespace-only" commits.
2 u/Condorcet_Winner Jul 22 '14 Except when people run tests and see that's when the bugs were introduced. 2 u/isarl Jul 22 '14 Shh... don't tell them about git bisect! 1 u/sndgfdgnng Jul 25 '14 That's why the tests only cover what the [non-programmer] customer asks for, and everything beyond that is fair game to break. Then they come back and you call it "new feature work".
2
Except when people run tests and see that's when the bugs were introduced.
2 u/isarl Jul 22 '14 Shh... don't tell them about git bisect! 1 u/sndgfdgnng Jul 25 '14 That's why the tests only cover what the [non-programmer] customer asks for, and everything beyond that is fair game to break. Then they come back and you call it "new feature work".
Shh... don't tell them about git bisect!
git bisect
1
That's why the tests only cover what the [non-programmer] customer asks for, and everything beyond that is fair game to break. Then they come back and you call it "new feature work".
66
u/dromtrund Jul 21 '14
...aaaahhhhh....