6 ms·
I'm sure you're doing something right. If you have users you're definately doing something right. But do you really think that the only way to make one group o
by fauigerzigerk 17y ago
I'm sure you're doing something right. If you have users you're definately doing something right.
But do you really think that the only way to make one group of users happy is to simply exclude functionality that would make another group of users happy? Is this an unsolvable problem in your opinion?
I tend to agree with TomOfTTB that it is a UI challenge that can be met.
- ahoyhere 17y agoIt's not about excluding features to make people happy, it's about designing something right from the ground up. I didn't take a mental image of a time tracking app and then remove stuff. I started from scratch. Different groups of people have different use cases, and different needs. It's a fallacy to think you can design one thing for all people. It compromises your vision. Make sense? And yes, by the way, there are lots of things we are able to do with Freckle because we have decided paths that we do not want to tread. For example, project creation is always on-the-fly. It's so elegant I could cry. But if we added permission restrictions, based on who could create projects, that would take away the elegance, and add confusion. In the end, our approach -- which is awesome for our desired audience -- would be totally compromised by the additional error-checking and rigamarole if we were to add this as a feature. Thus, we won't do it. There are plenty of people who don't need or want that, who are our potential audience. And people who do need it, won't like the other assumptions our app makes. They will be better served by more traditional products. To my mind, this is win/win/win.
- berntb 17y agoLet me limit this to web applications. To me this discussion sounds like an argument for user controlled scripting languages in web applications. This is needed since web applications which use lots of Javascript can't be automated by normal web scraping libraries with no Javascript/DOM emulators (they support cookies, etc so they can do sessions etc). Something like the classic Applescript, for user control. (Or maybe the latest web frameworks already have that?) Edit: Reformulated sentence for clarity. Edit 2: I think the plugins for Firefox etc are too hard to write? Maybe you could add scripting languages to them?
- ahoyhere 17y agoThere are a few problems with this. 1. No one will do it. 2. Even people who do know how to program have a special aversion to JavaScript, especially. 3. Almost no one is equipped (or willing to invest the time/effort) to analyze their work and come up with a process that is best for them. A typical person is about as self-aware as a box of rocks. Even particularly smart, savvy, successful people. It takes a lot of work to get real insight out of them in terms of work processes. And impossible to get them to generate novel ideas for solving those problems. More importantly, to design great software you have to understand not just business processes, but software itself, and the human animal (psychology, sociology). That is an extraordinary amount of extra crap to expect somebody to do, when they just want to get their work done. This is born out wherever you see "lay people" creating their own solutions. Ever worked in an organization that powers itself on Excel? It's not only not pretty in a technical sense, but they never, ever, ever do a good job, even within the constraints of what is possible with Excel. And they also never think to question if there could be a better way. So, that's what people like me are FOR. All this crap happens to be my passion.
- berntb 17y agoYou and 'toadpipe' are probably correct. I'll argue the point anyway, to see if it could be made to work: Consider that the scripts would run on the web server. That means they would be published and used by other users... (After a bit of analysis, so they don't do anything destructive.) And charge money from users that really want their scripts to be private. Just make certain that there is a script language defined for the web app framework -- and an extensible object model for the local web site's data. (Again, Applescript. But not that syntax!)