Reputation
558
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 12
Newest
 Quorum
Impact
~7k people reached

Apr
22
accepted Readability & Performance: Is it better to allow the Java garbage collector to clear a datastructure?
Apr
21
comment Readability & Performance: Is it better to allow the Java garbage collector to clear a datastructure?
The cleared array would be filled again with new content. That's why null wasn't used.
Apr
21
asked Readability & Performance: Is it better to allow the Java garbage collector to clear a datastructure?
Apr
16
comment What to bring to a programming interview?
I still don't see why it's necessary to bring a resume printout. Interviews should be conducted without having to ask the candidate to bring printouts of anything: nrecursions.blogspot.in/2015/10/…
Mar
15
accepted Transitioning from C++ multithreading to Java multithreading
Mar
14
comment Transitioning from C++ multithreading to Java multithreading
Ah the example I had just copied from the popular mutex tutorial on the internet. While the use of smart-pointer-protected locks is better, it'd help to know that there are some applications (like one I worked on), which needs such fast processing, that smart pointers actually slow down the program by a third. We had to replace boost pointer containers with a simple array implementation and noticed a huge improvement in performance. For smart pointer mutexes also, one man's meat is another man's poison.
Mar
14
asked Transitioning from C++ multithreading to Java multithreading
Feb
17
accepted Is it viable to copy contents of a database into a program's memory, if multiple queries take time?
Feb
16
comment Is it viable to copy contents of a database into a program's memory, if multiple queries take time?
@DocBrown: The result could be stored in a table having 1 row for each combination of ABCD. Every combination is checked with rows of E and if a condition is satisfied, an integer value associated with that combination, is incremented. That integer value is stored in the table having 1 row for each combination, as you indicated. So this final "count" table will have 240 million rows.
Feb
16
comment Is it viable to copy contents of a database into a program's memory, if multiple queries take time?
@MichaelT: In one pass? Really? I didn't picture that being possible. There is a variety of columns in table E. 240 million is just the start. There's plenty more data that's going to come in later, which is why I'm wondering if it really is better to do the counting in SQL or to take the data into Java and work on it there.
Feb
16
revised Is it viable to copy contents of a database into a program's memory, if multiple queries take time?
added more detail
Feb
16
asked Is it viable to copy contents of a database into a program's memory, if multiple queries take time?
Jan
17
comment Git Bisect found the buggy commit. Now what?
@gnat: What's with the link on chameleon questions? I didn't change the question. I was mentioning the solution (and mentioning to delnan that I understood what he explained) to the problem, as part of my update to the question.
Jan
17
accepted Importance of uniformity of development architecture across the team
Jan
17
comment Git Bisect found the buggy commit. Now what?
Hmm...interesting info about git blame. Actually, for bad commits A and B, I didn't know which line of code caused the problem, so bisect was necessary. After finding the commit I had a look at the files that had got modified during the commit and the diff of what changes were done. Looks like that's exactly what a blame does. Still, blame and show seem to be nice ways of getting the job done. Thanks!
Jan
16
revised Git Bisect found the buggy commit. Now what?
removed an unnecessary, incorrect line
Jan
16
accepted Git Bisect found the buggy commit. Now what?
Jan
16
comment Git Bisect found the buggy commit. Now what?
Thanks. I've updated my question to explain what I understood.
Jan
16
revised Git Bisect found the buggy commit. Now what?
added more detail
Jan
16
asked Git Bisect found the buggy commit. Now what?