Reputation
3,041
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
2 12 28
Impact
~102k people reached

Oct
6
answered How have you found, refined and maintained your coding style?
Oct
6
answered Maintaining a list of nodes with challenging requirements
Oct
6
comment Can you recommend a good commit message template / guidelines to enforce in the company?
+1 That is a nice way of dealing with it and you can easily grep for changes.
Oct
6
comment Can you recommend a good commit message template / guidelines to enforce in the company?
+1 for bug fixes but what about new features? Unless new features are all created in JIRA as well...
Oct
6
comment File naming convention for images stored in version control?
+1 nice trick indeed.
Oct
6
answered Multiple projects - similar platforms or as different as possible?
Oct
5
answered is it a reasonable practice to extend a class just to reuse a single function?
Oct
5
comment What's the best way to organize our unit tests
I would store it in a version controlled spread sheet in the test directory. If you have a lot of things you need to test, breaking it down into meta structures would be beneficial. Try thinking in terms of what general thing is being tested instead of what or how.
Oct
5
answered Where to start learning to use the Boost libraries?
Oct
4
answered How can I thoroughly evaluate a prospective employer?
Oct
4
comment How can I thoroughly evaluate a prospective employer?
+1 good and bad! That is very useful and probably will show some honesty
Oct
4
awarded  Commentator
Oct
4
comment Bringing my genius brain back
4 hours a day: either look for another job closer to home or ask to work from home for a couple of days a week.
Oct
4
answered What's the best way to organize our unit tests
Oct
3
comment Open Source Project and Revenue
"Les bons comptes font les bons amis" (lit. good accounting makes for good friends). If everyone is happy that only the lead developer gets money that is fine. There maybe a contract (written or verbal) that said money must be used for the project's costs. There may not be. There is nothing sinister if there is transparency.
Oct
3
revised Open Source Project and Revenue
Question edited which means that the answer was no longer valid.
Oct
3
answered Open Source Project and Revenue
Oct
3
comment White box testing with Google Test
Why is your tree not a class in and off itself which you can test via its public methods?
Oct
3
comment White box testing with Google Test
The reason why you should not test directly the internal of the class is that it makes your tests brittle. If you decide to refactor the code, you will need to re-write some tests and there will be no confidence that the new tests keep the old functionality. You should test the correctness of the private methods by testing the API of the class (aka its public methods). See all the links in my answer for more in depth explanations.
Sep
30
awarded  Suffrage