meta user
network profile
| bio | website | darkspiredesign.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years, 7 months |
| seen | Mar 3 at 22:50 | |
| stats | profile views | 129 |
|
Mar 29 |
answered | What's a good light-weight source repository for local development? |
|
Mar 29 |
comment |
How do you normally layout a class's regions? My boss loves regions, looooves them. He also loves private inner classes and huge methods. Our code has one class with about a dozen regions dividing it up, 3 inner classes, and some methods so long they have a dozen top-level regions inside them, with sub-regions inside those. |
|
Mar 25 |
answered | Are Vim or Emacs practical for languages like .Net or Java? |
|
Mar 25 |
asked | Is Computer Science a “solvable” field? |
|
Mar 22 |
comment |
Why do game developers prefer Windows? Why Windows programmers prefer DirectX over OpenGL is probably a more interesting question historically. As the link to the Carmack interview below might indicate, DX used to be loathed. It would be interesting to know how it kept enough users for MS to support it until Xbox and modern rewrites made it more popular. Or maybe it was just always good enough so folks stuck with it. |
|
Mar 22 |
comment |
Why isn't Lisp more widespread? True, and as I understand it's a very powerful one, but it comes across to me as a side-feature of the language. It isn't like Java where you need to understand objects from day 1. Practical Common Lisp doesn't touch on CLOS until chapter 16. I may also just be biased towards static-typing, though I don't dislike dynamically-typed languages. |
|
Mar 22 |
answered | Why isn't Lisp more widespread? |
|
Mar 22 |
comment |
Why isn't Lisp more widespread? I think a lot of why Haskell is really catching on where Lisp hasn't is due to the research effort put into showing that Haskell code is "more correct." Lisp has a reputation of being very flexible but not necessarily for making objectively better programs. Haskell has a large body of research (especially towards concurrent programming) to show that a Haskell program is provably correct. I think that lowers the percieved risk factor and makes it a more viable choice. |
|
Mar 18 |
answered | Are “customizable” programming languages more widely used than not as “customizable” ones? |
|
Mar 18 |
answered | How to learn to translate real world problems to code? |
|
Mar 18 |
comment |
What's the best book for coding conventions? +1 One of the few subjective programming questions with an objectively correct answer. |
|
Mar 14 |
comment |
Advantage of Learning Lisp for a Python Programmer +1 just because it demonstrates an interesting reason to look at Lisp and not just at functional programming in general. |
|
Mar 11 |
comment |
When is it okay to ship a product with a known bug? @zzzzBov I recall an amusing lesson on bug hunting that involved a faulty "hello world". I forget the details but it probably involved text encoding or multi-threading or something. The point was that working code is only "bug free" in the context you tested it in: a change in the runtime context can introduce unforeseen bugs. |
|
Mar 11 |
comment |
What do you call one element in an enumeration? Hmmm... I know FP, but that doesn't sit right with me. An ADT can act as an enum, but I don't think it goes the other way. An enum is really a shorthand for a series of constants: you don't construct anything but they often have a directly mapped value underlying them. I don't find it wrong enough to warrant a -1 (it's an interesting thought at least) but I don't think it's very accurate. |
|
Mar 11 |
comment |
What do you call one element in an enumeration? +1 I call it an element, which I believe is the "official" term for them, at least in C#. |
|
Mar 11 |
comment |
Could a singleton type replace static methods and classes? As an aside: OOP offers many useful principles for extension beyond inheritance. As the Gang of Four said, "Favor object composition over class inheritance." One way to reuse a static method in a new class is wrap the call to that method in your new class. Thus you get the benefit of inherited behavior, and since you can't use static types polymorphically, that's all the benefit you'd get from inheritance anyway. |
|
Mar 11 |
comment |
Could a singleton type replace static methods and classes? @Berin Loritsch Oh no, I agree with that. I think I've used a singleton once and regretted it afterwards. I've also converted a large heap of static methods into a series of objects that were kind-of injected (not true DI) into the client objects and found that to be a significant improvement. |
|
Mar 11 |
comment |
Could a singleton type replace static methods and classes? @Berin Loritsch While I'd agree that being forced to put static methods on an object can at times seem like a hack, when the class itself is also static it mostly becomes a module or a namespace. Terminology aside, I don't think a static method on a static class is much different from a module full of a library methods in another language. And surely you'd want your free-standing functions grouped together somehow for ease of use and maintenance. |
|
Mar 11 |
comment |
How do you classify bug severity? @Thorbjørn When an error takes more time to put under tracking than to just fix right there when I noticed it, I tend to just fix it. (Mind you, we don't have a formal QA process, so no one else's job is to put bugs in the tracker. It's more of a "to do later" list for us than a work queue from someone else.) |
|
Mar 11 |
comment |
When is it okay to ship a product with a known bug? @DisgruntledGoat Not all bugs are equal: some are easy fixes, some are project destroying disasters. Obviously those should be fixed. Some are very rare bugs, hard to find, based on unusual circumstances, and usually difficult to fix without major rewriting. Sometimes those just have to stay in because fixing them offers too little value and the software needs to ship yesterday. Its all about cost/risk/benefit analysis. |
