361 reputation
15
bio website
location Rio de Janeiro, Brazil
age 39
visits member for 3 years, 9 months
seen 31 mins ago

I'm a Delphi developer mainly, with 12+ years of experience, having done things ranging from ActiveX controls, maintaing and evolving systems to creating an (private) web service acting as business layer in Delphi.net.

I have some experience with C#/Vb.net too.


Oct
10
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
So the discussion is lost forever, so moving it is equivalent to lose it. And this discussion is MUCH better than the answer.
Oct
10
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
@WorldEngineer, the sad thing is that chat is not tied with the question and, by the last time I looked at, content there is transient...
Jun
13
comment Should I use parentheses in logical statements even where not necessary?
@Kaz: Because of experience. Parenthesis is more reliable than using the precedence and (using well) transmit my intention much better. And yet, many times I decompose long boolean sentences on boolean variables (where available, when not I do the most common idiom to emulate them) much before introduce local refactoring became common on IDEs.
Jun
13
comment Should I use parentheses in logical statements even where not necessary?
@Kaz: you know that exists miles of distance between "should not have" and "does not have".
Jun
12
comment Should I use parentheses in logical statements even where not necessary?
@Kaz - "should not have undocumented ambiguities".... You can guarantee that? Or that an breaking change on parsing/syntax checking/code generation will not happen? Of course not. So LarsH and CapeCodGunny are right: be clear on the intentions when writing conditional statements.
Apr
24
comment What is the best way to prove that in-code documentation is greater than extensive external documentation?
@GlenH7, I think people missed the point: his boss' is trying to trace the code changes. What SAP process showed him is a way to achieve that traceability
Apr
3
comment Why didn't == operator string value comparison make it to Java?
See last sentence (which I separated in a proper paragraph in a edit).
Mar
13
comment How do I handle having so many SQL queries?
Sincerely, this one is better than the accepted answer... +1
Mar
5
comment How do you know you're writing good code?
@mplungjan Wow, REXX!!! It's (or was) a really cool system language...
Feb
27
comment My customer wants me to record a video of how I develop his software product
Nothing works better than the good old hurt in the human's most sensible organ - the wallet..... ;-)
Jan
21
comment My boss has a bad case of “Not Invented Here”
I've made in the past, and sometimes I had to reduce batches' size to get faster. Is a tuning thing.
Jan
21
comment My boss has a bad case of “Not Invented Here”
I/O normally cost a lot more than network. Even using bulk copy, there's things that get logged. A lot of I/O at the same time will make cpu get low use and hang the server until the I/O is done. Of course, this depends of how powerful is the I/O subsystem of those database server.
Oct
24
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
@JimmyHoffa: I personally translate "never <rule>" to "are you sure that this is better than the result you'ld get from following <rule>?"
Oct
24
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
@JimmyHoffa: trying again. There are cases where Db-Side processing is not enough and client-code have to do extra processing to generate the information. So, yes, most set-based operations go to db-side which are set-based data cruncing engines. But sometimes just it does not do the job and you have to finish it on code (because you need sparse arrays, special collections, etc). There very few "nevers" that stand the test of reality...
Oct
24
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
@JimmyHoffa: No, the rule says "never do in app what the RDBMS can do well for you" . And I'm talking about transient information - not information persisted on database. I worked on systems where, to fullfill business rules, I needed to do processing on code. I remember a Business rule that I had, after do heavy processing on DB, do additional processing on that data to generate an (very important) report. I which I could use linq on that (it was done on the now-defunct Delphi.Net). In other words, linq can be used even following that rule.
Oct
24
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
@JimmyHoffa: That's not true, sometimes you generate transient information that need to be processed with the data you already have on app memory. Linq works wonders on that.
Oct
23
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
+100 - I could not say better.
Oct
23
comment “Never do in code what you can get the SQL server to do well for you” - Is this a recipe for a bad design?
@JimmyHoffa: certainly. Dealing with resultsets more than the enough to be visualized certainly fit better on the SQL Engine rather than application code. It's an architectural choice decide what fits where - and sometimes is not easy to detect.
Oct
10
comment Isn't MVC anti OOP?
@MichaelBorgwardt: 100% agreed. That one is really good. +1
Aug
22
comment Is it a good idea to design an architecture thinking that the User Interface classes can be replaced by a command line interface?
@MasonWheeler - I believe it would be more like PlotRoute(startPoint, endPoint, chart)