chucklarge
We do have other contained infrastructure that is written in some other languages like go and scala.
You should also run an ongoing A/A test across your site or app to have confidence your bucketing, data pipeline, stats tests and effect on metrics is working as expected over time.
Kellan might have a rule to not build a CMS but we certainly have built one to manage help page content and other knowledge base pages. That content is largely managed by our support staff.
I wrote the current tool but it is actively being replaced. We chose to to roll our own since we'd have to do some work to integrate a third party tool into our database architecture and authentication system. The tool is heavily integrated into other internal tooling and has specific workflows that also make using an existing tool challenging.
The About page content is largely static, aside from the staff photos mentioned in the above post.
On the other hand, I like the idea of less and more generic constructs that can be adapted to achieve some need. Specialized tags like dd, address, details, summary, code, blockquote, etc just seem superfluous.
I used to use LaTeX but couldn't figure out how to style it exactly as i needed.
If you do use LaTeX, use the \LaTeX function.
Mctop - memcache top; new tool from etsy
John Allspaw explaining the Etsy way to its community.
The The Grammar of Graphics (Statistics and Computing) by Leland Wilkinson is also great, though more focused on building graphing systems. I believe it is the inspiration for a lot of d3.js http://www.amazon.com/The-Grammar-Graphics-Statistics-Comput...
http://www.perceptualedge.com/articles/Whitepapers/Dashboard... http://www.perceptualedge.com/articles/Whitepapers/Common_Pi...
The author also has written a great book on dashboard design.
Operations dashboards are essential for any (tech?) company.
Business dashboards are another beast all together.
MW has obviously been successful at a blogging platform and service (maybe other stuff, don't know his full history). My point about the Ford quote is that maybe he has a good vision for how his service should be run.
There is always going to be tension between the producers of a service and the consumers of that service. Neither could exist without the other, but I tend to feel that the exceptional people who have succeeded where others have failed should be given more credit.
I don't use Wordpress. I am on Facebook, do I think they care how their site should work? Why should they care what my opinion is? Because i am a user, I get to complain and get my way?
This attitude that users dictate how products and sites should function only brings to mind the Henry Ford quote in the Steve Jobs book. If Ford had asked people what they wanted, they would have asked for a faster horse.
Apple has made a very successful business out of not building faster horses. If you want it your way, start your own business.
I think the real pain comes when there are problems. How do i unfuck what i just did?. You're getting stressed out, there are people waiting on you to get your commits in. I had my flow down with svn, but now what do i do? Compound that with 100 engineers experiencing that on some level as we transitioned, it was trying.
It's true of changing any tool or workflow, though. You rely on muscle memory or run on auto-pilot and suddenly you don't know what to expect from your day.