419 reputation
1410
bio website github.com/ferruccio
location Sharon, MA
age
visits member for 4 years, 2 months
seen Nov 14 at 12:13

Ferruccio Barletta

freelance software developer

ferruccio.barletta@gmail.com


Nov
15
comment Do you prefer conciseness or readability in your code?
You are confusing conciseness with terseness. Conciseness improves readability. Terseness detracts from it.
Oct
29
comment Can you learn functional programming in C?
Absolutely! The first step is to write a Lisp interpreter ;-)
Jul
12
comment Software Engineer VS “Harder” Jobs
the surgeon only needs to keep up with the research and the latest techniques.
Jul
1
comment What is the Best Way to Incentivize a Team of Developers?
Make your own casino! with blackjack! and hookers! on second thought, forget the blackjack.
Jun
2
comment The “blub paradox” and c++
Coroutines in C++: crystalclearsoftware.com/soc/coroutine
Apr
6
comment Why do programmers use or recommend Mac OS X?
It has a downside, though. I get really frustrated when I can't click by pushing down the touch-pad on my thinkpad.
Apr
5
comment Is it appropriate in a developer's job description to have “error free” as a key output?
Of course it's error free. The compiler says: 0 errors, 0 warnings. That completely fulfills the job requirements :-)
Feb
7
comment Uncomfortable terminology
Gender Benders!
Jan
30
comment Why is Lisp useful?
@Mark: I think you're describing Emacs.
Jan
1
comment Programmer aptitude test
"apptitude" is a really cool typo in this context :-)
Dec
22
comment Is there any reason to use C++ instead of C, Perl, Python, etc.?
Boost is the only reason I still use C++.
Dec
22
comment Why hasn't a faster, “better” language than C come out?
@jalf - I disagree. D's syntax is familiar enough so that a C or C++ programmer can pick it up easily and D can link to existing C libraries so that you don't lose the existing code base (C++ libraries are a whole other matter).
Oct
7
comment What parts of your coding standard contribute to quality code?
I agree in general but disagree on the "constants are capital" rule. I think this type of rule evolved from misapplying the C "preprocessor macros are all caps" rule (which makes sense, it's a dangerous construct and all caps makes it stand out). I don't think it adds any value to be able to tell whether a given symbol is constant or not and it conflicts with the other rules: "is this a private or public constant?" naming rules are a good thing, but they should take the language's capabilities into account and not just be dragged from one language to another whether they make sense or not.
Sep
27
comment What should every programmer know?
Not to mention assembly language.