There is some skepticism of wireless charging, so I will address all of it with some facts and personal experience.
In my opinion, the micro USB port was not designed with smartphones in mind.
With heavy use (such as shooting and uploading video) I can completely drain my Samsung Galaxy S III from 100% to 0% in about 90 minutes. Unless less strenuous use such as gameplay I can easily drain my phone in 3 or 4 hours. With the lightest of use and having a number of useful apps installed on my phone doing things in the background the battery never lasts more than 12 hours. With the first scenario, I have no way to charge my phone and it is out of commission in an hour or two (this is frustrating enough that I might buy a second battery) but to make the second and third scenarios feasible I leave my phone plugged into a charging port continuously. Scenario 4, less common but common enough, is that I can't use Waze the GPS app without being plugged into my car's cigarette lighter unless the trip is under an hour. But if I use the GPS during my trip without being plugged in, I arrive with a completely drained phone. That is not acceptable.
So instead of the charging port being used once every couple of days with the phone more or less stationary (like the designers of micro USB probably intended), most people including myself have the phone plugged in via the charging port continuously, always putting a strain on the connector.
What that means for me is that my phone was dead after 9 months of heavy use. The connector became bent internally. No micro USB cable would fit anymore, and I was in Detroit with only an approximate idea of how to get home with a dead phone. After a while of trying to work the cables I had on hand in, the motherboard cracked.
If you visit your smartphone insurance site, you'll see a failed charging port as one of the reasons why you're submitting a claim, right under lost and stolen. Essentially micro USB is too fragile for this type of application, and Apple and your insurance company know this.
Luckily I didn't have to go through my insurance and I got a new phone under warranty. The first thing I did was buy a Qi module to place inside the phone. Qi charging isn't feasible in the car. It's most feasible at work, so roughly 1/3 of the time I'm wirelessly charging. I expect the port on this new phone to last roughly 1/3 longer, or around 1 year.
Clearly, Samsung needs to figure out how to make the micro USB charging port more robust but Qi will help you until that happens.
They had the worst selection in the industry and once they pushed out ma and pas they jacked up their prices too high. I don't watch television or movies myself but my mother switched to Netflix by mail. Personally, I don't pay for any video ever. I watch what I need on Youtube.
If you want to do programming as a career, you need to be flexible enough to be able to pick up any language, so use whatever language you feel comfortable enough using to write maintainable code.
Forget about having to learn any specific language or environment. You should be able to pick up any language or environment on the job.
You need to learn how to plan, estimate how long that plan will take to complete, and finish it on time. Very few programmers I've worked with are any good at estimating how much time they will take to complete anything. The worst offenders take double the amount of time they say they will.
Forget about specific computer science trivia. You can look that all up, and it's all available in libraries with various licenses. When you're starting a new job, refresh yourself on how that problem is already being solved. If you need a refresher on a specific computer science concept, take some time and do so.
With this advice you won't burn out at age 25.
I didn't read the article, so your mileage may vary, but I have been programming since I was around 7 or 8 years old and I just turned 38.
Here goes. The vast majority of code that you will need to write and maintain does simple things. It should be simple and expressive so the next person can both fix your mistakes and add new behavior.
Every once in a long while you will be given something fairly complex to do, and as you gain experience you learn to isolate that complex piece, perhaps write tests and drivers, special debugging code for it, documentation and wiki entries, and otherwise treat that code specially so it doesn't become a burden.
Under 1% of code does tricky things. It is true that you will find non-trivial code in academic papers, maybe something like a cryptography research paper. Eventually that code will become something like openssl. But 99% of what you write will be simple database, GUI, or text processing work, or something else fairly mundane. That code is arguably much more important. The cryptography routine won't need much maintenance but GUI and database requirements change all the time.
If you find yourself always writing mind-numbingly difficult code, perhaps you need to relax a little bit, because you won't make it 30 years.
Goodbye, vomit-making system!
My analysis is that to spit was conserved because it is an onomatopoeia or onomatopia for you picky Brits.
Some of the other words are not much more than ma, ba, da, etc., the sounds that babies make, which form the cognitive basis for all languages. Some Google sleuthing will reward you with some interesting papers on this.
There is no such thing as bad publicity. It's a fake leak.
Please refrain from attacking de Icaza for these simple reasons.
Like Stallman, de Icaza has donated countless hours of organization and programming time to Linux. Neither got rich as a result. Politics aside, Linux is about superior engineering, even if only as a side effect. Because of the efforts of these two individuals, among many others, Linux is now the most popular operating system on the planet. By any stretch of the imagination, they were and are victorious. Android is closing in on a billion users, but regardless of what Google's marketing materials may tell you, Android is a Linux distribution, and GNU and GNOME have been perfecting Linux distributions for over two decades.
I understand that Android does not ship with much GNU or GNOME software, but GNU and GNOME are what built Linux. Without either, the foundations upon which Android runs would never have accreted enough functionality to even think about running a smartphone.
As mostly non-rich people, often not closely allied with specific companies, we don't have publicists or agents. We don't come off as polished. We don't have speech writers. Forgive us for seeming offensive, rude, obnoxious, conceited, full of ourselves, or some other adjective. We're people, and as engineers we're trained to traffic in the honest truth. Once you meet us you'll like us, for the most part. And even if you don't, enjoy using our software. Contribute if you like.