tag:blogger.com,1999:blog-6579772240267288367.post8348561540398617686..comments2023-06-05T08:45:12.716-04:00Comments on kwblog: To Empower or RestrictKevin Berridgehttp://www.blogger.com/profile/13759114853595462455noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6579772240267288367.post-91902521526535585542008-03-10T11:54:00.000-04:002008-03-10T11:54:00.000-04:00I agreeI agreeBenjamin P Leehttps://www.blogger.com/profile/15089639187841179363noreply@blogger.comtag:blogger.com,1999:blog-6579772240267288367.post-17514453602718043872008-03-08T18:26:00.000-05:002008-03-08T18:26:00.000-05:00If we're only talking about design of end user sys...If we're only talking about design of end user systems, I agree with you, its clearly important to know the user and understand what they need. I still firmly believe the "empowering mindset" is important to doing this correctly.<BR/><BR/>Even still, you don't want a "dumbed down" interface. You want one that does exactly what you want in the simplest way. But as soon as it doesn't do what you want, you'll call it crap. If you can configure it to do what you want, then it's flexible, and has empowered you to change it. I think you'll agree that's pretty unusual in most run of the mill software though.<BR/><BR/>This whole idea becomes even more important when you look at API designs and "standards." Primarily because those are tools or practices you use to build something else. If they only allow you to build one type of thing, and you need to build another but *slightly* different thing... You wont be happy.Kevin Berridgehttps://www.blogger.com/profile/13759114853595462455noreply@blogger.comtag:blogger.com,1999:blog-6579772240267288367.post-26526461665373741812008-03-07T14:32:00.000-05:002008-03-07T14:32:00.000-05:00As soon as I started reading this, I thought of th...As soon as I started reading this, I thought of the push in the last couple years to "convention over configuration". <BR/><BR/>e.g. recent pushes in many Java framework designs, pushes toward DSLs, the allure of things like Rails and ActiveRecord (guess at what I want, your probably right, and I will tell you if your not).<BR/><BR/>As you said, its a fine line that must be made between designing for flexibility, forcing flexibility, and giving the majority of users what they need the majority of the time, without making them think too much.<BR/><BR/>Flexibility needs to be there, but I would much rather have a "dumbed down" interface that does what I want the bulk of the time and an easy one stop shop for all my configuration needs that can be as flexible and exact as needs be ... for those few times I need it.<BR/><BR/>The real problem is then really knowing your users and understanding what they need to do that majority of the time.Benjamin P Leehttps://www.blogger.com/profile/15089639187841179363noreply@blogger.com