And how should the government do that? With the tax income that these companies managed to avoid paying? Cool story bro.
The government should take money from the poor and funnel it into the coffers of these corporations. Did you miss the part where government is for the privatization of gains and the socialization of losses?
The alternative is asking for bankruptcy.
I can just about guarantee you that several buyers of bandwidth in Phoenix had contracts with the people who owned this fiber and those contracts specified multiple redundant paths out of the city.
Odds are we're looking at backup system failure or contract fraud. Probably the former.
How so? Everyone gets the same speed....
It's almost as fair as the toilet paper supply in Venezuela, Comrade!
Ah - they'll face opposition in some southern cities where they want to expand Google Fiber, but they won't suffer the wrath of the LGBT... community.
I've been working on a little side project. I would like to have an app where people can read updates that I send out. It seemed like a fun way to learn more about programming mobile apps and it's something I could actually use if I can get it to a decent state.
I'm keeping it simple. I decided the app would just be an rss feed reader. And that meant I need a feed. I want it to be very specific to my app so I decided the way to go would be to just create my own back end for cre
Put the key in off the license sticker on your PC
Yeah, the one that rubbed off the bottom of your laptop in three months and you forgot to take a picture of it when it was new...
Ah, I hope Redbox helped fund this feature since they're going to be a primary beneficiary!
Business can't plan or talk to customers or have any strategy whatsoever without at least some estimate...that's just the real world. If devs don't give estimates, managers have to make estimates. If managers don't make estimates, business makes estimates. You want devs to do the estimating.
I just don't want the boss to be disrespectful to me when the estimate is not accurate. Get us some estimation training or something. Don't give me a lecture. I'm too old for lectures.
you forgot to order the right Compaq IDE laptop header adapter. Whichever one it is for this model...
Suddenly a Laplink cable and a VirtualBox running DOS with a detachable D: doesn't seem so awful bad. Move the image from the XP box via flash drive or network, mount it loopback and profit before lunch.
If you don't have it, you'll make bad decisions. For example, answer the question, "should I use framework A, or should I write some code myself?" If you can't estimate how long it will take to use the framework and compare it to how long it will take to write the code yourself, then it is impossible to make a realistic decision.
That's a bad example because that's almost never my criteria. I could write my own framework almost as quickly as I could suss out the quirks of someone else's, and that's usually a teensy part of the overall project lifetime anyway. Instead, I judge on things like "do I want to spend the rest of my time here maintaining this thing?" and "who's going to own security updates?" and "will it be easier to hire people with experience on this one or on the one I haven't written yet?". Sometimes there's no good framework A to use, or maybe framework A exists and is popular but is unfit for this specific purpose, so we write something in-house. Either way, notice that "time to get started" is a trivial or nonexistent part of the equation.
Software project estimates are too often wrong, and the more time we throw at making them, the more we steal from the real work of building software. Also: Managers have a habit of treating developers’ back-of-the-envelope estimates as contractual deadlines, then freaking out when they’re missed. And wait, there’s more: Developers, terrified by that prospect, put more and more energy into obsessive trips down estimation rabbit-holes. Estimation becomes a form of “yak-shaving”—a ritual enacted to put off actual work.
Save me a seat at the table. I think these screenshots look like a nice update. This is timely to me because I was stuck in a meeting this week and looking at the presenter's projected Windows 7 desktop, and thinking of how ugly and unhelpful the current icon set is. Have you ever actually looked at the Outlook icon? It's a big "O" and a faint envelope in orange on a yellow background. Unless you've used it enough to associate that with Outlook, you wouldn't make the connection. The Mac Outlook icon is a lot simpler, nicer, and more visually obvious. The rest of his toolbar icons were the same: shapeless, indistinct, and unappealing. I like these new ones a lot more.
To the "change for change's sake!" Luddites: this isn't that. The Windows 8 Metro desktop abomination is that. This is a company updating its visual components to meet the expectations of the day. Everyone does this. Food labels change. Magazine layouts change. Car styling changes. Furniture colors change. Clothes change. Why do you think Windows icons should look the same for eternity? And spare me the "it's confusing!" whining - a file folder is still instantly recognizable as a file folder. Its look has evolved, but it's still the same basic shape and color.
Mark today on a calendar: I defended Windows's visual appearance. I never thought that would happen.
With your bare hands?!?
