That still wouldn't be evidence that recruiters are trying to hire actual entry level positions. I'm not saying that they aren't, but simply that the post was not really very solid evidence of it if the poster isn't entry level.
This is not always an option; the argument applies as well to using tools written by others that expect secrets to be provided in an environment variable. The AWS SDK is a popular example. While it will also happily read credentials from a configuration file, or allow them to be explicitly passed, it's a popular method and is the only one that is consistent across the various SDKs that AWS provides.
It will be interesting to see if it actually works this time around; just having a new interface for deregistering from iMessage does not convince me that it will solve the issues.
The most frustrating, for me, is that in a one-on-one conversation, if your iPhone attempts and fails to send an iMessage to someone, it will tell you that it failed and allow you to send it as SMS instead.
However, in a group, if it attempts to send an iMessage to a member of the group that does not actually have a device supporting iMessage, it will silently fail; you will not know that the message was not sent to that person, nor will you be able to force it to send as SMS even if you know they did not receive it.
Do you mean Alameda county, or actually on Alameda, the island? If the former, I live in Alameda county, so that wouldn't explain it. If Alameda the island, why would costs be lower there? (honest question)
I'm skeptical of his estimated electricity cost; as a Bay Area resident, $0.12/kwh seemed low, so at first I thought he might be in an area of the country with lower energy costs, but he states he's actually in Silicon Valley.
I'm not sure how his particular usage and rates compare, but the rates for my most recent PG&E bill are as follows:
$0.13627 for the first 487.20 kWh
$0.15491 for the next 146.6 kWh
$0.31949 for the next 340.9 kWh
and then up.
In my area, according to my bill, average household usage (for the past month) is 400kWh, and 250kWh for "efficient homes." I'd imagine average use is higher in the summer months due to air conditioning, etc, and higher in the winter months due to heating and lighting.
So, right off the bat, $0.12/kWh is low, but perhaps rates were a bit lower when he did this analysis, or he lives in an area with cheaper rates? But let's assume that he's an efficient user of electricity, and uses 250 kWh/month for things aside from the car. He estimated 15k miles per year, at 3 miles/kWh, that's 416 kWh per month, which works out to roughlly $65.50/month, or $785/year, not $600.
If we instead assume he's an average user in a home that's not "efficient", it goes way up to roughly $92/month, or about $1100/year.
Obviously I don't know this person's exact rates for electricity, or his usage, and it may be the case that there are credits associated with having an electric car that can bring his average rates down or prevent him from going into the higher tiers (as he said, he could often charge for free at work), but regardless an estimate of $0.12/kWh seems strikingly low. I'm sure there are areas of the country where that's reasonable, or even high, but I don't think the Bay Area is one of them.
Of all the cost analyses of Tesla ownership that I've seen (admittedly few), I have yet to see one that attempts to take into account the higher marginal electricity cost associated with using significantly more electricity.
"[Java]’s used for everything, from web apps to games. Almost everything except embedded device software, and perhaps high performance parallel computation software."
Apparently hasn't ever heard of Embedded Java or Hadoop
Perhaps I'm missing something, but it seems like what this post describes isn't so much "test driven development" as "testing". Rigor of the data analysis aside, unless I misread, it seems like a comparison between not testing at all, and testing (I didn't notice any specific mention of TDD methodologies).
Shouldn't the comparison be between full-on TDD (e.g. write tests first, etc etc) and 'old fashioned' testing (for lack of a better term)?
"I illustrate the importance of growing the size of the pie to one’s share of pie to my entrepreneurship students at the Stanford Graduate School of Business by reminding them of the formula for a circle’s circumference versus its area. The formula for circumference (a proxy for share of pie) is linear (2 πr) vs. the formula for area, which is exponential (πr²)."
It seems to me that the value of growing the size of the pie as well as one's share of the pie is pretty easily understood and not in need of an analogy. But yet, this guy has decided to use one, and it is terrible.
Not only is it quadratic, not exponential (a relatively minor detail), but what on earth, exactly, is the radius meant to represent in this analogy?
Visualizing these numbers is a good idea, but this is a terrible execution.
- The line segments go in different directions, making it unnecessarily difficult to visually determine relative lengths
- The packet send from CA to the Netherlands and back to CA is split over many lines, making it even more difficult
- The data is split across multiple maps, making it nearly impossible to get a good sense of, say, just how much longer the packet roundtrip takes than a memory reference.
- It's nearly impossible to see the line segment for main memory reference
- Having the lines overlaid on a map is more distracting than anything else