About Us
Codedgers Inc. is registered in Canada, Toronto by Vladimir Grytsan.
There are 3 keywords in company name:
- Code
- Edge
- Codger
At least now you partially know whom you are dealing with.
We are generally focused on the system programming for Windows OS and GNU/Linux OS, cryptographic programs development and compilers creation. For more details please see our services section.
Let us give you a couple of reasons why to choose us:
- Relatively low prices - see the detailed Pros and Cons in our blog.
- Highly qualified professionals - every Codedgers employee has to come through a serious two-stage interview.
- Best project management methods:
- zero-defect development (ZDD) - Tom DeMarco is totally right - most of the defects are already in the code before even the testing begins. The conclusion is therefore quite simple - one must truly devote as much attention as possible to the application architecture. Also we use informal code review keeping in mind the fact it is the only quality assurance practice that is able to catch out up to 80% of the bugs in code. And code review is able to find the bugs early. Remember: the earlier you find the bug in the development cycle, the less it costs to fix it!
- some selected elements of CMM
- Japanese have an astonishing kaizen practice. Some of its elements we also use in our day-to-day business processes. One example: each and every company must have some sort of the coding standard. If you wrote one and never updated it you probably do not follow the kaizen spirit. The standards must be continuously reviewed and improved. Again and again and again.
- Most of TDD adepts usually forget about acceptance testing. We do not. Our smoke phase is quite well developed - we use lots of Microsoft, Google and Apple quality assurance tools. Some of the examples are: AppVerifier and clang, Driver Verifier and KLEE and many-many others
- Software estimation is truly one of the biggest difficulties of the industry. Quite often the initial estimates are subject of about up to 4 times to change. Also it is close to impossible to estimate something when your development process is chaotic. As we have well-controlled and well-established development our estimates are more correct. We also use some advanced methods so the chances of the success are even higher.
- High code quality:
- We don't really think TDD is a panacea. However, being test infected makes sense :)
- We use some selected IEEE standards IEEE 830, IEEE 829, IEEE 1008 in our day to day practice.
- We use lots of metrics.
We have gathered many materials and articles during the years of our hard work as investigators and researchers, explorers of new computer science technologies. And we thought that our experience could be helpful to other developers in their work. We want to share our experience with the community, and we run the blog on the site for English speaking community.
WHAT'S NEW
- A couple of words about TDD
- Unit-test coding supposes to be one of the most significant methodological achievements of the industry, let’s say, for about last 15 years. The Internet is full of enthusiastic exclamations [1, ...
- February 21, 2010
- CodeExample plugin for Trac
- The Trac plugin for code examples colouring. It supports three types of examples - a simple, a correct one and an incorrect. Further details see at
- February 13, 2010
- Metrics - LoC
- This is going to be a small set of articles devoted to metrics. The first one is about LoC - Line of Code. I think that the first reaction on ...
- May 11, 2009
- Metric - Cyclomatic Complexity
- There is a simple and logic explanation: the more “if”, “while”, “for”, and etc. in code the higher the complexity of the code improvement, management, understandability and refactoring. Cyclomatic (here ...
- May 11, 2009
- SESE vs SEME
- SESE/SEME are terms of structural programming and were introduced at 80-s. Nothing new. However, experience shows that some programmers do not know about them till today. That’s why it makes ...
- April 08, 2009