In the interest of simplicity I've started work on simplifying the site. After almost two years working with the split dichotomy of article and blog posts I've come to the realization that it is stupid.

First, because this precludes the notion I've had for a while that neThing is meant to be a gateway of streams, where multiple sources, including the stuff generated from the site itself, feed the postMonster (the backend that handles these things).

Two, because its too complicated. What makes a blog post different than an article post? In reality nothing except a few bits than can be more than handled with a checkbox or two when creating a post.

So, now all posts are posts. They are still identified by where they originated from, such as Twitter, but otherwise blog posts are now fully converted into articles. Which means they have wiki discussion pages and histories. As far as the wiki bot is concerned it is an article and thus can be linked as such by name. Conflicts will arise and thus it will behoove me, and anyone else using neThing in the future, to mark master posts when multiple of them have the same name. The other posts would then use their POSTID as their permalink.

Also notice that the left slider menu is gone. Replaced by two much simpler archive boxes on the right side above the twitter panel. There is also an Archive page that can be accessed using the IDT logo menu up top. The first archive box is simple, it displays years, and then gives links to the months that had posts. The second archive box is a cloud of most tags.

That's all for now.

posted by dharh 5:16 PM Dec 2nd, 2009

I'm a big fan of simplicity. Not because I do not like complex things. The most beautiful things tend to be complex (people, galaxies, life, etc). I like simplicity because when applied correctly it leads to a fuller better experience.

Now that sounds a bit vague and also perhaps pompous. Yet it is also true that if you want to lead a less stress filled life, you should simplify your life. To me simplicity is not necessarily something you need to use in extreme.

For example, one way to simplify your life is instead of having a breadth of hobbies that you do not delve deep into, is to have a few hobbies that you do delve deep into. Or another example, instead of dramatically changing your lifestyle and diet to loose weight, change a little bit of various things like fruits and vegetables as snacks, taking the stairs more often than not, and more water than soda.

You may question whether these are really examples of simplicity, and you would be right. They are examples of a less extreme simplicity. Simplicity is not just about non-complexity. It is how you view the world and your interaction with it.

Here is another example, more near and dear to my own heart, software. These days we have come to the age of software bloat. After several iterations and revisions software becomes complex, unwieldy, and generally a pain to use. When we see software that is new and not riddled with tons of features and legacy we think of this software as refreshing.

Software caught up in feature creep tends towards not only being complex but also suffers from features that just plain don't work. If one of those features is a piece core of the software it can be rendered unusable. By focusing on a core set of features, simplifying the software, developers can better guarantee that the software does those core things very well.

But of course, just as you don't want to take the simple but extreme choice of going on a major diet (regardless of tendencies to fail anyway), you don't want software that can only do a very small set of things (even if it does them better than any other software).

For one thing, you'll never sell another version of your software that way, you will always have to add more and more features. You just do it at a slower pace and always keep an eye on not loosing to bloat and complexity. Two, users want features! Each and every user wants that one feature outside of the core set. They will be passionate about it and will tend to not use your software if there is another available even if that other software is more complex, with more bugs and bloat, but does do what they want.

So whats the solution to that second part? Perhaps the most complex feature a piece of software can have. Plugins, extensions, the ability to build macros or use the API. It is complex, but perhaps the simplest solution to the problem. Developers can focus on the core feature set, and the plugin system, while users can to their hearts content add any feature they want. You end up with a loyal base of users doing things with the software that even the developers never thought of.

So simplicity comes into play to solve a complexity problem, even if the solution itself is complex, though less complex than the problem itself was.

posted by dharh 2:47 AM Nov 17th, 2007

« Previous
Next »

2024: 1
2023: 4 2 1
2022: 5 3
2011: 5 3 1
2010: 12 9 7 1
2009: 12 11 8 5
2008: 12 5 4 3 2 1
2007: 12 11 10 9 8 7 6 5 4 3 2 1
2006: 12 11 10 9 8 7 6 5 4 3 2 1
2005: 12 10 7 6
2004: 10 9 6 5 4 3 2 1