Reputation
1,346
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
7 12
Newest
 Yearling
Impact
~52k people reached

  • 0 posts edited
  • 0 helpful flags
  • 44 votes cast
Jun
28
awarded  Yearling
Mar
11
awarded  Nice Answer
Jun
28
awarded  Yearling
Jun
28
awarded  Yearling
Jun
25
answered Best practice for storing HTML coming from text fields to a database?
Jun
12
comment What features should a programming language have to say it has good reusability?
This is a very broad question, and the answers can vary greatly with programming paradigm. Reusability will be very different between OO, functional, and procedural languages.
May
3
accepted Feature branches, beta branches, and scrapped features
May
3
comment Feature branches, beta branches, and scrapped features
In case it was unclear, the "specifically" part of the question was the important part. When posting questions to SE sites, I try to post specific, answerable questions. This one just happened to include a request for more general data as well.
May
2
comment Feature branches, beta branches, and scrapped features
I guess feature toggles have a certain use-case - usually one where, as @DocBrown mentioned, the feature has a small entry point. Fortunately, my latest scrapped/indefinitely-delayed feature does have a (relatively) small entry point, and can be toggled rather easily by just changing a couple lines of code. More "integrated" features, I think, are less likely to be toggleable.
May
2
comment Feature branches, beta branches, and scrapped features
I'm not sure I entirely agree with the branching model presented in the link. Of course, it depends a lot on the release schedule - in my situation, we don't really have one, so I think it's best to be developing off of known, stable code. Or maybe that's where our workflow breaks down - the fact that we don't have a release schedule.
May
2
comment Feature branches, beta branches, and scrapped features
Feature toggles are definitely an interesting idea, and something I'll consider. I get the feeling it would be an architectural change, but it might be worth it.
May
2
comment Feature branches, beta branches, and scrapped features
Ooh! I think your link made an interesting point regarding merging. git has an option on merge (--no-ff) that allows you to treat the merge has a single changeset, rather than merging each changeset separately. That would make it a lot easier to backout/rollback/revert a feature. Now to research similar techniques for mercurial.
May
1
asked Feature branches, beta branches, and scrapped features
Mar
30
awarded  Necromancer
Mar
5
comment Is a merging strategy like Git Flow really an anti-pattern?
+1 for that first paragraph
Mar
5
comment Which of these OOP examples demonstrate proper OOP concepts?
Yeah, examples 1 & 3 being non-obvious is a real problem
Mar
5
answered How to manage github issues for (priority, etc)?
Jan
22
answered NodeJS as an avenue towards learning JavaScript
Dec
19
answered Do I have to learn html and javascript to create web applications?
Oct
24
answered Is there an established convention for separating Windows file names in a string?