back
user profile
rbanffy
194,607karma·63,760submissions·March 12, 2008
about
Seasoned software developer, proficient in Python, Java. Less proficient in Ruby and Lisp. A bit rusty in C and C++. Learning Erlang very slowly. Also a computer collector and restorer, lover of 8-bit computers, mainframes and interesting Unix workstations.
email: username at that google mail thing
http://about.me/rbanffy
https://linkedin.com/in/ricardobanffy
[ my public key: https://keybase.io/rbanffy; my proof: https://keybase.io/rbanffy/sigs/HtF1uAf_RNpwIkNP1-YGWP_-3doWV6S5Cc1KywXeLYo ]
recent activity (63,760 total)
comment
I was only half joking about opening a pub next to it and calling it Papa Doc.
comment
We are having a problem with namespace collisions. I really thought this was related to the Raspberry Pi (which is a very minimalist computer). Earlier today, I saw something about a Rio terminal an…
comment
Kids who don’t learn history are doomed to repeat names we already used. Before you name something, google for it. Here in Dublin, Ireland, there’s a store that sells stuff for small kids and their pa…
comment
Generals say it’s logistics that win wars. The US record in winning wars is simply terrible.
comment
A hard boundary should only emit a warning. The same with nested loops and ifs.
comment
I knew a guy who naturally wrote code that baffled me all the time. Sometimes I wondered how the compiler managed to figure it out. Fun thing: he was like that all the time - it felt like his language…
comment
The easiest would probably be the smallest plausible set of actual server components in a 5u/tower case, but a custom eATX could go a little further with the cost cutting.
comment
Then I’d stop at claiming “best” is meaningless in a military context without defining what the mission is. If it is starting wars, I’d say it’s great. If it means achieving goals, then it’s kind of m…
comment
> "Functions should be 5 lines or less" This can’t really be a serious guideline unless you are writing APL, in which 5 lines can already be daunting to grasp. This guidance depends on th…
comment
I’m not sure the author knew what was happening. It seems like it worked like this and they left it at that.
comment
I really think a desktop Oxide machine, with the minimum meaningful hardware to demonstrate why it’s different from a generic amd64 server, would be an interesting idea. At this point I don’t know the…
comment
> I've seen 10k+ SLOC functions written in C, and 20k SLOC functions written in Fortran, That, spoken by Rutger Hauer.
comment
> It was a complete failure. That branch was abandoned and development continued off the spaghetti. It was considered too hard, most likely because the present state of the code already degenerated…
comment
> I have seen functions that were over 60,000 lines long That can't possibly be from a serious person.
comment
> unless compiler will save you by inlining the function into your code or architecture That's precisely what a compiler should do. Your code should be easy to read and understand. Let the com…
comment
It's much easier to optimise an easy to understand program than it is to debug a highly optimised one.
comment
> Fortunately we are humans, and professionally trained humans at that, and we can judge readability and comprehensibility of methods through better measures than whether it crosses a boundary of n…
comment
> The problem with a long function is not if it has N or N+1 lines of code, it's that length code with many branching conditions is prone to be untestable and introduce non trivial bugs. Once …