TechHuddle is participating in the Careers Day at Interpred World Trade Centre Sofia on 14th Oct 2015 from 10:00 – 18:00. See you there!
OnTheMarket.com officially launched today with the goal of giving Estate Agents and consumers a credible alternative to Rightmove and Zoopla.
OnTheMarket.com’s Android phone and tablet apps also went live tonight. Search the Google Play store for OnTheMarket or click OnTheMarket.com Android app
The OnTheMarket iPhone and iPad app’s should be live shortly once they have passed the Apple App Store process.
Richard Yeo the CEO of TechHuddle was nominated by Robert Yeo of Morgan Stanley to take the ALS Ice Bucket Challenge. In this video Richard Yeo CEO of TechHuddle takes the ALS Ice Bucket Challenge multiple times and nominates
- Sir Stelios
- Robert Ellis the CEO of easyProperty
- Paul Ellerbeck the CTO of easyProperty
- Juha Koski the CEO of MadBid
- Richard Brindly the CTO of MadBid
- Joe Slavin former CEO of fish4
- Mark Milner former CEO of TDPG (The Digital Property Group)
- Andrew McGreggor the CEO of Order Dynamics (previously eCommera)
- Michael Ross the Chief Scientist of Order Dynamics
- Warren Cowan the CEO of Greenlight
- Andreas Pouros the COO of Greenlight
- Kevin Murray of Greenlight
- Ivailo Radev MD of TechHuddle Bulgaria
Andreas Pouros and I launched http://www.acceleratr.co today.
acceleratr.co is a London-based, high performance start-up accelerator providing start-ups with everything they need to get to a major funding round – capital, strategy, mentoring, resources, subsidised office space and contacts.
Not all Content Delivery Networks (CDN) request pipeline (also known as Pre Caching System).
Request pipelining is a technique to reduce the number of origin hits for simultaneous requests. If there are three simultaneous requests for a non cached item then one server will make the request to the origin and the other two servers will wait until the server making its request has completed and then return the cached content.
The impact of having no request pipelining depends on the nature of what your origin is serving. If origin hits are particularly heavy CPU/IO wise and/or you have flash traffic (large amount in very short window) then you will definitely want your CDN to request pipeline.
It’s not something CDN (Content Delivery Network) providers broadcast but not all CDNs cache an object on first request. Their rationale being they don’t want to fill their cache with items that are not frequently requested.
The impact of don’t cache on first request really depends on the nature of what your origin is serving. If origin hits are particularly heavy CPU/IO wise and/or you have flash traffic (large amount in very short window) then you will definitely want your CDN to cache on first request.
The good news is many CDNs can turn this off so first requests are cached.
At long last Amazon have introduced rudimentary CloudFront reporting and ELB logging.
No longer do you have to write scripts to download and process thousands of log files from S3 or use third party services to get basic CloudFront reports. Although if you need anything more advanced than these, which is quite likely, you will
- Number of Requests: show the number of HTTP or HTTPS requests served by edge locations in the selected region for the specified CloudFront distribution.
- Data Transferred: show the total amount of data transferred over HTTP or HTTPS from CloudFront
- Data Transferred from CloudFront Edge Locations to Your Users: This chart shows data transferred from CloudFront edge locations in the selected region to users, combining both HTTP and HTTPS usage.
- Data Transferred from CloudFront to Your Origin: This chart shows data transferred from CloudFront edge locations in the selected region to your origin for POST, PUT PATCH, OPTIONS, and DELETE methods, again combining both HTTP and HTTPS.
I often hear people say “offshore doesn’t work I need my people together”.
This is simply not true. Perhaps they are embarrassed to say they haven’t been able to make it work. I don’t think that is true either. I think it is just a case of they haven’t tried it but they probably have and haven’t even realised it.
Staff often work from home because they are not very well, waiting for plumbers, etc. Whilst at home they dial into meetings and/or conduct conversations with other people using telephone, Skype, Google Hangout, GotoMeeting, etc.
I know a company where their team lead is in Sofia and he manages a distributed development team across Sofia (Bulgaria), London (UK) and Newcastle (UK). I also know a company with developers in San Francisco (USA), Bath (UK), Kiev (Ukraine) and St Petersburg (Russia). They and many others find it works very well.
My personal preference is to divide projects into small self contained teams, e.g. < 5 people, so the communication overhead between people is reduced which results a small amount of team to team communication.
For example an eCommerce project could be split into 5 small teams UI designers (London), www UI developers (London), admin UI developers (Sofia), web services developers (Sofia), import / export developers (Sofia), etc. Should the import / export developers sit in a scrum meeting and listen to the UI developers whittle on about things effecting them and vice versa. No. It’s not a good use of their time.
Here is an example of what not to do
A meeting for 16 people regardless of whether face to face or distributed is going be long and energy sapping. Just look at their faces!
If you operate multiple locations it makes sense to invest a few hundred dollars in a large TV and a conference camera like this Logitech BCC950 Conference Camera in each location.
Offshore teams and distributed teams work and there is a new generation of people for whom this is the norm.
You should embrace talent no matter where it is in the world.