This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: Eckel: Rethinking weblogging (and everything else)
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
Because elegance is difficult and time to market is crucial, many have come to believe that the former should be sacrificed for the latter. It's hard to argue against this. The rabbits that rush a half-working piece of garbage to market are usually the ones that are wildly successful, whereas the careful tortoises are never noticed.
Link. Eckel's weblog posts are always interesting. More:
Part of what I'm trying to convey in this article is the subtle threshold beyond which a thing is just a bit too complicated to absorb into your toolbox, along with all the other tools. The subtlety is that it's possible to use that tool, but beyond a certain vague point it's just a little bit too hard to put down and then easily pick up again later, and for me, that's the crux not whether it's usable at all, but how easy is it to put down and pick up?