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
26
awarded  Enlightened
Jun
26
awarded  Nice Answer
Jun
26
revised Why is it good to split a program into multiple classes?
added 1 characters in body
Jun
26
answered Why is it good to split a program into multiple classes?
Jun
25
awarded  Good Answer
Jun
25
awarded  Enlightened
Jun
25
awarded  Nice Answer
Jun
25
comment Should you keep a copy of all the code you write?
In the case of a company accusation of IP theft, having a copy of the code is going to act as a big aggravating factor against you. Having the memory of it is not. That's the difference.
Jun
25
revised Should you keep a copy of all the code you write?
added 647 characters in body
Jun
25
comment Should you keep a copy of all the code you write?
Do you really want to risk a legal battle with a company over this? Their lawyers can spin this is a lot of ways that make this questionable (like a violation of your NDA or Non-compete clause in your employment contract)
Jun
25
answered Should you keep a copy of all the code you write?
Jun
20
awarded  Good Answer
Jun
19
awarded  Nice Answer
Jun
19
revised Why are so many languages passed by value?
added 2 characters in body
Jun
19
answered Why are so many languages passed by value?
Jun
19
answered Writing selenium tests, should I just get it done or get it right?
Jun
19
awarded  Nice Answer
Jun
19
comment Are too many assertions code smell?
Also in regards to "it suggests that the writer of the code didn't really know what he was doing [...] you do.". Future developers might not be as clear on what a particular method does. In this case, having pre and post conditions in the form of asserts can be invaluable in understanding a piece of code.
Jun
19
comment Are too many assertions code smell?
-1 Unit testing a class as a whole can be dangerous since you end up testing more than one thing per test. This makes really brittle tests. You should be testing one piece of behaviour at once, which often corresponds to testing just one method per test.
Jun
19
revised Are too many assertions code smell?
added 117 characters in body