Reputation
8,945
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
4 27 50
Newest
 Good Answer
Impact
~659k people reached

Nov
17
comment How clean should new code be?
@djechlin: Anything under 20LoC is rather easily refactored even when a lot of code is built atop of it.
Nov
16
awarded  Good Answer
Nov
16
revised How clean should new code be?
added 1 character in body
Nov
13
awarded  Nice Answer
Sep
15
comment Can you learn functional programming in C?
@nategoose: So you're telling me knowing about FP is good even if you do not write FP. I am not sure what to make of this, as this question wasn't even discussed here.
Sep
13
awarded  Yearling
Sep
11
comment Can you learn functional programming in C?
@nategoose: My original question (stemming from the comment discussion I linked to) was whether it makes sense to learn FP using C. However, I feared a "does it make sense to..." would be closed within minutes, so I rephrased it. But even if taken literally, I think it's clear that a "can you..." asks whether the language is a good enough fit to make it easy. As for pseudo-code: Would you pick an imperative or a functional type of pseudo code? (FWIW, having grown up on the wrong side of the Iron Curtain, pen and paper is how I "programmed" in the beginning. It's not very effective, though.)
Jun
30
answered Idiomaticy of macros in C++
Jun
30
awarded  Informed
Jun
25
comment In git, how to do versioning for a dozen libraries all worked at in parallel
@Patrick: And again no argument on the subject. HAND.
Jun
24
comment C++ is easy once you know PHP
"When you consider that PHP itself is written in C" ...then what? Most code is either written in C or compiled/interpreted by something written in C while running on something written in C. So? Does that mean that all code has some magical relationship with C? This is a bullshit argument. Oh, yeah, and it's true: writing your own sort algorithm in C++ today is stupid. But thinking that, coming from PHP, you could jump right into C++ and produce anything but horrible code is just as stupid. (FWIW, I have taught C++ to Java developers for several years. The code they produce at first is evil.)
Jun
23
comment In git, how to do versioning for a dozen libraries all worked at in parallel
P.S.: " I'd imagine you hardly want to switch languages." This is embedded stuff. :)
Jun
23
comment In git, how to do versioning for a dozen libraries all worked at in parallel
We are now evaluating putting the libraries into only two repositories. That's still more than one, but much less than "one for every project", and the libraries can very well be split into two groups. Thanks for your input!
Jun
23
comment In git, how to do versioning for a dozen libraries all worked at in parallel
@Patrick: I have described the steps in my question, and not only is the turnaround non-zero, it's also rather big. You, OTOH, haven't even bothered to provide an argument for why that seems neglectable to you.
Jun
23
awarded  Benefactor
Jun
23
comment In git, how to do versioning for a dozen libraries all worked at in parallel
I got a bit caught up in the last few days, so now my time for the bounty nearly ran out. I gave it to you because yours was closest to a helpful answer I got.
Jun
22
accepted In git, how to do versioning for a dozen libraries all worked at in parallel
Jun
22
comment In git, how to do versioning for a dozen libraries all worked at in parallel
"it counts as a process failure if you have to change all 4 together". Actually it wouldn't. In fact, this is exactly what we did using SVN.
Jun
19
comment In git, how to do versioning for a dozen libraries all worked at in parallel
No, backwards compatibility is ensured through release branches and is not our problem. The problem is that we sit on a currently rapidly changing codebase, which wet want to separate into libraries now, despite the fact that the interfaces are still in the phase where they change often. I know how to manage such beasts in SVN, but do not know how to do that in git without being drowned in administration.
Jun
19
comment In git, how to do versioning for a dozen libraries all worked at in parallel
I'm now on the train, having promised my oldest I'd take her to Jurassic World. Some other time?