...being told to call around to different departments until you end up with the person you spoke to originally
- Lack of direction
- Bloated interface
- Too much Evil
If everyone in your group uses the same editor, say MS Visual Studio, this is probably less of a problem.
why are you making those errors?
...because it "integrates with a pretty scary existing system". Something written from scratch would have much much fewer. I guess it does speak of quality of the code but also depends on the quality of data it has to work with, external interfaces, changing user requirements, etc.
The jury deliberated for 2 days, so there were some serious arguments to deliberate about, and thus this was not a frivolous lawsuit.
Lawsuites like this impose a cost of litigation but in the long run they give us something more important, something other places like Korea or China lack. This advantage is the prime reason the Silicone Valley exists in the Valley as opposed to some shithole where laws are questionable and judges go to the highest bidder.
In this example, the lawsuit tries to establish equal treatment of men and women in the workforce. Women comprise over 50% of population and any country that can tap that talent (and most countries cannot) suddenly has access to 2x the number of capable candidates, a tremendous advantage. Most of these lawsuites are impossible for lack of proof, but if something is so obvious that it is provable in court it would be a waste not to persue.
Now imagine a society where all the respectable and compensated positions are given to communist party member's cousin's son-in-laws. All their talent rots in slums. This is the current situation at some 75% of the world. Good luck starting any successful ventures there.
Imagine something that takes 0.001 ms on a cheap CPU and is used once a day. Is it worth making it faster for a day of work and a man-week of maintenance increase due to complexity?
- Depends program objectives. Most of my code does not need to be fast, and some even works better if it is slow so it does not pig some resource
- Usually the case, then again, see "Fast"
- not bloated
- not buggy
- BS. I just completed a complex project that integrates with pretty scary existing system. It is 95% bugs at this point, yet does not make it bad code. Most bugs will get weeded out over a few weeks, as long as code is easy to read and maintain.
- respectful of the user's privacy
- hardened with regard to hacking
- not encumbered by dependencies
- adequately featured
- well supported
- It is if someone pays for it?
- well documented for the end user
- Users of a very complex iPhone never read a single page of documentation. I prefer things that just work as expected
So IMHO it boils down to maintenability and security.
Norway in 2011:
Try to detect certain mental disorders early and restrict their access to firearms. Tighten control over who has access to firearms.
Paris last Wednesday, Sydney last month, etc.:
Figure out why perfectly sane and capable muslims have frequent urges to execute random civilians. Find and fix the root of the problem.
While #1 is difficult to accomplish, many jurisdictions try their best to restrict access to firearms.
#2 is easy to fix but political pressures tie our hands under "freedom of religion" umbrella. My personal opinion is that we should be keeping zealot followers of Sharia Law in countries where Sharia is the official law of the land, rendering them harmless. I would also like to see the the enablers of the assassins called to justice. I am sure they had lots of help -- moral, financial and operational to carry out this massacre.