Live data from Hacker News

Joel Spolsky Launches Trello - Organize Anything Together

trello.com

161–170 of 292 posts

Re: Joel Spolsky Launches Trello - Organize Anything Together

#162
From the js source -

This application uses other third-party javascript components distributed under appropriate licenses. For more information, see the following files at http://trello.com/js/lib/

backbone.js,

highcharts.js,

json2.js,

markdown.js,

socket.io.js,

underscore.js,

...apart from jquery/jquery-ui.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#163
post #160

So I honestly don't get it. Is this a poor mans bug tracker? A possible re-invention of a bug tracker? (something wacky and different version of a bug tracker to see if it sticks?) I have seen people mention project management a bunch, but the view really isn't about viewing what people are doing. In fact items that don't have people assigned to them still show up. The 10 foot view isn't even that good as they all sq…

Well, to fuel your fire, Fog Creek also happens to make a bug tracker, http://www.fogcreek.com/fogbugz/

Re: Joel Spolsky Launches Trello - Organize Anything Together

#164
Mostly a nitpick, but it'd be nice if the home page had a little text for those of us who browse safely and are wondering what it is at a glance or why we should care enough (besides the Spolsky reference) to enable scripting.

Anyway, it's pretty slick with the UI. I'm going to check it out for tasking myself, and if I like it see how it works for a school project with others.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#166
post #104

It definitely has all the trappings of a Fog Creek app: - The overall UI: built by programmers who dabble in design - A seven(!) minute video about how _simple_ it is to use. It's easy! Instead of just raising your hand, you mark a light on the corresponding tote board, which informs your manager that you need more information. I hate to be contrarian, but there are many other apps out there that solve this problem m…

OK, but can you give us some specific improvements you'd make? Or parts of the design that you'd change?

I would say change the colors. They're as fresh as Windows software from the 90's.

The typography is rather ugly and makes the UI look stuffed (so maybe tuning the font, font-weights and font-sizes would help)

Overall the UI looks stuffed and heavy and colors make it seem depressing. The actual task something like two words, but about half of the space is occupied with heavy indicators of comments or other UI elements, so you tend to focus on the UI and not the actual information.

I guess the UI works in the basic level, but it's not that well or tastefully executed, and definitely looks like coder design.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#167
Few things I am really digging from a design perspective -

1) The slight tilt of an item in the process of doing a drag and drop of tasks

2) The modal boxes for adding invites, viewing task details etc.

3) The scrollbar on the right(Activity) pane. (Was digging around in the css, is this done in Javascript?)

Well done!

Re: Joel Spolsky Launches Trello - Organize Anything Together

#168
post #66

Joel, serious question, if you're listening. In the blog post, you mention that these teams are adopting the Lean Startup philosophy of ship early and ship often. Does that mean that you've softened on the "never ever write any code without a spec" dogma from "the Joel Test"? I've personally found that when you're doing tight iterations and continuous deployment, writing old-school spec documents feels, well, old-sch…

It's more complicated than that, and it's hard to answer here. Basically -- if you're building something big and complicated and you should know exactly how it's going to work, a big written spec really helps. If you're building something brand new, a startup, or a crazy idea that you need to test quickly and iterate, you should use lots of little specs. It's ok if the specs aren't so fancy... a detailed map of what…

As someone who can't draw a thing, there's a phenomenon I've noticed that might apply. Every time I need to draw something out, I try to hold it clearly in my head, where it looks so complete, but of course it never works. My suspicion is that instead of actually seeing the details of what I want to draw in my head, my brain has filled them in with "here be details," which makes for a nice mental image but that doesn't really play so well on paper.

I also think the same thing happens when we write software with loose mental maps. Our brains fill in the gaps with "yadda yadda yadda," to make it feel complete, but really there's nothing there at all.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#169
post #168
post #66

Earlier quoted context omitted.

It's more complicated than that, and it's hard to answer here. Basically -- if you're building something big and complicated and you should know exactly how it's going to work, a big written spec really helps. If you're building something brand new, a startup, or a crazy idea that you need to test quickly and iterate, you should use lots of little specs. It's ok if the specs aren't so fancy... a detailed map of what…

As someone who can't draw a thing, there's a phenomenon I've noticed that might apply. Every time I need to draw something out, I try to hold it clearly in my head, where it looks so complete, but of course it never works. My suspicion is that instead of actually seeing the details of what I want to draw in my head, my brain has filled them in with "here be details," which makes for a nice mental image but that doesn…

Isn't that why Balsamiq exists?
Post reply on HN