Thank you for your message.
I admit that it's the first time I hear about user habitability. I just
read the link you included, and the two concepts look indeed very
similar. It wouldn't be the first time a past idea was revisited.
I have however two issues with the idea of Software Habitability, as I
understand it now:
1. It doesn't specify strongly the fact that a software developer is the
user of software design. We've always had the problem in this industry
that the user of software doesn't care how the software is structured.
In writing the articles, I felt it was important to clearly state that
software design is not userless.
2. I couldn't find any practical ideas on how to achieve Software
Habitability. There seems to be a slight connection with interaction
patterns, but it's very little to work with. On my part, I did provide
the first few ideas on how to achieve more Usable Software Design, and I
plan to explore this topic some more.
This doesn't mean I'm dismissing the idea of Software Habitability. One
the contrary, I am open to learning from the past, because I feel this
industry reinvents the wheel every 5 years or so. If anyone can point me
to more materials related to it, please do.