Dariusz on Software

Methods and Tools

About This Site

Software development stuff


Entries from July 2015.


Ttitle: Twitter.com performance analysis done over 5 years

A long time has passed since I've started to measure some of "mainstream" websites. One of them is twitter.com.

Probably you remember old days when everyone blamed it for general slowness and huge performance problems.

This is the past now! As you can see from the graph twitter.com staff did their homework quite well in 2013. Since then they respond almost instantly (~100% of requests under one second):

That's a great score!

A link to full measurement report is available there (measured by site-uptime.net).

Someone might ask: why do bother that ~50% of requests served under 2 seconds? I think you cannot just ignore such performance problems.

Even if you don't handle them with high priority you have to measure (to know if it's not going to be worse for example). The knowledge is crucial for making optimization decisions in the future.

Tags: monitoring.
Wed, 08 Jul 2015 21:47:52 +0000

Nobody likes it. They are boring duty you ought to do after a meeting. What? "Minutes", of course.

By "minutes" I mean: a note from the meeting (or a telco) that should be sent after a call to all participants involved in order to remind what has been agreed on the meeting and what action items are specified and who is responsible for implementation.

boring-meetingIs there a way to make this very useful tool more effective? The answer is: YES!

First of all: lets enumerate expected properties of those "minutes":

  • easy to write
  • do not skip/forget anything important
  • allow to control if every action item has an assignee

Having above properties in mind I've implemented the following process using an online documents solution (Google Docs, to be specific):

  • I send proposed agenda as online document link to every participants and I allow them to extend it if needed
  • During the call I (or any participant) add action items and responsible persons to the document. Remember: concurrent editing is fun!
  • A copy the document is sent after the call in the same e-mail thread as invitation
  • And now: the previous step delivers your team "minutes"! Voila!

Everyone has R/W access to the document and this is the gag - you can delegate your job to add notes and complete document (including completeness checks) to meeting participants. They enjoy that as they're involved in the meeting flow and the output directly. Nobody is bored.

To speed things up you can add timestamp to each agenda item. Such meeting could never miss allocated time!

Implementation tracking is also easy - you can add ticket tracking ID (Jira, Redmine) to the minutes and assign appropriately.

Happy (not boring) meetings! :-)

Tags: business.


Created by Chronicle v3.5