See my sibling comment -- I honestly believe it's describing what people already do. I'm curious what someone who's read the paper (like I have) thinks.
As with any technology, CoreData works well when the problem domain falls within its sweet spot. When the problem domain is outside that, CoreData can quickly become a challenge to work with.
While this is true, the problem is that the sweet spot for Core Data is quite small. Given the framework description, it’s quite easy to go with Core Data when some of its many drawbacks mean you really shouldn’t.
Abstracting control flow is extremely powerful. Those interested in learning more should explore monads, which offer some very useful methods of generalizing and composing control flow abstractions.
I couldn't agree with Brent more. Performance is absolutely critical to the user experience of an app. It is not premature optimization to ensure an app remains responsive to the user at all times and can handle real-world sized data sets. It is good engineering.
According to Robert Cringley iOS 7 includes Bluetooth mouse support: http://www.cringely.com/2013/09/19/the-secret-of-ios-7/. However, I haven't seen this confirmed anywhere. I would like to know where he heard this and hear more about how it works. Any links on this would be great!
This is very nice as a review of Git, but probably best in that context rather than an initial presentation of the concepts. I really enjoyed the Source Control Made Easy series by Jim Weirich. It presents the same information in an easily digestible, step-by-step approach. Highly recommended for those trying to understand how Git works and how to best make use of it.
Employer provided 401k plans are great when you receive matching contributions, but otherwise not a very good. They generally have extremely limited investment options. It will be hard to offer general advice applicable to all 401k participants since they will each have a small selection of investment vehicles.
The best advice is to make sure you contribute enough to receive the matching contribution, and then immediately roll the money out into an IRA as soon as you leave the employer. This will allow you access to a much wider range of investment vehicles.
> Also in a 401(k) plan you get to purchase mutual funds at NAV which you cannot do through an IRA.
I don't believe that's correct. My understanding is that all mutual funds (excl. closed-end funds) must trade at NAV regardless of the type of account they're held in.
"That is, the price that investors pay to purchase mutual fund and most UIT shares is the approximate per share NAV, plus any fees that the fund imposes at purchase (such as sales loads or purchase fees). The price that investors receive on redemptions is the approximate per share NAV at redemption, minus any fees that the fund deducts at that time (such as deferred sales loads or redemption fees)."
In 401(k) the loads or purchase/redemption fees are usually waived (with the exception of short term redemption fees which are sometimes imposed for not holding funds at least 30-90 days to discourage people trying to "day trade" mutual funds).
Also, I did forget to mention that, in addition to waiving CDSC charges, large plans can usually qualify for cheaper share classes of the funds. For example Admiral or Signal shares at Vanguard rather than the retail Investor shares.
There are a great many no-load funds. A cost-sensitive investor will naturally buy index funds, and all the major IRA custodians offer at minimum, their in-house index funds fee free.
anandabits - that's the point of our service! It is specific advice customizable to your specific 401(k) plan. Check out the site to see what I'm talking about.
I've got to agree w/ your last point - it is typically best to move money into an IRA. There are cases however where a larger employer may be able to get lower cost funds than would be available to you in a stand-alone IRA.
What is most important is putting away enough money to maximize any company match you might get.
But you're right, the limited options can be problematic; and that's why we've created Kivalia.
This article covers the basic data format Git uses internally and explains how the staging area works. It's a good primer for those looking to have a little bit deeper understanding.
If you like this article and are looking for a much more in-depth understanding of how Git works, I recommend Jim Weirich's Source Control Made Easy series.
