[Tracing] Report #5
Hi folk,
I've been battling against splines extraction lately and my code is kind of messy (uncommitable). I've realized I was getting confused and decided to write a summary about what I'm doing and this would help me to get code faster. So, this "progress update post" is located at http://vinipsmaker.wordpress.com/2013/07/21/splines-extraction-on-kopf-lisch... .
Well, I think I need to apologize for don't give news about the project too, but my punishment is several hours under the dictatorship of the great lord Pomodoro http://en.wikipedia.org/wiki/Pomodoro_Technique. I hope to get something useful to show ya.
On Sun, 2013-07-21 at 17:02 -0300, Vinícius dos Santos Oliveira wrote:
Well, I think I need to apologize for don't give news about the project too, but my punishment is several hours under the dictatorship of the great lord Pomodoro. I hope to get something useful to show ya.
Don't worry if your code is messy. Commit it to your branch and push it, you can always delete the branch later and make a new one with cleaner code.
The advantage is that we can advise and help you with issues you might be having.
Martin,
2013/7/21 Martin Owens <doctormo@...400...>
Don't worry if your code is messy. Commit it to your branch and push it, you can always delete the branch later and make a new one with cleaner code.
The advantage is that we can advise and help you with issues you might be having.
I like to make commits that don't break. Following this rule, I also like to make small commits that change small parts of the code and are easy to track.
Anyway, my code is slowly progressing and soon I'll be able to post another update with some samples. Meanwhile, there is another post update without image-result samples: http://vinipsmaker.wordpress.com/2013/07/22/splines-extraction-on-kopf-lisch...
Nathan, you may want to skip the "Generalized Voronoi diagram generation" section, because it's the same of that PDF you received.
On Mon, 2013-07-22 at 18:58 -0300, Vinícius dos Santos Oliveira wrote:
I like to make commits that don't break. Following this rule, I also like to make small commits that change small parts of the code and are easy to track.
The policy I follow is:
Is the branch going to be released -> trunk==yes, dev-branch==no Breaks should be avoided in released branches but encouraged in dev-branches. It sounds odd to encourage broken code, but the more adventurous and the less shy, the less likely developers spin their wheels while their subconscious calculates risk vs reward and get stuck second-guessing the ability to hit a home run with every contact with the code.
Broken code can be fixed, uncommitted or reversed, non-existent code can't even be seen.
Small changes is a good plan, nice and smooth. Easier to see the progression and once merged all those get collapsed into a nice subtree.
Martin,
2013/7/22 Martin Owens <doctormo@...400...>
Is the branch going to be released -> trunk==yes, dev-branch==no Breaks should be avoided in released branches but encouraged in dev-branches. It sounds odd to encourage broken code, but the more adventurous and the less shy, the less likely developers spin their wheels while their subconscious calculates risk vs reward and get stuck second-guessing the ability to hit a home run with every contact with the code.
Okay, captain. =P
Small changes is a good plan, nice and smooth. Easier to see the
progression and once merged all those get collapsed into a nice subtree.
The "unreleased" code where I got stuck was related to B-Splines extraction, but I'm progressing again and good commits will follow.
After implement this code I'll start to implement B-Splines optimization and position fixing code.
Nice policy Martin. Never looked at it that way, I always tried to have working code in dev-branches and just as you say, I tend to get stuck second-guessing. The last year(s) continuous integration and workflow discussions in different forums might have focused a little bit too much on working code.
Regards
participants (3)
-
Christoffer Holmstedt -
Martin Owens -
Vinícius dos Santos Oliveira