On the plus side, you don't have the issue of links breaking because they send iOS devices to their mobile ghetto that ignores everything in the URL after the domain name.
486 karma · joined October 30, 2010
On the plus side, you don't have the issue of links breaking because they send iOS devices to their mobile ghetto that ignores everything in the URL after the domain name.
And, of course, centralizing the generation of emissions can be a good thing in that you just need to upgrade a few generators to improve efficiency/reduce emissions vs upgrading millions of cars.
But most iPad competitors have little-to-no reliance on a
connection to a desktop PC, the way an iPad does.Plus, there's far from a consensus that this is the best design out there. It hasn't been proven in mass production yet. STMicroelectronics, a massive player in microcontrollers (which often go into applications with even tougher power constraints than mobile phones), is pushing Silicon on Insulator pretty for their next generations.
With fixed point, you have to decide how many fraction bits you're going to have. If you have more than zero fractions bits, multiplies and divdes end up looking like this (assuming 16 fraction bits): result = (a * b + 1 << 15) >> 16 result = (a / b) << 16; // rounds to zero is a is close to b result = ((a << 4) / b) << 20; // not much range or precision on the result Of course, if your variables can't all be represented with the same number of fraction bits, you need to keep track of that and adjust your shifts for each calculation. You also need to do shifts when you add two numbers with different numbers of fraction bits. This stuff is all taken care of for you by floating point numbers.
With fixed point, if you mess up a calculation and it overflows, you get completely whacky results (wrap around) which will cause massive bugs. With floating point, you lose a bit or two of accuracy.
There are definitely places where fixed-point is needed. If you're on a microcontroller without an FPU, you'll have to learn your way around floating point. If you absolutely can't deal with the loss of precision you get with big floating point numbers, you'll have to use fixed point and make sure you understand the range of parameters that can go into each calculation and prevent overflow.
If floats work for you, just use them.
Just in general, be respectful. If you disagree with an answer, ask a clarifying question or move on. Don't tell me in the middle of an interview that out whole approach is wrong, especially when it's on a fairly subjective matter. We're doing the interview to learn about each other, not to convince each other about development philosophies. If you don't understand that there's a time and a place for disagreement, it's a warning sign to me (not saying disagreement is bad, but there are times when it's much more appropriate than others).
But, asking a bunch of overly aggressive questions will earn a candidate a "might not play well with others" footnote on my evaluation. The questions in the article are great. Getting confrontational when you're supposed to be making a good impression is a bit of a warning flag.
My advice: Use your questions to make sure you understand what kind of work you'll be doing. Use them to understand the team dynamic. Carefully use them to understand if the company has a reasonable business plan. Don't be a jerk and ask a lot of confrontational or trick questions.
Genre: Formal Female = 509 Male = 971 Difference = 462; 65.6% Verdict: MALE
Computing represents a pretty specialized topic, and most of the sample data with computing-related discussion will be from men. It would be pretty tough for any simple Bayesian analysis to account for this.
http://www.cnn.com/2011/WORLD/asiapcf/03/15/japan.nuclear.re...