241–250 of 292 posts
Oh you US people, I get internal server error when I try to activate account which contains ä character in the full name field... And when trying to change my name from the account page: Display Name can only contain letters, numbers, spaces, or the following characters: -_'.@+ Does this affect the Google account login also, it doesn't work for me either.
Earlier quoted context omitted.
Thanks for the response. I see where you're going from. I only brought it up because my development organization would fail that part of the Joel Test, where many totally dysfunctional organizations I have worked with would pass. Doesn't pass my initial smell test. It's easy to see someone jumping in and writing and re-writing code when they haven't thought it through as wasteful. People have a harder time seeing tha…
Rewriting the spec for a feature takes a lot less time than rewriting the code.
I think Joel's comment of "thinking in a disciplined way before typing code" hits the nail on the head. Different people can think in disciplined ways before typing code. Some people do that by writing specs, other people do that by writing tests, others do it at the whiteboard. There's no one right way to do it.
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…
Practical suggestion that has worked for me is to use graph paper. Having the grid to align and separate things makes a huge difference. My non-graph-paper sketches look like something from a lunatic's diary in comparison.
I would be eager to try a whiteboard with a consistent faint grid to it.
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…
Hey Joel, this is terrific, and what's on my mind for quite a long time. None of the present kanban implementations are good, and I've been thinking of using node+socket+backbone to build one in my spare time. I've also downloaded the iPhone version but it lacks a lot of polish. TL;DR I like trello, and could I join your fabulous team?
It would be nice if it was mentioned somewhere.
Earlier quoted context omitted.
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.
"Holy shit. This is EXACTLY what I was envisioning. This is freaking AWESOME. Since the data is stored outside of [our company], security might have a conniption fit if they found out that we were using this for managing internal project data.
I'm certain a tool like this could be highly useful to many other teams..."
Can Trello address this concern?
Earlier quoted context omitted.
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'
Earlier quoted context omitted.
Harumph, grouchy pants. Well, one of the designer/UI peeps at 37signals liked it! so there! http://twitter.com/#!/rjs/status/113751685091950592 But in typical usenet style, I will engage each of your points directly and anxiously await your rebuttal. - "The UI stinks." I think this is the number one thing we've gotten praise for. It's hard to please everyone, but overwhelmingly people have told us the opposite of wha…
No rebuttal here! Thanks very much for the clarification. If you're getting praise for the UI, go for it. I think my biggest issue is the relatively narrow nature of the design. The cards, the columns, etc. Example: http://cl.ly/1i01452a3l0V1X3K3N1f -- line breaks like that are difficult on the eyeballs. Little things, like using color-coded labels for organization sound good on paper, but are very tedious in practic…
RE: onboarding, we want to do something like we did with webputty.net using Optimizely's Guider https://github.com/jeff-optimizely/Guiders-JS