175 reputation
19
bio website
location
age
visits member for 2 years, 9 months
seen Sep 9 at 10:43

Just another spaghetti chef.


Oct
18
awarded  Autobiographer
May
18
awarded  Commentator
May
18
comment Japanese Multiplication simulation - is a program actually capable of improving calculation speed?
Your algorithm is basically a way of simulating a mechanical computer on paper. If it was faster to do multiplication this way, processor architects would already lay out their circuits using it.
Mar
14
comment How do you know when to stop adding features?
So what do you do if you fail to meet your own deadline on a personal project?
Mar
14
comment How to address, “Is anyone even using this feature?” questions
You are doing it wrong if the only time you worry about useless features is when it lets you shirk on coding working patches. If you leave this decision until the feature blocks your code, there is a conflict of interest. You would be putting the cart before the horse. Features are determined at the design phase, before you start coding. If you feel like the original design is obsolete, stop coding, redesign, rewrite the spec, and then code without doubting if "anyone is still using this feature".
Feb
27
comment What should I do when I've already waited too long between commits?
@durron597 I disagree, I think this is different from #3. Regarding 149 lines, how much do you value a clean commit history? Is it worth spending half a day on? Anyway, it's not like the other methods won't require figuring out which line should be in which commit, so you will have to go through the 149 lines either way. The difference in time will be small.
Feb
27
answered What should I do when I've already waited too long between commits?
Feb
27
comment Able to read Code but struggling majorly to write it
Practice makes perfect.
Nov
24
awarded  Notable Question
Apr
4
awarded  Popular Question
Nov
5
comment Static DataTable or DataSet in a class - bad idea?
@asd Winforms in this case.
Nov
5
comment Static DataTable or DataSet in a class - bad idea?
Well, I gather that I'm not supposed to use statics although I don't quite understand why (besides your remarks). On the other hand, it makes more sense for me to use static in this case, as far as I can tell. So I guess I will just ignore the "no static fields" rule in this context unless someone feels like justifying why I shouldn't. Thanks for the link about locking!
Nov
5
awarded  Student
Nov
5
awarded  Scholar
Nov
5
accepted Static DataTable or DataSet in a class - bad idea?
Nov
5
comment Static DataTable or DataSet in a class - bad idea?
So if multithreading is something I don't wish to preclude, what alternatives do I have to a static field?
Nov
5
asked Static DataTable or DataSet in a class - bad idea?
Nov
1
awarded  Editor
Nov
1
comment Should comments say WHY the program is doing what it is doing? (opinion on a dictum by the inventor of Forth)
I agree mostly, except for "WHY is the only question worth answering outside of a few bizarre fringe scenarios". I don't think the bizarreness threshold is that high - sometimes a given block of code is just complicated and takes time to comprehend, and having a brief comment saying "this code basically does X" can help navigate code and mentally break it into components when you revisit it after forgetting everything (or when other people visit it the first time). Yes, you can refactor and make a nicely named method, but sometimes this ends up adding complexity to the code needlessly.
Nov
1
revised Should comments say WHY the program is doing what it is doing? (opinion on a dictum by the inventor of Forth)
Question title was broader than the actual question