Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Joel Spolsky Launches Trello - Organize Anything Together

trello.com

Post reply on HN
Print view View original

181–190 of 292 posts

Re: Joel Spolsky Launches Trello - Organize Anything Together

#181

Post by Vitaly »

spolsky wrote: post #14
Adaptive wrote: post #11

"vote" is a little weird... Everything about this is pretty intuitive except for that. It's only mentioned once on the summary/info page and in the welcome board after signup there should be a card that explains what voting is supposed to be, exactly. (besides just the ubiquitous like equivalent) I get the impression this started out with "voting" more prominent than it is now. But otherwise, this is really pretty ne…

Voting is actually a kind of "test of concept" of the idea of Trello Plugins which enhance Trello boards in interesting ways that not everyone necessarily uses

another feature request: import from pivotal tracker ;)

They have api.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#182

Post by thedufer »

city41 wrote: post #152
ellyagg wrote: post #137

You can actually view the live Trello Development board itself here: https://trello.com/board/trello-development/4d5ea62fd76aa113... I'm impressed they're so transparent with their development process.

It's mostly read-only, which you'd expect. Except I was surprised I was aloud to vote on their cards. I wonder what prompted that design decision.

Voting and commenting on public boards can be allowed for everyone, restricted to members, or turned off. We chose to leave it on because we like the aspect of simple, quick feedback on where things are going.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#183

Post by ianthehenry »

kylemathews wrote: post #151
tghw wrote: post #44

Earlier quoted context omitted.

Node, Backbone, CoffeeScript and MongoDB

Any reason you didn't use Socket.io? I noticed you're polling the server every few seconds for updates.

Trello does use Socket.io. If your browser supports websockets it will use them, but it will transparently fall back to polling if necessary.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#184

Post by Vitaly »

spolsky wrote: post #14
Adaptive wrote: post #11

"vote" is a little weird... Everything about this is pretty intuitive except for that. It's only mentioned once on the summary/info page and in the welcome board after signup there should be a card that explains what voting is supposed to be, exactly. (besides just the ubiquitous like equivalent) I get the impression this started out with "voting" more prominent than it is now. But otherwise, this is really pretty ne…

Voting is actually a kind of "test of concept" of the idea of Trello Plugins which enhance Trello boards in interesting ways that not everyone necessarily uses

another one: I should be able to add people from my organization to a board w/o going through the invitation confirmation process.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#185

Post by olavk »

spolsky wrote: post #66
MartinCron wrote: post #61

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…

I would really like a tool that would allow a spec and development notes to evolve just as a program evolves. It should start out with being as simple and low-overhead to use as a few post-it notes, but as the projects gets bigger it should be possible to impose structure, like categorize notes into functional spec or requirement, user stories etc, prioritize etc.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#186

Post by jagira »

icefox wrote: 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…

It is a simpler version of Pivotal Tracker.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#187

Post by Vitaly »

Joakal wrote: post #114
coffeemug wrote: post #111

Earlier quoted context omitted.

This product was designed to do a really good job helping people that have to get things done. Like any other software project, they must have had thousands of issues and limited resources to fix them, so they had to triage. With all due respect, the kinds of users that spoof their user agent to protect their privacy is probably fairly low on their priority list.

"Thousands of issues and limited resources to fix them"? They seem to have the resources to make it by design to block such user agents rather than advising users to upgrade.

yeah. and people will ignore the warning, continue to use the app and then complain that it doesn't work wasting everybody's time.

Re: Joel Spolsky Launches Trello - Organize Anything Together

#188

Post by Vitaly »

spolsky wrote: post #14
Adaptive wrote: post #11

"vote" is a little weird... Everything about this is pretty intuitive except for that. It's only mentioned once on the summary/info page and in the welcome board after signup there should be a card that explains what voting is supposed to be, exactly. (besides just the ubiquitous like equivalent) I get the impression this started out with "voting" more prominent than it is now. But otherwise, this is really pretty ne…

Voting is actually a kind of "test of concept" of the idea of Trello Plugins which enhance Trello boards in interesting ways that not everyone necessarily uses

since there is not feedback link I could find, I'll keep it here ;) :

- color labels are nice, but real text tags would be good too. lists are not enough. having a 'bugs' list doesn't help as soon as the bug moves to 'under work'

Re: Joel Spolsky Launches Trello - Organize Anything Together

#189

Post by StavrosK »

spolsky wrote: post #66
MartinCron wrote: post #61

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…

Sidenote: "Trello" is Greek for "crazy".

Re: Joel Spolsky Launches Trello - Organize Anything Together

#190

Post by vog »

olavk wrote: post #185
spolsky wrote: 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…

I would really like a tool that would allow a spec and development notes to evolve just as a program evolves. It should start out with being as simple and low-overhead to use as a few post-it notes, but as the projects gets bigger it should be possible to impose structure, like categorize notes into functional spec or requirement, user stories etc, prioritize etc.

I believe this is called literate programming (LP), which focuses on real documentation (in the broader sense, including specs, etc) rather than mere API docs. There are quite a lot of LP tools, many of them being independent from the language.

However, LP is not about tools. I've written LP programs that don't need any extra tool[1]. Rather, LP is about putting the documentation (spec, requirements, etc) at the highest level, and make the code a sublevel of that. This is very different from the traditional approaches where code is the highest level, or where documentation and code are separate.

[1] This worked because the build script was part of the literate program, too. Many "problems" with LP solve themselves if you just apply LP consequently.

Post reply on HN