HNHacker News
TopNewBestAskShowJobs

richie5um

145 karma · joined July 26, 2015

submissionscomments
richie5um··on Open Letter to Tim Cook
I agree. We can't prove it, but recommendations of "it just works" are what I feel has helped drive Apple - especially the Mac, but in the early years, also the iPhone.

Every year they seem to continue to introduce (via neglect/decisions/priorities) more reasons to pause at purchase time. And, recommendation time.

richie5um··on How to Accept Over-Engineering for What It Really Is
I think 'over-engineering' is too broadly used. Clearly some solutions are over-engineering, but most are built by skilled and experienced engineers who know that requirements change / evolve. In this (common) scenario, not predicting it - and creating the necessary 'over-engineered' solution - will lead to a failed project. Alternatively, predicting the wrong thing to 'over-engineer' is equally problematic.

Without these gambles, the project will often fail too.

It's a really rather difficult problem.

richie5um··on An External Replication on the Effects of Test-driven Development [pdf]
This.
richie5um··on Why's that company so big? I could do that in a weekend
Yeah. At least with a success you have a data point that it could be successful - with a failure, you don't even know that.
richie5um··on How being alone may be the key to rest
I've had this too.
richie5um··on iPhone 7
I think the key point is that they don't want a wired device. When viewed from that stance, these answers are obvious.

Wouldn't surprise me if iPhone 9 was wireless only. Somehow.

richie5um··on Google shelves plan for phone with interchangeable parts
If so, seems like a rather bad PR _stunt_.
richie5um··on Google shelves plan for phone with interchangeable parts
Completely agree. This is baffling.
richie5um··on Google shelves plan for phone with interchangeable parts
Yep. My only surprise is that they took them this long to stop working on it.

I can understand why this could be a useful internal experiment. But, clearly, some people at Google expected this to be a viable product. Baffling.

richie5um··on Vesper, Adieu
As per some other comments, I think the problem with Vesper is that it is too niche in a very well served market. The design is fantastic, but that doesn't matter if you can get more (functional) value elsewhere.
richie5um··on Scythe, the most-hyped board game of 2016, delivers
Thank you for the suggestion. I tried to play this a few times on iPad, but not managed to have enoughtime play through. Will give it another try.
richie5um··on Scythe, the most-hyped board game of 2016, delivers
Thank you for the suggestion.
richie5um··on Scythe, the most-hyped board game of 2016, delivers
Can you recommend some suitable games for a beginner please?
richie5um··on How We Do Spikes
Rant as much as you like :-)

I _think_ we are saying the same thing. I'd put 'done' in quotes for exactly the reasons you mention.

Timeboxing is merely used as a forced checkpoint; to re-assess across all activities/plans. It doesn't mean we can't follow on with more spike work.

At the end of the day, we, as a business, have to determine what we do (or don't do) and when. And we use spikes (or 'research', sic) to try to help inform those decisions.

If a problem occurs - as per your scalability example - or we identify more 'unknowns', we now need to make more decisions, and use spikes (and experience, and etc) to help inform those ... rinse/repeat.

richie5um··on How We Do Spikes
Nice article, thanks for sharing.

In addition to the great information you've provided, we identify features/decisions/choices that require spikes based on assessment that they are high risk and/or we have low confidence in our estimate. In addition, we sometimes use spikes to break xxx-large estimates into smaller pieces.

That way, until a project/plan/item has low (enough) risk, and high (enough) confidence, it needs more spikes.

We've found this model is a great way of identifying what needs spiking, and when a spike is 'done'. And, it also helps to ensure spikes don't end up consuming too much time.

Hope this is useful.

richie5um··on What no indie developer wants to hear about the App Store
This was my feel too.

I doubt the author would admit it, but, I think a lot of hyperbole is due to long-standing "Mac devs" and the author's circle of friends and acquaintances being unable to sustain a living from (merely) writing their own apps. Which is especially frustrating for them as the audience has grown dramatically over the past 5+ years.

Sure, the supply has grown considerably, and with that there are more 'light, snackable, mass-market apps'. But, that's what happens when the barrier to entry gets lower, and supply increases.

It is a true shame when we lose gifted 'indie' developers and some truly fantastic apps. But, no one has a right to a living.

Interestingly, and perhaps a hidden message in this article, is that there are significant parallels to draw to journalism.

← PreviousPage 2 of 2