marcog1

6 ms·

1.
by marcog1 2y ago
This might not help you, but it might help someone earlier in their career. I was born, raised and studied in South Africa. Living costs and salaries are cheaper. I worked in California. Instead of living a lavish lifestyle, I saved. In hin
2.
by marcog1 10y ago
You want to replicate as much as possible, but if we ran canary on the same machines we could have testing code bring down production. That's bad.
3.
by marcog1 10y ago
We actually have a traffic replica (dark client) setup for the new webserver architecture we are gradually migrating to. It likely would have caught this before deploying to users.
4.
by marcog1 10y ago
We have very comprehensive dashboards. Getting the perfect ones that help in all cases, while not being information overload (the problem here) and being discoverable is a hard, iterative process.
5.
by marcog1 10y ago
We have talked about it. It is unlikely to helped with an event like this, and I don't recall an event where it would have. It also has the downside of extending our deployment cycle by a lot. Notably, we do run a canary internally, a
6.
by marcog1 10y ago
When you do daily deployments, you can't QA every one much. You rely on automated tests and Internal users using the new code for a couple hours before the deployment. We were unlucky in this case with the number of bad releases. Each
7.
by marcog1 10y ago
We will never out individuals. The person who committed the code was innocent. We got him a fun gift as a sort of joke.
8.
by marcog1 10y ago
Every response from our users so far has been thanking is for the transparency. It also represents our internal transparency, and that has a real impact on recruiting.
9.
by marcog1 10y ago
We do, but it didn't help given the cause of the high cpu was our logging infrastructure (Amazon Kinesis) being overloaded by the webservers.
10.
by marcog1 10y ago
Correct. We don't roll out during peak load either.
11.
by marcog1 10y ago
This was the first time we had this class of outage. Many things were in a very bad state, and many of these symptoms were more familiar to us. So we spent time ruling them out before realising webserver CPU was closer to the root cause tha
12.
Full technical details on Asana's worst outage(blog.asana.com)
77 points by marcog1 10y ago|62 comments
13.
by marcog1 10y ago
I work at Asana. There's no way we'll drop our free plan. It's too fundamental to our sales model. We are, however, thinking a lot more actively about what features to make premium. Largely new features we haven't releas
14.
by marcog1 10y ago
Perf is our #1 priority right now. We've had a big team tackle the fundamentals for the last two years, and we're rolling things out in the coming months. I'm personally leading the team that's rebuilding our API on top
15.
by marcog1 10y ago
I think it requires a company email? I can't recall. They also have a verification window, reviews don't post for a couple days.
16.
by marcog1 10y ago
That happened when someone noticed we were ranked #1 in the Bay Area and announced it to the company. Employees followed with more reviews.
17.
by marcog1 10y ago
Sam is investing personally, not YC.
18.
SwiftKey founder sold his shares for a bike(independent.co.uk)
3 points by marcog1 11y ago|1 comments
19.
George Lucas nearly wrote a perfect prequel trilogy. He just didn't notice(gamesradar.com)
11 points by marcog1 11y ago|1 comments
20.
by marcog1 11y ago
At Asana, we've been beta testing Kinesis Firehose. It's been quite convenient not having to manage much, and having the data end up in S3. We're also using Kinesis streams, and have a simple KCL app to pull from streams and
21.
Circling Ourselves: The Story Behind Asana’s Rebrand(medium.com)
10 points by marcog1 11y ago|3 comments
22.
by marcog1 11y ago
They likely get a good deal, but either way their content licensing costs are huge in comparison and make their Amazon bill a drop in the ocean.
23.
How to give advice to a teammate(blog.asana.com)
1 points by marcog1 12y ago|0 comments
24.
by marcog1 12y ago
We did long ago, but ditched that idea because we get to use the tools of JS and we realised that effectively using a DSL embedded in another language allows the developer to break the rules of the DSL.
25.
How to Build Stable, Accessible Data Infrastructure at a Startup(eng.asana.com)
8 points by marcog1 12y ago|0 comments
26.
by marcog1 12y ago
Asana engineer here. With such a large market size, we can scale the sales process to make it inexpensive. We only have a couple sales people. User operations, i.e. keeping customers, is larger but still in all less than 10.
27.
by marcog1 12y ago
That specific point was about Google. At Asana, we offer 1:1 and group Yoga sessions, and some people get together to meditate. A lot of people take it quite seriously, but it's in no way pushed on anyone.
28.
Building mindfulness into the Asana culture(medium.com)
53 points by marcog1 12y ago|19 comments
29.
A new day for Asana on iPhone and iPad(blog.asana.com)
5 points by marcog1 12y ago|0 comments
30.
by marcog1 12y ago
"Member companies receive a license when the patents are transferred out of the LOT group. That means that companies retain their right to enforce a patent so long as they retain ownership of it. However, as soon as it is sold, a licen

More ›