Reputation
366
Top tag
Next privilege 500 Rep.
Access review queues
Badges
2 6
Newest
 Nice Answer
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 5 votes cast
May
10
awarded  Nice Answer
Apr
30
comment Commit at a logical checkpoint only, or also when you're at a stopping point?
You're only re-writing history on your personal branch, not the overall projects. Yes some still have issues with this approach, but it allows you to keep on moving forward. I find this approach to very natural as well. Just keeps everything happy. New comers will usually have the problem of having very large commits. Everything still needs to be atomic where each merge back into the development tree is one fix. Keeping this in mind, rewriting history (on your personal branch) is sometimes the only way to keep your own development moving forward.
Apr
30
comment Commit at a logical checkpoint only, or also when you're at a stopping point?
a lot of branches that should get cleaned up after they are merged into develop or master...
Apr
30
answered Commit at a logical checkpoint only, or also when you're at a stopping point?
Apr
3
awarded  Supporter
Feb
26
awarded  Constituent
Feb
26
awarded  Caucus
May
10
awarded  Yearling
Feb
12
comment How do Data Scientists Use Python?
It is apart of it. It all starts with parsing without parsing, you dont have anything to analyze
Feb
11
answered How do Data Scientists Use Python?
Dec
19
awarded  Nice Answer
May
17
awarded  Teacher
May
10
awarded  Autobiographer