mrwilliamchang

8 ms·

31.
Let me come to you(william.is)
1 points by mrwilliamchang 13y ago|0 comments
32.
Best programming shoes(william.is)
2 points by mrwilliamchang 14y ago|0 comments
33.
by mrwilliamchang 14y ago
Great interview.
34.
Predicting the next 25 years(william.is)
2 points by mrwilliamchang 14y ago|1 comments
35.
Understanding Camera Optics & Smartphone Camera Trends(anandtech.com)
1 points by mrwilliamchang 14y ago|0 comments
36.
by mrwilliamchang 14y ago
My favorite part: Turnaround Artist Manual – Chapter 1: Walk in with a frown; blame your predecessor; slash projects, budgets, people; lower expectations, loudly; and write off assets.
37.
Why the lightning plug had to be reversible(william.is)
2 points by mrwilliamchang 14y ago|0 comments
38.
by mrwilliamchang 14y ago
I have found the Big Nerd Ranch iOS programming book to be very good. http://www.amazon.com/iOS-Programming-Ranch-Guide-Guides/dp/... In relation to the criteria you raised the book is a good fit. - I understand most of the basic concept
39.
Twitter already pivoted(william.is)
1 points by mrwilliamchang 14y ago|0 comments
40.
by mrwilliamchang 14y ago
"the screen size of a tablet is the one spec that customers clearly recognize and associate with value" I don't think people want to pay more money for a larger screen when they are buying a tablet. Consumers have an ideal screen size (prob
41.
IPad Mini obsoletes the iPad(william.is)
2 points by mrwilliamchang 14y ago|5 comments
42.
by mrwilliamchang 14y ago
I think this post has a lot of interesting points, but in general I find asking interviewees questions that are not related to their job a little weird because no you are basing your judgement on things unrelated to the actual position. How
43.
Twitter for techies(william.is)
1 points by mrwilliamchang 14y ago|0 comments
44.
Apple's custom ARM approach for A6 pays off in JavaScript performance(arstechnica.com)
5 points by mrwilliamchang 14y ago|3 comments
45.
by mrwilliamchang 14y ago
Given that the request for a pull to refresh API is a subpoint to "Scrolling performance", I am guessing they found that their implementation of pull to refresh had all the drawbacks they listed under "QoI issues". From the post, "[Scrollin
46.
by mrwilliamchang 14y ago
Given this list of concerns, I believe that Facebook made the right decision in switching from HTML5 to native. The downside for them is now they have to write native code to support both Android and iOS.
47.
by mrwilliamchang 14y ago
I love this quote from the article. "Several Google projects rely on [J2ObjC], but when new projects first start working with it, they usually find new bugs to be fixed," And also "If you'd like to join the bug hunt, the full source code fo
48.
by mrwilliamchang 14y ago
I think that staying HTML 5 is a mistake. As the needs of your app expand, there will be a greater and greater need to use native API's. The longer you develop in HTML 5 the more code you will have to port when you finally do decide to tran
49.
by mrwilliamchang 14y ago
I'm impressed with how quickly FB, able to transition from emphasizing their web experience, to emphasizing their mobile experience. Most established web companies are moving much slower on this (ie Microsoft, Google, Yahoo!, Amazon, eBay,
50.
by mrwilliamchang 14y ago
I think the case you are making is a little exaggerated. It is not impossible to judge whether something you created is any good or not, without charging for it. The feedback that Joe is getting in the app store is not entirely worthless. A
51.
by mrwilliamchang 14y ago
This experiment is something I've been curious about for awhile. Tablets are so much easier and cheaper than traditional PC's that is hard to imagine normal consumers buying PC's in the future. However normal consumers still need to type. T
52.
by mrwilliamchang 14y ago
What I like about this article is that it is a good example of how to think about how the stock market evaluates tech stocks.