Both Sides of the Table
MAY 7, 2011
Sometime around 2003/04 my technology team turned me on to “Spolsky on Software&# a periodic newsletter served up blog style from Joel Spolsky of FogCreek Software, a maker of bug-tracking software. But I loved reading them and so did my team. Defensibility in Software. His Tenure at Microsoft.
ConversionXL
NOVEMBER 11, 2015
A/B Tasty is yet another testing tool designed for the masses, this one hailing from France. Vlad Malik from www.goodui.org gave a review of A/B Tasty: Vlad Malik : “The things I like about ABTasty I like a lot. Can offer much better data due to true user basis then tools like GO or Optimizely. It’s not cheap.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. I dont think so.
mashable.com
MAY 9, 2011
With development teams often based around the world, being the center of communication and progress can either lead to a tremendously successful strategy or a bottleneck that can slow down an entire company. Organization and Execution Your new CTO should be able to handle your development team so that projects run along smoothly.
mashable.com
OCTOBER 27, 2010
Here, developers and dev shops are organized by vertical so you can find a shop that has expertise in the kind of app you want to build. As for web and social apps, for some platforms, you’ll want to have a special development team. Last, you will want to see whether your potential hire has technical chops.
Startup Lessons Learned
OCTOBER 5, 2008
I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said.
Startup Lessons Learned
OCTOBER 20, 2008
They just assumed it was the way software companies worked. In teams that follow the "pick two" agenda, which two has to be resolved via a power play. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. I couldnt see that we were managing to pick even one.
Expert insights. Personalized for you.
285 
Let's personalize your content