I think this is quite incorrect. I've recently got the new iPhone and looked at the possible options across AT&T, Verizon, T-Mobile (I haven't included Sprint for a reason I cannot recall right now).

If you calculate the costs over a 2 year span, the differences are quite significant: http://jots.mypopescu.com/post/61007400356/iphone-5s-choosin...

_nb_: I haven't included any interest/depreciation rates though.

That's exactly what I've been searching for!

Thanks for digging this up. I find the 2 models being almost identical. And as one can read in that thread there can be subcategories that one might consider.

My preference is still with the formulation Slava came up with:

1. it's slightly easier to think only about 3 buckets 2. category names are more descriptive 3. their explanation in the post makes them more approachable/easier to grasp than formulation in the Wikipedia page

I haven't read the book, nor did I know about Kano's model until today, so thanks again.

I have always wondered how many people use the stock Janus/maximum-awesome Vim setups? How do people maintain their customizations? (the same questions actually apply to other configuration systems like dotfiles, etc.)

The reason I ask is that I've found these projects absolutely great in helping me learn more, discovering new plugins, and putting them all together in a (somewhat) maintenable way. But I've ended up with my own forks. And while I only tweak them every 6months or so, I usually have a hard time rediscovering the improvements that these systems have made in the meanwhile.

Yeah, catching up is always an issue, I've already stayed behind in my master branch, which is unfortunate.

I'm seeing myself eventually building a custom configuration from the ground up.

I've recently tried adopting the http://www.bulletjournal.com/ system, but using Evernote. Unfortunately I wasn't able to make it work for me.

After just a few days I've found myself not being able to figure out at a glance what's next and having to go back and forth the notes. That even if I've spent the time to inter-link things. But at this point I should also mention that in my role (product manager) I have quite a few projects on my plate at all time and a month long list of things is usually in the high tens/hundred items (and doesn't include meetings).

I was really attracted by the BulletJournal system as it felt in a way similar to what I've been using, but with a nicer/cleaner visual representation. Basically I have my long list of things in a tool. Every Monday I spend a bit of time extracting what's the focus for the week into a separate file. In this file I also log daily activity. At the end of the week there's a short review and then I'm archiving the week.

I'm sorry you weren't able to make it work. That kind of workload sounds like a lot for anything. You might consider using something like Omnifocus or Things in order to keep track of all of that. (among other solutions for tracking all of that kind of data) They're a bit more tailor-made for something like that. Evernote is less of a heavy task-management system as it is a place to dump a lot of information. (such as the entire web page with a brownie recipe I have saved. perfect for that, less for managing 10 complicated projects)

Honestly though, it sounds like you have a system already in place that works well for you. Why switch away? The only thing you might do is use a notebook to dump all the stuff from one week into, then have your short review on a separate page(s), then start over. (using indices in the front of the notebook to keep an easy reference to start of each section. start of week 1, start of week 1 review, start of week 2, etc.) But I suppose one size does not fit all. Do what works and helps you keep track of things!

> This is a picture of me in 2009, right around when I started Pinboard. I'm standing on a balcony in Botosani county, Romania, in the poorest county in the European Union.

I had no idea (based on his name) that Maciej started Pinboard in Romania.

A Polish immigrant to America starts a one-man business while traveling (staying? working?) in Romania, gives it an Indian TLD, and moves back to America to work on it full-time. And only a short while ago I'd been reading his blog about Argentinian cuisine. 50 years ago, people would have found this mind-boggling. The Internet truly is global.

Neither do I. Impressive. Never used Pinboard, but I'll take a look.

PS. And actually Bulgaria is the poorest, Romania does better.

Bulgaria didn't have as high a standard of living as Romania at the time, 2009, but Botosani county on Romania's Moldovan border was the poorest county in the EU. Whether or not it still is, I do not now.

He is referring to Botosani county being the poorest in EU, not the count_r_y Romania. Fell for it too :)

I am not a Pinboard "user" but it is a great way to find stuff to read. The system has a very nice url system. For example:

https://pinboard.in/t:minimalism

I'm a pinboard.in user, but I actually find the URL scheme annoying, at least compared to delicious. I find it much easier to type

http://delicious.com/username/tag

than

http://pinboard.in/u:username/t:tag

The argument has been that by specifying what each URL part is, you can build a link to https://pinboard.in/t:minimalism in the first place. Is delicious.com/minimalism the tag minimalism or the user minimalism? And what is delicious.com/settings? In practice, delicious gets around this by making all-user tags accessible at http://delicious.com/tag/iphone, but then you can't have a user named "tag". Or "tools", or "help", or "about", or "terms", and there's probably more and they might change every now and then.

Indeed, and it'll be grown increasingly into a platform for subscription-based consumption, when the Pinboard Reader is launched.

You can basically create your own reddit feed of tags, even if you don't intend to use the bookmark feature - which is quite excellent.

As a long time pinboard user, I devoutly hope not. It's a great service for antisocial people like me, and I'd be disappointed were it to develop that "social" layer of oily mucus.

You can already subscribe to tags. It's not social in a sense that you can interact directly with others, but it does have a secret feature of sharing your bookmarks with others by making them public.

Using git bundle looks like an interesting idea, but the solution suggested in the post is seems incomplete:

1. it's only working for master 2. it bundles everything making an update on a different machine more difficult

I'm pretty sure that people that use git bundle extensively know how to handle these scenarios though (I don't)

1. I'm still relatively new to git, so haven't looked into branching, etc., yet. Worst case scenario, add other branches to the post-commit file. 2. It really is intended as a "backup", if I was looking to interact with more machines, I'd setup a central repository that everybody could commit to, and individuals could still use this to backup their local repos.

That's a very interesting subcategorization of game changers.

What I find quite interesting about thinking only in terms of hooks and painkillers is that this categorization might trick you.

A series of hooks could prove to be only distractions. A features that users think it's awesome is not necessarily "signing the deal". They might be an eye catcher, a conversation started, but in the end you might find that not enough users actually care about it.

As for painkillers, well, I think that those could be anything from game changers to distractions (include too many painkillers and you'll get MS Office :-).

Once again, this is only to say that I think I'd be thinking in terms of hooks and painkillers only after making sure that the feature is a game changer. And not vice versa.

ps: by the way I feel I disagree with some of the hooks you've listed. But that part of the discussion would fit better in a different context :-).

I don't think you should have a series of Hooks. The Hook's value is to get people's attention: it's often not actually that useful in ordinary usage, just like PageRank is far from the complete Google ranking algorithm and people usually don't care about the satellite imagery on Google Maps when they just want to get from place to place. But they made people stand up and think "Wow" when the product came out, and that's what convinced them to try using the Painkillers. Oftentimes the Hook is quietly retired once the product gains market acceptance.

By definition, if something is a Distraction, it's not a Painkiller. :-) This relates to the common marketing wisdom that your product should be an "aspirin", not a "vitamin". You should solve something that's painful to the user, not just an "Oh hey, this looks shiny."

When talking about painkillers I think we should also think about how many have that pain. If it's too little, then that painkiller can be a distraction. So while I fully agree with you that a distraction is not a painkiller, the opposite is not always true.

Plus I think painkillers could definitely be just showstoppers.

Once again, I find this subcategorization working great as a refinement applied to the @coffeemug's model. The only point is not to start with it directly.

I think this is very much true considering Samsung's most (?) successful campaign lately has been focusing on the exact opposite message (Apple fanboys not knowing what's happening outside their world)

How was that campaign successful? It didn't move Apple a dent from the high end market.

But it sold lots of Samsung phones.

True. Always thought it was Apple that was targeted, but it was mostly a node to the Apple-haters crowd.

One aspect of micro-benchmarks that is most of the time ignored is that they reveal different default settings various systems come with. And unfortunately after seeing the results, not too many dig deeper to figure them out.

Indeed. And the default settings reveal something about a system's priorities. If you care about your users' data, then Mongo's default settings should be a giant red flag. The revealed priority is seeming fast.

In noSQL world, any DB's default settings should be a giant red flag. Don't get me started about HBase... I lost 2 hours of data this way. :(

That was actually one of the explicit design goals of Rethink -- pick defaults such that users never have to wonder about the safety of their data. I know the folks at Riak are also in this camp, so there are definitely NoSQL dbs that do this well.

I'm not sure Riak is a good example as it's another example of an extremely slow database.

There's also the angle that if it's to offer no performance benefit, perhaps a classic relational database will do it?

I'm curious to hear your thoughts about it.

As someone that uses hbase in production, I'd be interested in hearing the setting you are talking about.

Honestly, I've been very positively impressed with CouchDB so far.

How about "they should be an invitation to learn more about the system" :D? As far as I can tell, in many cases these defaults have almost never been reviewed by devs because most of the early users already knew what tweaks they needed.

I dunno. Personally I'm a big fan of the "sane default or no default" approach. I think that mongo's former approach is irresponsible engineering (I understand they have fixed it recently).