The internet is just full of these idiotic comparisons.

I am frustrated because it is comparing apples and oranges. Sure - both take photos, however most comparisons made are unfair, biased and just plain wrong. Let me get this out of the way first - any DSLR or modern mirrorless camera will smoke any cellphone camera under all circumstances, ignoring for the moment the photographer and the concept of availability. Once you start arguing that the camera you have with you is better than the one left at home, you are no longer comparing cameras. You are comparing laziness and personal attributes of the photographer. I am not saying it does not contribute to a camera system's success or usefulness, but one cannot use it in image quality comparisons - which is what all these reviews are about. Furthermore, all these reviewers have the tendency to show images at small web resolutions of about 0.3MP. Granted, for exclusive online use that is a fair comparison, but once you use it as background image on your computer or try to print it, the small resolution images are misleading.

So we have established three aspects to describe the relative benefit of one camera system over another:
1. Camera
2. Portability / Availability
3. Photographer skills

Americans especially like to advertise stuff to people as if people are idiots. Agreed - most of the time they would be correct in assuming so. However, when it could potentially adversely affect your well being I think they have gone overboard. Look at the bottle of nice carrot juice below:

If your RDA (Recommended Daily Allowance) is determined to be x, and you consume 7x of it per day, I presume you would be 7 times as healthy? Logic suggests that by this reasoning, the RDA should be infinite. Why? Because if 7x is 700% better than x, then surely 100x is 10000% better, and so on.

I recently ran into an interesting issue where the qODBC bridge we use to connect to QuickBooks from our custom application would fail to properly initialize QuickBooks. In principal the qODBC bridge is an ODBC driver that connects to QuickBooks via QuickBooks's API by launching an instance of the actual QB GUI and then communicating that way with it. It follows that our custom application connects in turn to qODBC to perform database related calls to QuickBooks.

Recently after a server patching we started receiving these error messages when trying to connect to QuickBooks:

Unhandled Exception: System.Exception: Cannot connect to QuickBooks: ERROR [00000] [QODBC] QB Begin Session Failed. Error = >80040408, Could not start QuickBooks. ERROR [00000] [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks. ---> System.Data.Odbc.OdbcException: ERROR [00000] [QODBC] QB Begin Session Failed. Error = 80040408, Could not start QuickBooks.

Make/Model: MINI Cooper John Cooper Works 2016
Colour: Rebel green with red roof
New?: Demo, had 656km on the clock
Engine: 2.0l Turbocharged
Power/Torque: 170kW (228 BHP) / 320Nm (236 ft/lb)
Average Fuel Consumption: 5 - 7.5 l/100 km (Highway - City)
Performance: 0-100km/h in 6.1s, 247 km/h top speed
Owned: Jan 2016 - Mar 2018

Notes:
Pardon the dirt - these are the only pictures I have.

For a review, see the new 2018 JCW. The two cars are basically identical for all practical purposes and most comments apply the same.

If you ever tried to backup / restore a Microsoft SQL Server database from one server to another, or one database instance to another, you might have run into the issue where the database security user account has been restored but it does not have a corresponding instance login account, or, the instance login account is present but it is not linked to it. You may be tempted to open up the instance login account and assign it to the database and database user account, but you will receive an error:

User, group, or role 'XXX' already exists in the current database (Microsoft SQL Server, Error: 15023)

The fix is simple - run this from an SQL window: