191 reputation
3
bio website jbrownstudios.com
location Maui, HI
age
visits member for 3 years, 1 month
seen Jul 7 at 5:18

Jun
12
comment Continuing to code on large projects
Version control is trivially easy to use these days for huge benefits. If you can't remember every LOC you've ever changed on a project, you should be using version control for it. +1 here on test & document too.
Jun
12
comment How can my team avoid frequent errors after refactoring?
As others have commented. TDD. You probably already recognize you should have unit tests for as much of the code as possible. While writing unit tests just for the sake of it is a waste of resources, when you start refactoring any component you should start with extensive test writing before touching the core code.
May
8
comment Should I use branches for example uses of a github repo?
While I agree with the above, the other option would be to use a fork. I don't think it's a viable solution for you so I'm not proposing it as an answer. In no case would I use a branch, branches should really have a start (branch) and an end (eventual merge).
Apr
6
awarded  Supporter
Dec
10
revised “Mac” vs “OS X” vs “Mac OS X”
added 163 characters in body
Dec
10
awarded  Editor
Dec
10
revised “Mac” vs “OS X” vs “Mac OS X”
added 115 characters in body
Dec
10
comment “Mac” vs “OS X” vs “Mac OS X”
@Izkata is right. I've heard plenty of well informed folks express the shared assumption that OS X will continue past 10.9 to 10.10 and on.
Dec
10
comment “Mac” vs “OS X” vs “Mac OS X”
Agreed and while the official change from Mac OS X to OS X is recent, I'd also argue it's more appropriate for future proofing since it's unlikely Apple will switch back.
Dec
10
comment “Mac” vs “OS X” vs “Mac OS X”
Fair enough... you do need to consider you target demographic.
Dec
10
awarded  Teacher
Dec
10
answered “Mac” vs “OS X” vs “Mac OS X”