4,229 reputation
927
bio website hierax.org
location Minneapolis, MN
age 36
visits member for 3 years, 8 months
seen 2 days ago

I love software development, and technology of all kinds. I have a boy and a girl and a beautiful wife, all of whom I adore. I practice Traditional Chinese Kung Fu, and hope that my kids will too. I write code and play boardgames in my spare time.

I currently work as a JEE engineer in Edina, MN.


Mar
22
suggested approved edit on Not getting paid for hours you've worked?
Mar
21
revised What is the objective of unit testing?
grammar, clarity
Mar
21
suggested approved edit on What is the objective of unit testing?
Mar
6
comment Drawbacks of code kata
@Antonio2011a: Good. I think you're right that we do learn best by tackling a real problem, or working on something that is useful or cool, but I do think that practice, even when boring, can be a good thing.
Mar
6
comment Drawbacks of code kata
I hear you, but I would argue that the name is less important than the intent, which is to help programmers improve. As to the actual question of whether there are any drawbacks to this type of practice, I can't see how the name is a drawback to the practice itself.
Mar
6
comment Drawbacks of code kata
I agree that the term 'kata' is imperfect, but don't lost sight of their point because of the name. Also, they're not all word problems; from Kata Two: "Implement a binary search routine (using the specification below) in the language and technique of your choice. Tomorrow, implement it again, using a totally different technique. Do the same the next day, until you have five totally unique implementations of a binary chop. (For example, one solution might be the traditional iterative approach, one might be recursive, one might use a functional style passing array slices around, and so on)."
Mar
6
comment Drawbacks of code kata
Code katas are not about rigid repetition; they're more about working to solve a problem, then working to improve your solution until you're satisfied. From Kata One: "The goal of this kata is to practice a looser style of experimental modelling. Look for as many different ways of handling the issues as possible. Consider the various tradeoffs of each. What techniques use best for exploring these models? For recording them? How can you validate a model is reasonable?"
Mar
6
comment Drawbacks of code kata
Read the link provided in the question; the idea is not mindless repetition as you seem to assume from the name.
Mar
6
comment Drawbacks of code kata
It's clear in your answer that you didn't read the link provided in the question.
Mar
6
comment Drawbacks of code kata
It's clear in your answer that you didn't read the link provided in the question.
Mar
6
comment Drawbacks of code kata
This answer appears to be getting a lot of support from the "I just want to do my job" crowd; it's completely useless in answering the question. Practice is what you make of it.
Mar
6
comment Drawbacks of code kata
While I agree that solving problems is a good way to improve as a programmer, learning to write elegant code can be a worthwhile pursuit as well. I wish that some of the original developers of code I currently maintain had put some time and effort into writing elegant code rather than copying and pasting to just get things to work.
Mar
5
comment how to find out if spelling mistakes in source code are a serious issue or not?
That makes sense @gnat; I've removed the extra paragraph from my answer.
Mar
5
revised how to find out if spelling mistakes in source code are a serious issue or not?
removed preamble about lack of previous answers
Mar
5
answered how to find out if spelling mistakes in source code are a serious issue or not?
Feb
29
comment Type mocking frameworks does not change coding practices from testability point?
If you're writing Java, Mockito supports mocking of concrete classes, not just interfaces.
Feb
24
revised Password hashing and support to your user
corrected spelling
Feb
24
suggested approved edit on Password hashing and support to your user
Feb
24
revised Is there any scenario where it's useful to keep mutable properties cached in domain objects for anything else than informational purposes?
rewrote title as a question, formatting, clarity
Feb
24
suggested approved edit on Is there any scenario where it's useful to keep mutable properties cached in domain objects for anything else than informational purposes?