But when you make the most profitable way the preferred way, you shift the power from the people to a controlling party, at which point, the price goes up to suit the "investors".
I've got into a habit of defining pre and post-call checks on just about everything. It's knocked down my regression and defect rate quite considerably. Assumptions are dangerous - so always check them.
Microsoft are actually leading this if you ask me with PEX:
The worst thing I find is when you get a part in it which is designed to work with several different products and it has extra holes drilled in it. Rather than specialising the CAM / drilling process, they throw some little stickers in to cover up the holes.
The only reason they needed QA is the software was a giant toilet-clogging turd. There were no formal unit or integration test cases so it was used to catch regressions against massive test plans knocked up in Excel, Word and god-knows what else.
I think they should bring back the "old" Nano. A lot of people haven't bought the new one as they still like tactile controls and want a screen large enough to watch a video. They also don't want an iPhone or to pay for the touch. They shot themselves there.
There has been a lot of innovation with the iPod but some of it hasn't always been that great. Consider the "stick" shaped shuffle which reverted back to the old design in the latest revision. I consider the touch-based iPod Nano to be the same sort of unnecessary crock.
I did exactly the same, except to get a contract outfit off the ground. I paid off about $60k in total (in GBP) over 10 years. I worked out that in total I made about 20% more than salaried people over the time. It definitely wasn't worth it.
The irony of this is that I have just cancelled my Spotify account because tracks I have on my playlists have disappeared due to I assume various problems with record labels.
It's utterly annoying when you sit down in the office and the first track you go to is gone.
I won't go further than to say that when semantics are change by politics, we all lose. Legitimising murder in the name of war and justice is a slippery slope.
"An-eye-for-an-eye-for-an-eye-for-an-eye ... ends in making everybody blind." (Ghandi).
This is the typical result of "enterprise" applications which are more interested in decoupling the logging system from the framework versus picking one that works.
Over-abstraction at work.
There is a "commons logging" for .Net as well which replicates the entire log4net API 1:1. That is where the crazy starts to set in.
The definition of murder was "manipulated" around the time of the second world war to include the world "unlawful".
Find an old dictionary (circa 1930) and look up the definition of murder. It mentions only a "premediated killing".
This is an unpopular opinion, especially with the "perpetual war" that we have to endure, but if you kill another person regardless of the justification, even if it's your job, or they wronged you, then you are a murderer. That includes the people who perform the executions and all soldiers. Putting a label on it or changing semantics doesn't make it ok.
(This was downvoted immediately obviously by a supporter of murderers)
Like I suspected, this entire thread has been turned by zealots into a Microsoft-bashing exercise.
I genuinely dispair for people who spend their entire time platform bashing and don't add something constructive to the discussion or tar and feather a side religiously. It paints a very bad picture of the "startup culture" amongst more established organisations.
It's disgusting.