Asana Engineering
eng.asana.com · Company blog · on HN since 2013
The engineering blog of Asana, covering its web stack, data infrastructure, TypeScript and node.js adoption, and hiring.
What HN saysHN commenters mostly cite its post on scaling Asana.com, which used Statamic, PHP, and AWS Elastic Beanstalk; one calls that costly for a simple static site.
15HN people shared it
7linked it in comments
13stories submitted
323story points
11 years agolast shared
2013people per year2026
Most-shared posts
- 1Scaling Asana.com7 people · 123 points · first shared 2014 · 43 comments on HN
- 2How to Build Stable, Accessible Data Infrastructure at a Startup2 people · 10 points · first shared 2014 · discussion on HN
- 3Why Asana Is Switching to TypeScript1 people · 101 points · first shared 2014 · 25 comments on HN
- 4Great Data: it's all in the delivery1 people · 48 points · first shared 2014 · discussion on HN
- 5Visualizing Collaboration at Asana1 people · 12 points · first shared 2014 · discussion on HN
- 6The Evolution of Asana’s Luna Framework1 people · 11 points · first shared 2015 · discussion on HN
- 7Making Asana, a JavaScript-heavy app, work in Internet Explorer1 people · 7 points · first shared 2013 · discussion on HN
- 8Asana switches to node.js1 people · 4 points · first shared 2013 · discussion on HN
- 9Testville and Beyond: Massive Parallel Testing at Asana1 people · 2 points · first shared 2014 · discussion on HN
- 10Sharding is Bitter Medicine1 people · 2 points · first shared 2015 · discussion on HN
- 11Adding Perfect Forward Secrecy to Asana1 people · 2 points · first shared 2013 · discussion on HN
- 12Sane Build Systems1 people · 1 points · first shared 2015 · discussion on HN
- 13Homepage1 people · first shared 2013
What HN people wrote when they linked it
awad · 2014-07-22
We just switched to Statamic and could not be happier. We modified it a bit so that our staging server has the admin panel enabled while still being backed by a git repo. Every save action commits and pushes to master, giving our non-technical folks a super convenient way to see their changes immediately without making a fatal mistake in production. Devs can then merge into prod after a quick review of the final changes.
Our design and workflow were largely inspired by the Asana team (http://eng.asana.com/2014/02/scaling-asana-com/) but we wanted to give our folks a fully featured admin panel instead of making them trudge through the Bitbucket/Github interface.
Edit: do not want to rain on the Pagekit parade at all...looks great so far.
aestoe · 2013-08-14
Asana: San Francisco: Full Time: http://eng.asana.com/
Technology: http://asana.com/luna
Full Job Description: SOFTWARE ENGINEER https://asana.com/jobs/software-engineer
If you join the team, you'll work with seasoned engineers from Google and Facebook, as well as the co-founder of Facebook. You will also take ownership of a large problems in a successful and small but growing startup.
Contact: [email protected]
tsurantino · 2015-07-07
Asana did something similar: https://eng.asana.com/2014/02/scaling-asana-com/
There is an argument to be made that a ubiquitous, developer-first system translates into more instant changes. Seeing changes quickly makes it easier to iterate, which is better over time than the initial investment to learn Markdown.
jnankin · 2014-08-12
See this Asana post on how they do it: http://eng.asana.com/2014/02/scaling-asana-com/
This still requires Statamic, PHP, and AWS Elastic Beanstalk. That would appear to be expensive for just a simple static site.
barryhand · 2014-04-26
Depending on tech capability, Statamic is a good option http://statamic.com/
The team at Asana have used it to scale as we ll http://eng.asana.com/2014/02/scaling-asana-com/
bri3d · 2014-02-14
Ties in perfectly with the Git + file-based CMS approach as used by (one of many examples) Asana: http://eng.asana.com/2014/02/scaling-asana-com/ .
Cool feature!
inthewoods · 2014-02-14
This blog post from Asana is proving inspirational for my team:
http://eng.asana.com/2014/02/scaling-asana-com/
http://statamic.com/ is the CMS and it provides a nice interface for content owners - although Asana uses the online Github interface for editing content.