I have been writing some Javascript which reads data, creates the <table> HTML tags and then does conditional formatting of given numbers (based on five equal sized bins). Let me know if you find any bugs.




Here is an update on the rail delay figures. I have collected more than a week now (12 days).

Reading is still the worst station with 65% punctuality. It also had 8 of the 10 worst days. Clapham Junction and Putney are second and third worst close to 80% punctuality. Putney has the highest % of small delays. Waterloo has most cancellations. Best station is Charing Cross.

8 and 9 am are the worst times to travel during the week, Saturday is the best day to travel.

table4 table5 table6 table7


  • If the company has very ambitious plans, they have a problem with fulfilling them.
  • If they have a lot of new staff, they have possibly a retention problem.
  • If hiring you is a scoop, you won’t be learning from them.
  • If they answer emails outside working hours, you are facing long hours.
  • If you think the interview was too easy, there will be a catch later.
  • If they have a lot of contractors, they will have a problem with commitment.
  • if their HR are delaying things, they are very bureaucratic/slow or political.

(based on own and other people’s experience)

I have been scraping real time departure board train times from the ten busiest train stations (plus Reading and my own Putney). I am calling the departure board every five minutes and then keep the last status.

Punctuality varies between 60% (Reading) and 98% (Charing X). Putney has the highest rate of small delays (10% 1-2 minutes). So if you see any high 90% stats by train operators, you better question them.

Looking at hours, excluding night 8am is the worst time to travel. 15pm is the best time to travel, but who does?

Weekdays don’t see much variation, but this might change as I collect more data (have 3.5 days now).