The could be anywhere.
Why not to (always) trust recruiters’ advice.
A piece of advice and “wisdom” I received from a certain nameless Director of Major Players in 2000 (now departed).
“Go back to college. Learn (formerly Macromedia, now Adobe) Lingo. Learn how to create CD-ROMs in Director.”
Fortunately, I didn’t take heed of this, was aware of an upcoming language called PHP and the CD-ROM has gone the way of the dinosaur.
I hate to quote Fleetwood Mac but sometimes it pays to “go your own way”.
This interesting post on Ask HN listed a number of things tried and tested at Twilio, a Bay Area startup offering an API for making/receiving telephone calls and sending/receiving text messages:
Read more Tips and Tricks to Save Money While Running a Startup…
What project artifacts do your digital web development projects typically generate? Here are some of the basics I deal with:
What’s your company’s earnings per employee? Take a look at this incredible statistic from Google (part of a CNBC article on the S&P 500′s most lean companies).
Software & Services
Industry Leader: Google Inc. (GOOG)
Annual revenue per employee: $1,093,892
Annual profit per employee: $214,768
Employees: 20,164
[Link]
Here is the full article:
The S&P 500′s Leanest Companies
What project controls does a digital project manager use and maintain? Here is a list of project documents and controls which I’ve used in my line of work.
The all-governing document is typically the Statement of Work (SOW). This forms a binding agreement between the service company (agency) and the client. These should be written in a plain English style shunning technical terms and buzzwords. It acts as the overall framework for how the project hangs together, when things happen and what exactly they are.
The SOW document includes:
Recruiters that don’t take no for an answer are frustrating. Especially when you kindly ask them to remove your details from their databases.
Here are a few of the guilty parties than constantly email with jobs that are not relevant. Notice how most of them come from one company:
Sara Clark s.clark@timothyjamesconsulting.com
Ben Gill b.gill@timothyjamesconsulting.com
Richard Haggarty richard@timothyjamesconsulting.com
Rory Mullins r.mullins@timothyjamesconsulting.com
Christine Christodoulou christine@timothyjamesconsulting.com
Dan Wardle d.wardle@timothyjamesconsulting.com
Wakeford, Andrew andrew.Wakeford@hays.com
Damian Chana dchana@rethink-recruitment.com
[Update 04/04/2010]
Paul Fraser paul.fraser@ecrmpeople.com
[Update 15/04/2010]
Katie Lennon katie@ecomrecruitment.com
[Update 23/04/2010]
Lucy Haslam lhaslam@itrecsolutions.co.uk
[Update 11/05/2010]
Jonathan Swithinbank j.swithinbank@timothyjamesconsulting.com
Summary of the strategy of building low-burn-rate startups, i.e. capital efficient and generally frugal. By taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste.
Will the Google Apps team’s announcement on 29 January 2010 be the tipping point for the end of widespread support of Microsoft Internet Explorer 6?
In order to continue to improve our products and deliver more sophisticated features and performance, we are harnessing some of the latest improvements in web browser technology. This includes faster JavaScript processing and new standards like HTML5. As a result, over the course of 2010, we will be phasing out support for Microsoft Internet Explorer 6.0 as well as other older browsers that are not supported by their own manufacturers.
We plan to begin phasing out support of these older browsers on the Google Docs suite and the Google Sites editor on March 1, 2010. After that point, certain functionality within these applications may have higher latency and may not work correctly in these older browsers. Later in 2010, we will start to phase out support for these browsers for Google Mail and Google Calendar.
Google Apps will continue to support Internet Explorer 7.0 and above, Firefox 3.0 and above, Google Chrome 4.0 and above, and Safari 3.0 and above.
- The Google Apps Team
This will come as music to the ears of long-suffering interface developers who have had to struggle with numerous CSS hacks, the lack of support for alpha transparency in PNG images and security problems – to support a nine-year old product reluctantly supported by Microsoft.
Roll on 01 March 2010!
In searching for a simple, open source (and free) Subversion client for OS X, I came across RapidSVN. I’m using RapidSVN, a multi-platform GUI front-end for the Subversion revision system.
RapidSVN is an open-source client for Windows, Linux, OS X and other *nixes. It’s simple and functional but requires third-party tools for functionality such as visual Diffs. Its written in C++ and executes native code, so it’s the fastest cross-platform client.
While the user interface is not as nice as Versions, it’s lightweight feel and zero cost fits my current needs.
[Link]
RapidSVN