23,861 reputation
347102
bio website
location
age
visits member for 3 years, 11 months
seen Aug 26 at 17:08

Oct
28
answered I want a trivial example of where MongoDB can scale but a relational database will have trouble
Oct
26
awarded  Good Answer
Oct
8
comment Database is performing slow, even all the tables are having normalization
I would disagree, if I asked this question in an interview I would expect the interviewee to say a lot of other things before mentioning denormalization. Denormalization in an already existing database is a serious risk, I would expect the person to not suggest that as the first alternative, although I would expect given the way the question is worded that they would mention denormalization and both the pros and cons.
Oct
8
comment Database is performing slow, even all the tables are having normalization
@JeffO, Yes that is one way to fix some problems with poor performance if the problem is mainly in the reporting end of things.
Oct
8
comment Database is performing slow, even all the tables are having normalization
And check to see if all the joins are used. I have seen this espcially when people are using views that call views where lots of unneeded work was being done that would not have happened if they had written the code directly. But I have seen this in nonview code as well. And of course not selecting information you don't need (such as using select * in any query using a join).
Oct
8
answered Database is performing slow, even all the tables are having normalization
Oct
8
comment Database is performing slow, even all the tables are having normalization
I would never suggest denormalization as the first performance fix. This is the fix of last resort as it often creates data integrity problems. And I certainly would never mention it without discussing how I would avoid data integrity problems and how denormalizing could slow inserts/updates/deletes but speed up selects. Likely proper indexing would make the normalized tables perform well without the risks of denormalizing.
Oct
7
comment How to code review without offending other developers
'The code doesn't progress until the reviewer approves it, and the reviewer won't approve it until the questions are answered." I thnk this is key. If you do code review after teh code has moved to Qa or even prod, then people will resist chaning it even more. If they know that they have to pass code review, they will be more open to making changes.
Sep
24
awarded  database
Sep
23
comment Sprint planning and accommodating slack
@KrisVanBael, in an ideal world yes. But I would wager that most people who think they are doing agile do not plan that way. Of course I would also wager that many of the organizations that think they have agile processes, don't.
Sep
17
answered Best practice in application design / SQL authentication
Sep
11
answered Why isn't protection against SQL injection a high priority?
Sep
11
comment Is rotating developers on a project a good or bad idea?
What I would suggest is that you make the intital team that starts the project composed of some current legacy devlopers and some current new project devlopers. Keep them through the porject. At the end the lagacy devlopers support the new product and the new devlopers join some other legacy developers to do the next project. That way the team is teh same through the project (Or major release) but legacy people get up to speed on what they will be supporting later. New hires shoudl generally start on legaacy unless they have some special skill you team doesn;t havea nd needs for the project.
Sep
10
awarded  Yearling
Aug
14
comment Is handwriting out code an efficient way to learn a programming language?
From the perspective of someone who has taught, it was probably done to make cheating more difficult. The fact that yes people do retain knowldge better when they have hand-written it is a side benefit.
Aug
13
comment What makes C so popular in the age of OOP?
This answer is also the answer to why do we still need SQL!
Aug
13
answered Safely fixing production database data
Aug
10
awarded  Nice Answer
Aug
5
revised How should I deal with problems with completed stories in agile
fixed typos and capitalization
Jul
30
comment Is Business Intelligence (BI) the Right Job Title?
@FlorianMargaine, BI is a programming field