8,973 reputation
13452
bio website oleksiderkatch.blogspot.com
location Waterloo, Canada
age 24
visits member for 2 years, 10 months
seen Dec 12 at 14:55

Aspiring software engineer for the healthcare industry. Currently studying Computer Science at The University Of Waterloo.

profile for Oleksi on Stack Exchange, a network of free, community-driven Q&A sites


Jun
1
revised Is dependency injection by hand a better alternative to composition and polymorphism?
deleted 1 characters in body
Jun
1
answered Are More Comments Better in High-Turnover Environments?
May
31
comment Are There Metrics For Cohesion And Coupling?
This might help with that: aivosto.com/project/help/pm-oo-cohesion.html
May
31
comment Are There Metrics For Cohesion And Coupling?
@OnorioCatenacci No problem. :)
May
31
answered Are There Metrics For Cohesion And Coupling?
May
30
comment User defined type for healthcare / Medical Records variable name prefixes?
@Rig you don't need Hungarian notation. In fact, it is widely consider bad practice to use it today. It became popular in the days when you couldn't just mouse over a variable in your IDE to get all it's type information. Today, IDEs make Hungarian notation obsolete.
May
30
revised Using static in PHP
added 4 characters in body
May
30
comment User defined type for healthcare / Medical Records variable name prefixes?
The same point applies to abbreviating parts of variables. You are reducing the clarity for a lot of other developers. I would still prefer a 20+ character variable to an unclear, non-standard abbreviated variable.
May
30
comment User defined type for healthcare / Medical Records variable name prefixes?
@Ryathal abbrevations are only ok when most people can deduce what the full word is supposed to be. If an abbreviation is too terse (or worse yet, in Latin) you risk other developers not knowing the meaning of your identifiers.
May
30
answered User defined type for healthcare / Medical Records variable name prefixes?
May
29
awarded  Guru
May
29
awarded  Enlightened
May
29
answered In need of a divide and conquer approach for re-writing small open-source utilities
May
29
comment Stuck due to “knowing too much”
@MSalters It's tricky, which is one of the reasons I didn't recommend this in my answer. However if you wanted to choose this route, I would partition the input space into several disjoint and complete classes: (Cache miss, cache hit), (Cache empty, cache non-empty), etc. This shouldn't generate a lot of tests. Once this is in place, then write your code to pass those basic tests. Next, I would use some code coverage tool to see what parts of the code aren't covered by the current test set, and add tests as required.
May
29
awarded  Good Answer
May
29
awarded  Nice Answer
May
28
comment Stuck due to “knowing too much”
@MSalters I think Graham is referring to TDD, where you write a set of tests before the code. Then you write the simplest code that makes those tests pass. Then you refactor. Following this technique may prevent you from over-thinking your initial development since your goal is to make the test pass, not make perfect code.
May
28
revised Stuck due to “knowing too much”
added 9 characters in body
May
28
answered Stuck due to “knowing too much”
May
28
comment Why C++ to write a compiler?
@delnan There's probably plenty more that I could've done to make it readable. I guess I'll know for next time. :)