Contributions
Re: Should we have dedicated code reviewers or should everyone do code reviews?
Here's my take on it: A given product/module/subdivision/etc. should have at least two developers who regularly work on it. Those developers should review each others' code. Rationale: You should be doing (1) anyway, if only for the redundancy of solving the "developer gets hit by a beer truck" problem. Given (1), each has the appropriate context with which to evaluate the changes. Sure, anyone can look for bad code constructions, but unless you are familiar with how the code works or what the application is supposed to do, you are more likely to miss logical bugs.A dedicated reviewer lacks the context in which to fully appreciate what the application is supposed to do.2.9KViews0likes0CommentsRe: What Database Should I Choose?
My personal experience is: Oracle is expensive and slow. MySQL is fast, though has had some teething issues over the years. It's gotten a little slower as they've added features, but is still pretty fast, and has gotten a lot more reliable. That said, change your default table type to InnoDB. MyISAM is a toy and should not be used in production. See MySQL Storage Engine DocsandGuide to MySQL storage engines. SQL Server had a decent edge on MySQL with regards to features at the beginning of the decade, but that has narrowed in recent years. I haven't used it much in production to really comment further.3.1KViews0likes0Comments