iOS devices are another story. Apple abandons them fairly quickly.
An iphone 4 ran iOS 7 (4 years later) which is better than any other phone I know. And abandonment is a little overstated, because the phone works fine with iOS 7, and will continue to do so, much like many Android phones still run fine on Gingerbread or Ice Cream Sandwich or Jelly Bean.
Also they had an ancient, hacked and weird version of GCC for ages. I gather they have a modern compiler now, but it sure sucked a lot when they didn't.
Did you last work on a Mac? OS9?
What about my concern on who decides they are criminals? What if I don't trust the police to make such judgement?
If people with guns are pointing them at other people without guns, and state they will kill them unless 'x', I'd say the room for error in judgement is rather small, probably so close to 0 that error is impossible.
I fully agree on the question, but not on the answer. I simply do not wish the police to have the right to decide how many hostages it's ok to kill in a hostage situation. And giving them the weapons to apply the result of that decision is too close to implying they have the right to take it.
I think everyone reasonable agrees that the decision in such a situation is an extremely hard one. For me, that's precisely the reason to place the burden of making that decision far from the people we use to protect us from common criminals. Because those people are the most biased on precisely the taking of that kind of decisions.
In the case of the Russians, I believe that decision was made all the way at the top circles, if not the top. Israel, as well, was at the top. Do you have a case where such a decision was made by a local street policeman? Or even a sergeant? Instead of attacking windmills, how about focusing on something realistic?
Programmers that chat to each other tend to be in the bottom 50% of productivity.
Programmers that chat throughout the day tend to miss deadlines.
Programmers that sit in meetings do not write code.
Now, that is not to say that programmers shouldn't talk to each other or users, but that should happen in small time slices, not throughout the day, as every interruption costs 30+ minutes, depending upon the level of being done.
Yo soy el stupido = I am the stupido?
I think you meant "Yo soy estupido"
Simpler and correctly accented: "Soy estúpido."
The attack of the grammar spaniards!!!
Have 2 monitors side by side.
Because when something fails, most users will buy a new one instead of repairing the last one... and guess what... probably they will buy another samsung device! So instead of selling one TV each 15 years, they sell one each 3-5 years... even if just 1/3 of original buyers buy again samsung, it is still a win situation for then.
This is not an issue just with TVs, laptops, phones, routers, cars, washing machines, dishwashers, etc, are all cheaper to replace than repair if you cannot do it yourself. Sadly, the ability to fix things like this appears to be a shrinking skill set, but for those that have it and can afford an hour or two here or there, you'll save tons of money over your lifespan. I know I saved several thousand just in the past couple of months being a plumber, mechanic, electrician carpenter and painter. That leaves money to do other things.
If you want to frame coding as a social activity, you need to emphasize "collaborative problem-solving" and downplay the "lone hacker" stereotype.
Egads, you're suggesting you cut programming productivity by 80% or more. If programming were burger flipping, that might work, but it's not, or at least not where I work.