I thought that was the phrase...
I don't keep any tax data on my PC for security reasons. Had an iMac a while ago that blew up and it was a pain to get the drive out before trashing the thing. Easier just to keep the data in the tax cloud.
Based on my recent experience with an illness, this is exactly what you will have to do if you ever fall out of the normal bounds of straightforward illnesses. You will be managing your own treatment and trying to piece together what's wrong with you. You will burn through doctors and specialists one by one as they say they cannot help and refuse to let you make appointments. You will end up being the only person on the whole planet who cares and all the time you will be doing this when you are sick and/or drugged up. You will also realize that the whole health care system does not work like JIRA and that there is no follow up and your issue will be dropped if you don't continue to be the squeaky wheel. Health care is not engineering. It's scary how few engineering best practices are used in it and how full of holes the "system" has. Healthcare is probably about 40 years behind engineering in terms of problems solving and issue resolution and about a million years behind understanding how our bodies work vs "complex" systems we diddle around with all day on computers.
Moral of the story is - don't get sick with anything weird otherwise you're basically toast.
...had the display flowing over the edge of the phone's sides so you could place a phone on a table and have only the edge display info.
As a hiring manager, I would not care if a candidate had completed their degree online or offline so long as it was a real degree (we can test some things, but the whole point of a qualification is that it's supposed to mean something). However, there seems to be a big reluctance by established universities to give degrees based on these online courses so far. What needs to change for that to happen and will it ever?
Do these guys have a license to transmit in the cellular bands?
I have a Solar Tube in my house in California and it works excellently. Better looking but more expensive than this DIY version.
Yeah, like bleach.
No, they stopped selling them because transflective displays are limited by resolution. You can still get cheapy phones with them in Asia, but smartphones with HVGA or greater screen resolution don't have the space for the extra reflective part of the pixel that is required. One compromise is to use monochrome for the reflective part, which is what you see on the MotoACTV and WIMM smartwatches.
Corning's on a marketing offensive against sapphire, which is up and coming as a cover glass material. It's massively stronger than Gorilla (TM) Glass and so can offer better protection for the same thickness from impacts (although Corning will argue the opposite). The main problem has been that it's been expensive, but for some applications it's perfect (I'm looking at you smart watches) and the price is coming down, down, down.
Plastic guns? Been there, banned those... http://www.govtrack.us/congress/bills/100/hr4177
I've hired gray hairs, long hairs, dyed hair and no hairs as programming contractors. Age and experience are not so important to me for these mid-level programming gigs.I care about a few things though - are you up to date on not just coding, but contemporary development methodologies? Have you worked in an Agile team before? Do you have a niche skill that fits with my project (in my case often embedded programming, or Linux device drivers). I'm far more interested in what you've done in that last year before you came to me, so work experience is important. We *will* check if you can program and what approach you take to solving the type of problems we have via multiple interviews on the same day, so if you really can't program, then you will be found out. Also, we place a lot of weight on recommendations, so if you have worked with others on a team and they vouch for you, that will help a lot. Finally, if you are a jerk personality-wise, then we won't want you. Having been burnt more that once by hiring people with serious personality issues it's one of my top things I try to weed out at interview. Finally, a good agency might help you - they take a nasty cut, but push their employees.
Android is a gift, not a product. Android needs fixing to work properly because it doesn't work out of the box. Why? Because hardware changes from OEM to OEM, the government require mandatory support for features that aren't included, the customer (AT&T etc) require support for their apps or services, some very important ones, and last, but not least, it's buggy.
Details:
It takes about 6 months for a dedicated SCRUM team to knock a version of Android out that meets a major US carrier's requirements after Google releases their code to the community. I know because I've done it. Verizon has about 6000 requirements for their devices, Sprint and AT&T are not far behind. On top of the carrier requirements, which could be anything from implementing a custom address book sync adapter, to ensuring AGPS works accurately, you need to meet US Government requirements. CMAS is a great example. Further, there may be a stack of accessibility items that need to be done, although, Google dramatically increased their support there from ICS. So, once you've done the carrier requirements and the regulatory ones, you also then need to fix the bugs. These could be part of the open source - just look at the issues at code.google.com to see the outstanding ones, or they could be the result of the changes your chip set supplier made to have the code work with their hardware, or their proprietary codecs, etc.. Google may not have gotten around to fixing their bugs yet, but that doesn't mean you'll be able to ship a product today with without fixing them. Should those fixes be pushed back to the open source tree, absolutely, but are they? Why let a competitor benefit from our hard work? Also, you need to weed out any bugs that are unique to your hardware configuration - that could be caused by touch screen firmware, or the modem, bluetooth, or some other piece. Then, finally, you can decide if you want to reskin the UI or add your twiddly improvement. Sometimes that's an enhancement that customer's expect, like hyphenating dial strings, or sometimes it's a totally sexy homescreen widget. That part gets all the press, but all the other stuff must get done even if you decide to ship "pure android".
One man's constant is another man's variable. -- A.J. Perlis