It's nice that we get more content usable on mobiles... but this shouldn't come at the expense of bad usability when on desktops.

There will always be some design and some testing. The intensity of both activities needs to be properly managed over time though.

Definitely a good principle to follow when designing APIs. Otherwise you make them less obvious and more dangerous to use.

Yes, definitely this. Plenty of reasons why it's important.

OK, this is a very bleak view... maybe a bit over the top I'm unsure. There seems to be some truth to it though.

Definitely this, the message is often coming across lacking nuance. TDD can help you towards good design, but it's not ensuring you'll have a good design.

This is indeed a good thing to hide dependencies behind interfaces when it makes sense.

Good reminder that we have no idea of the window size the user will have. It's in the context of web frontends here, but really it applies to desktop applications as well (we have a bit more control on the minimal size there but that's it).

Interesting look at module systems and what they entail. It's funny to see that most languages do things slightly differently in this area.

Black has been getting too much of a bad reputation in the last few years. This article makes a good job arguing for a more balanced view.

I always felt uneasy around this "law" as well. It's a good deconstruction of it and proposes proper alternatives. It's all about dependencies really.

Good set of advises for Python APIs. Some applies more generally though.

Interesting parallel taken with IKEA. Some of their principles translate to nice traits for software as well.

Interesting post, highlights why it's better when languages are designed in a more community fashion (make sure to read until the conclusion). At least in term of popularity it seems to help.

Clearly the UI design matters quite a bit in term of how addictive all those social network systems are. The alternative proposed here is interesting, I wish it'd be more widely implemented.

Interesting approach. I did quite some of that but without really putting it together like this. It's a nice way to explain it.

A nice pattern to know and master in my opinion. At least I turn to it on a regular basis.

This is indeed a phenomenon which I find odd. Everywhere you look, culture seems like it became homogeneous... I don't like this much, but indeed it means it's easy to be distinctive if you want to.

Nice historical perspective from Alan Kay about the MVC architecture pattern.

Nice refactoring and design pattern catalogs.