9,704 reputation
12142
bio website en.wikipedia.org/wiki/…
location United States
age 70
visits member for 4 years, 7 months
seen 17 hours ago

BS Mechanical Engr.
PhD CS(AI)
CS Prof (4yr)
Numerous consulting jobs.
15 yr at http://www.pharsight.com
Published book on CS & several articles
4 kids, 2 grand
Pilot(student)

P.S. The picture is a Beta-prime distribution. It shows the program speedup factors you can get if you see a problem twice in 2, 3, 4, and 5 samples.


Apr
3
comment Trying to “combine” similar objects without doing a bazillion comparisons
Not being primarily a database person, I'm trying to understand the question. In something vaguely similar that I did ages ago, there was one database that described the structure of another database. Then, since the first one changed at low frequency, there was benefit in precompiling it.
Mar
24
comment Reason for (post/pre) increment operator in Java or C#
@Doval: I even built a language I called D, like C but with OO and parallelism features. It went nowhere (mercifully) and has no relation to the D you are talking about. I drive people crazy in C?? by always writing break; case ... ;-)
Mar
24
revised Reason for (post/pre) increment operator in Java or C#
added 25 characters in body
Mar
24
answered Reason for (post/pre) increment operator in Java or C#
Mar
16
revised Which statement performs best?
added 8 characters in body
Mar
16
answered Which statement performs best?
Feb
27
revised Does Refactoring towards Looser Coupling, Smaller Functions, and Separate Classes affect System Performance? (and Should I Care)
added 218 characters in body
Feb
26
revised Does Refactoring towards Looser Coupling, Smaller Functions, and Separate Classes affect System Performance? (and Should I Care)
edited body
Feb
26
answered Does Refactoring towards Looser Coupling, Smaller Functions, and Separate Classes affect System Performance? (and Should I Care)
Feb
12
answered Is debugging a waste of time?
Jan
30
comment How do I traverse a tree without using recursion?
Come on @Mat, that's kid stuff. You may disagree, like if you are afraid of bombing out on a tree that's too deep, that's a reasonable concern. You can just say so.
Jan
30
comment How to convey your approach is faster than the built-in, alternative approaches?
+ @Joan: I find if you say "It used to take a minute, and now it takes less than a second", that gets the idea across.
Jan
22
comment How has an increase in the complexity of systems affected successive generations of programmers?
@david.pfx: Agreed. Macros could use a debugger of their own :)
Jan
21
comment How has an increase in the complexity of systems affected successive generations of programmers?
@david.pfx: When I worked in Lisp, macros were perfect for that. In C-like languages, I would first see if I could do it just using C macros (I hated that the Java-folks deprecated those), otherwise I write recursive-descent parsers. I've done so many now, it's almost sleepwalking.
Jan
17
comment How has an increase in the complexity of systems affected successive generations of programmers?
@PeterMortensen: I just emailed it to you (17mb). Remember, it's 20 years old.
Jan
16
comment How has an increase in the complexity of systems affected successive generations of programmers?
@MDMoore313: I scanned it, and could send you that. It's 17mb.
Jan
15
comment How has an increase in the complexity of systems affected successive generations of programmers?
@Jason: I plead ignorance of nimrod. What I look for in a DSL is if you write domain-specific programs in it, and a specific request or requirement comes along that's simple enough that you can either do it or not, then if you completely implement it, then you diff the source files before and after the implementation, the number of differences is small. (puff!)
Jan
15
awarded  Good Answer
Jan
15
awarded  Nice Answer
Jan
14
comment How has an increase in the complexity of systems affected successive generations of programmers?
@Izkata and Peter: Yeah, I'm that oddball. FWIW, I put up a couple (extremely amateur) videos, in hopes of making it easier to understand. Random Pausing. Differential Execution. Cheers.