229 reputation
27
bio website gavenkoa.users.sourceforge.ne…
location Dnipropetrovs'k, Ukraine
age 30
visits member for 3 years, 10 months
seen Apr 22 at 23:09

Software developer and instructor. Mathematician by education.

Daily use Emacs and Firefox under Debian.


Feb
12
awarded  Informed
Jan
7
revised How do you version your files (Version Numbers)
added 121 characters in body
Oct
2
comment Naming schema for config files that generated and not for human editing?
Thanks for suggestion. I forget about possibility to group such files in separate directory. So can avoid name mangling in file names...
Sep
30
asked Naming schema for config files that generated and not for human editing?
Sep
12
awarded  Necromancer
Sep
12
awarded  Yearling
Sep
10
answered What's stopping Oracle from supporting identity (auto-numeric) columns?
Feb
25
awarded  Caucus
Feb
7
awarded  Autobiographer
Oct
13
revised How fast should a version number increment?
added 420 characters in body
Oct
13
comment How fast should a version number increment?
@Ed. I specially state: versioning schema for developer, does not for marketing. I use this rules for developer versioning so restrict unnecessery MAJOR + 1. Usually managers or sellers can decide increment MAJOR and this can break **if (vmajor != 3) error("Incompatable version detected!");
Oct
11
revised How fast should a version number increment?
added 285 characters in body
Oct
11
answered How do you version your files (Version Numbers)
Oct
11
answered How fast should a version number increment?
Aug
18
answered Advantages of a left to right language syntax
Jul
20
awarded  Teacher
Jul
19
answered Good naming convention for named branches in {DVCS} of your choice
Jul
19
awarded  Supporter
Jul
10
comment Where should the description about branches in a VCS be stored?
Interesting approach. But seems my boss can not use this techniques for reading stored info. It can read only email/text files.
Jul
10
comment Where should the description about branches in a VCS be stored?
Descriptive names are good for feature branches. But fail if branches used for custom product versions or different product versions.