TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How We Make Trello

290 点作者 spolsky大约 11 年前

21 条评论

edwinnathaniel大约 11 年前
I&#x27;m more interested to know the actual technical details of the build and testing process than the &quot;Task-List&quot; software development based approach because that can be done by any software project management tools (even JIRA).<p>What&#x27;s missing in this article is the whole Continuous Delivery technical aspect of it.<p>What do you guys use to build the NodeJS app?<p>What do you guys use to test the NodeJS app?<p>What do you guys use to check the code coverage of the NodeJS app?<p>What do you guys use to test the front-end?<p>What is the automated testing strategy?<p>How do you store artifacts of builds, schema migration (if using RDBMS) or handle different model versions, how do you rollback (what&#x27;s the rollback strategy)?
评论 #7393087 未加载
评论 #7397666 未加载
评论 #7393069 未加载
basicallydan大约 11 年前
Fog Creek are the _kings and queens_ of dogfooding. Spolsky, you sure have nurtured a group of very loyal team players. I applaud you all. It must be really nice to work at a place where the love of the process and the product are both so strong.<p>In my opinion if there&#x27;s one thing a reader should take away from this it should be that Single Page Apps and separation of server and client are The. Best. Thing. Ever. From the start, design your system this way.<p>Good post, and an entertaining read.
评论 #7392693 未加载
评论 #7393778 未加载
评论 #7394191 未加载
badman_ting大约 11 年前
It&#x27;s almost comical how nobody at my company would ever take a project this seriously. Good for them, Trello is awesome.
评论 #7392990 未加载
steveklabnik大约 11 年前
&gt; &gt; The Trello API is well-written, has no bugs, and is totally rock solid. Or at &gt; least it doesn&#x27;t change very often. That means we can put out new &gt; clients all the time without having to update the API. In fact, we can have &gt; multiple versions of the website out at any given time.]<p>A very counter-intuitive result: most people would not consider a stable API to let you iterate quickly!
评论 #7395098 未加载
allcentury大约 11 年前
I&#x27;ve used Trello &amp; FogBugz over the years and we&#x27;ve even modeled some of our software after some of the practices they&#x27;ve written about. Amazing stuff!
sidcool大约 11 年前
So they create a new branch for each fix? And all developers are supposed to merge in their branch every few hours or so? Isn&#x27;t it a bit of a drag?
评论 #7393090 未加载
评论 #7393191 未加载
评论 #7395513 未加载
评论 #7393074 未加载
评论 #7393060 未加载
评论 #7393279 未加载
评论 #7394315 未加载
评论 #7393291 未加载
评论 #7394275 未加载
评论 #7393892 未加载
评论 #7393057 未加载
trustfundbaby大约 11 年前
What I&#x27;m interested in is the mechanics behind how they know were to send a user based on their channel (beta&#x2F;stable&#x2F;alpha). We wanted to do something like this, but we couldn&#x27;t figure out how to route users to the right app server either using AWS ELBs or nginx proxying ... admittedly we didn&#x27;t really spend a lot of time thinking about it though.
评论 #7399404 未加载
jamessocol大约 11 年前
I&#x27;d love to hear—maybe I missed another blog post—why they went with the single release manager, where only one person can merge and deploy. What happens if Doug is sick or on vacation? Or even just in a meeting? What is a typical amount of time for a change to sit in &quot;ready for merge&quot; or merged but not deployed?
评论 #7393271 未加载
评论 #7394294 未加载
评论 #7393406 未加载
评论 #7393246 未加载
chrismorgan大约 11 年前
I like the lighthearted approach to cross-selling in the article. ☺
jcastro大约 11 年前
Are they on AWS or hosting your own hardware? What OS?
评论 #7393726 未加载
giulianob大约 11 年前
How difficult is it to make the backend work with both new features and old features at the same time?
评论 #7393292 未加载
评论 #7393261 未加载
mikegioia大约 11 年前
Does anyone know how the server determines which channel the client should be using? Are they doing this check at the apache&#x2F;nginx level, or on the server right after the user is authenticated, and before the client code is sent?
评论 #7392938 未加载
评论 #7392799 未加载
laurenstill大约 11 年前
This is great and all, but I really wish I knew why they won&#x27;t make the audit logs accessible to users. If someone has a hack for this, I&#x27;m all ears.<p>Need it for compliance documentation.
banachtarski大约 11 年前
&gt; The Trello API is well-written, has no bugs, and is totally rock solid.<p>The no bugs claim indicates to me this wasn&#x27;t written by a technical person. Or at least, not very technical.
评论 #7393995 未加载
评论 #7394010 未加载
jw2013大约 11 年前
These tech intros are pretty cool, yet can I ask how does the team acquire users? That seems to be harder than the tech challenges for Trello IMHO.
somid3大约 11 年前
I don&#x27;t get it. Why is having an API in the backend so that many clients can use it a big deal?
评论 #7394375 未加载
kalnuezis大约 11 年前
Anybody using FogBugz and Kiln from Fog Creek? Both seem to be a bit outdated...
评论 #7397597 未加载
nevster大约 11 年前
I&#x27;d like to be able to write like this. It made me LOL.
aravindb大约 11 年前
Trello using Trello,(Inception) awesome!
takacsv大约 11 年前
Trello is using Trello to develop Trello. So meta :)
评论 #7394673 未加载
haymills大约 11 年前
So interesting!