Reputation
590
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
5 15
Impact
~13k people reached

Jul
5
comment Do you actually write 'clean code'?
Usually open source developers are required to submit clean code, unless he is the owner.
Jan
10
awarded  Popular Question
Jul
24
awarded  Notable Question
Jul
7
comment Should unit test be in separated repository?
also this one github.com/editorconfig/editorconfig-core-c with unit test github.com/editorconfig/editorconfig-core-test
May
19
awarded  Nice Question
Apr
14
awarded  Yearling
Sep
2
comment Choosing between Single or multiple projects in a git repository?
Each module need to have separate version numbers. And we use git-describe.
Aug
27
comment Why are pointers not recommended when coding with C++
Nearly abandoned in C#, you can still enable pointer by specifying unsafe keyword
May
17
awarded  Popular Question
May
14
answered Is this a Best Practice with Enum in C#
May
14
answered How to apologize when you have broken the nightly build
Apr
16
comment INI files or Registry or personal files?
Also, registry can have size limit. Files don't.
Apr
14
awarded  Yearling
Mar
12
awarded  Informed
Mar
4
revised Why do most issue tracking systems have only single status field?
there are typo mistakes
Mar
4
comment Why do most issue tracking systems have only single status field?
@Kilian an issue tracker on its own isn't the right tool to solve release management problems. Then how? Could you suggest some tools / workflow for this? I want to link up everything.
Mar
4
comment Why do most issue tracking systems have only single status field?
@JanHudec Yes, I am asking "making product for specific customers"
Mar
4
suggested approved edit on Why do most issue tracking systems have only single status field?
Mar
4
asked Why do most issue tracking systems have only single status field?
Feb
23
comment Is it possible for a good programmer to have never used version control?
ask the DBA to generate SQL scripts from the database and then he can put the scripts in source control.