191 reputation
17
bio website
location
age 26
visits member for 2 years, 2 months
seen yesterday

Software Engineer, Linux enthusiast, Anime enthusiast, Java/JSP/JSTL/Python/C programmer. Looking to break into the mobile scene in the very near future.


Sep
17
awarded  Popular Question
Feb
27
awarded  Scholar
Feb
27
accepted Is a merging strategy like Git Flow really an anti-pattern?
Feb
25
awarded  Caucus
Feb
25
awarded  Constituent
Feb
20
comment Is a merging strategy like Git Flow really an anti-pattern?
Doing a bit of reading up on it, and Martin Fowler's reference seems to indicate that feature branches done in a continuous integration flow can work out - if they're done in smaller bites than what most people would consider doing them for. So, in a sense, you're right - less than two weeks as a time-to-live on a feature branch seems suitable. I don't see, however, how feature branches themselves are the anti-pattern.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
@ErikReppen: I'd like to take everyone's minds away from version control and have a process that everyone can get used to. This way, we don't have to worry about things like if this is an anti-pattern or not.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
Nah, not using branches is a non-starter. The other primary issue would be that work can be done in two different places in the same code, so hopefully we can do something to alleviate that, too.
Feb
19
comment Is a merging strategy like Git Flow really an anti-pattern?
My experience with feature branches, or the way we've done them, is that there can be heartache with them if they're allowed to live for more than an iteration. A rule that states that all features must be merged into the iteration before release would be nice, to alleviate the heartache of merges - and boy, have we had some serious heartache behind those...
Feb
19
awarded  Student
Feb
19
comment how to prove TDD is best compared to code inspection
So have your company give it a try for a few cycles. The only way they'll be able to agree is if you have concrete evidence of it, and they'd have to have firsthand experience with it, too.
Feb
19
answered how to prove TDD is best compared to code inspection
Feb
19
asked Is a merging strategy like Git Flow really an anti-pattern?
Feb
17
comment How can I deal with a team member who dislikes making comments in code?
I'd argue that showing cleaner code/refactoring their code to be more readable demonstrates a greater change than putting gobs of comments into the code.
Feb
10
awarded  Critic
Dec
14
comment Review tests first
You shouldn't be afraid to write the tests first, as long as the scope of what it's doing is clear. It's also the case that you'd want to hit the code from more than just the happy path, too.
Dec
14
answered Review tests first
Dec
12
awarded  Teacher
Dec
12
answered What to do when a sprint is finished early?
May
26
awarded  Supporter