Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Do you fix bugs before writing code? Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. They share a common language, culture, and coding style.

Software Review 68

Software Review Software Hiring San Francisco 68

Cracking the Code

JANUARY 16, 2012

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Cracking The Code on Facebook. software. (10). ► 2009. (9). Software 2.0: Cracking the SMB code. Monday, January 16, 2012. BlablaCar - Travel Revolution.

Software Review 95

Software Review Europe Technical Review Spain 95

Cracking the Code

FEBRUARY 23, 2011

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. and (2) their leadership position in multi-billion dollar markets will likely make them dominant players in the software landscape, even though they are still small today (SuccessFactors $2.5B

Software Review 101

Software Review Technical Review Valuation Europe 101

Software By Rob

NOVEMBER 16, 2009

Business of Software is a conference organized by Neil Davidson and Joel Spolsky , and was held this year in San Francisco. The speaking line-up is a who’s who of software bloggers and authors, including Geoffrey Moore, Paul Graham, Dharmesh Shah and Joel Spolsky. There were several great presentations during the conference.

Software Review 47

Software Review Software San Francisco RSS 47

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

YoungUpstarts

FEBRUARY 10, 2020

AI-powered spend automation software integrates with existing expense management, invoice automation, contract management, and ERP systems to augment rather than disrupt your status quo. In the case of early payment discounts, this software notifies you that the invoice should be prioritized to get payment out in ample time. .

Artificial Inteligence 162

Artificial Inteligence Software Review Technical Review Software 162

Startup Lessons Learned

OCTOBER 20, 2008

If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) The current code is spaghetti, but the new code will be elegant. Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

Hearpreneur

OCTOBER 31, 2021

Durant lost control of GM to a bankers' trust just two years later, in 1910, due to enormous debt and a crumble in automobile sales. Saturn, Pontiac, and Hummer were all shuttered due to GM's bankruptcy, which occurred on June 1, 2009. He saw the company shift its focus from personal computers to IT services and softwares.

Entrepreneur 120

Entrepreneur Software Review Las Vegas Bankruptcy 120

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

YoungUpstarts

JUNE 20, 2016

However, virtual data room software came as a huge relief to many companies because it reduced wastage of time and numerous expenses made to physically store data. The old PDRs were quite cumbersome due diligence processes. percent between 2009 and 2014. This ensures due diligence is observed.

Software Review 100

Software Review Technical Review Due Diligence Security 100

YoungUpstarts

JULY 1, 2015

Through web analytics software, you should be able to track indicators like web traffic, sign ups (at each stage), click throughs for CTAs, and more. Although the book was first published in 2009, its principles are still valid to this day and age. Managing Inbound Marketing.

Software Review 100

Software Review Marketing Social Media B2B 100

SoCal CTO

DECEMBER 19, 2012

It's the same as when I've created financial models and then have it reviewed by a hard-core CFO, sophisticated investor or similar kind of expert. And in the case of defining mobile/web/software, there is even more variability in terms of form and format. I'm never trying to embarrass someone. I know how it feels.

Developer 354

Developer Technical Review Fractional CTO Software Review 354

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

A Smart Bear: Startups and Marketing for Geeks

NOVEMBER 29, 2014

The first 90 percent of the code accounts for the first 10 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time. — This is due to the very definition of “average” — you’ll spend half your time before the half-way point, and half after.

Software Review 300

Software Review Technical Review Startup Channel 300

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

NOVEMBER 9, 2009

This required convincing software vendors to move their applications to our unique machine architecture. I had hired the VP of marketing from a potential software partner who was responsible to get all this 3 rd party software on our computer. His real job – the action – was to get the software moved onto our machine.

Silicon Valley 327

Silicon Valley Software Review RSS Technical Review 327

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Software By Rob

JULY 24, 2009

Software by Rob Passionate about Startups and MicroISVs Lessons Learned by a Serial Entrepreneur home about press micropreneurs archives ← The Future of the Web is Small, Academic Earth, Beatles Rock Band, Top Developer Blogs, et al. Functionality, code quality, documentation…are all a distant fourth.

Software Review 76

Software Review Software Developer Entrepreneur 76

Cracking the Code

MARCH 12, 2010

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. So, here is the first edition, including the recent Q4 2009 earnings and the updated 2010 forecast. Cracking The Code on Facebook. Friday, March 12, 2010. Subscribe in a reader.

Software Review 63

Software Review Technical Review Cloud Forecast 63

Cracking the Code

AUGUST 3, 2011

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Cracking The Code on Facebook. software. (10). ► 2009. (9). Software 2.0: Cracking the SMB code. Wednesday, August 03, 2011. Posted by Philippe Botteri.

Software Review 67

Software Review Europe Technical Review Search 67

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Cracking the Code

NOVEMBER 7, 2010

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Cracking The Code on Facebook. software. (10). ► 2009. (9). Software 2.0: Cracking the SMB code. Sunday, November 07, 2010. Posted by Philippe Botteri.

Software Review 59

Software Review Technical Review Cloud Europe 59

A Smart Bear: Startups and Marketing for Geeks

MAY 3, 2010

In fact all these words and phrases should theoretically carry meaning, but theory is for people who don't need to sell $2,600 more software by next Friday so they can make rent. If I had enough hubris to run around christening years, I would declare 2009 The Year of "Authentic." We get it! So what should you do instead? Be specific.

Software Review 279

Software Review Technical Review Security Advertising 279

Up and Running

MAY 6, 2020

seen at the end of the most recent recession in June 2009. Unfortunately, due to COVID-19, those gains have disappeared – at least for the time being. . In fact, a report by Glassdoor found that 55% of job seekers report avoiding certain companies after reading negative online reviews.

Technical Review 115

Technical Review Software Review San Francisco Acquisition 115

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

YoungUpstarts

JULY 13, 2019

This is largely due to the fact that Microsoft hasn’t added updates to the media player since the year 2009! The fact that this media player software does not consume too much of your Windows memory space is a good reason to download it as an alternative to Windows Media Player. It is very flexible, and highly customizable.

Media 138

Media Audio Metadata Software Review 138

Up and Running

MAY 10, 2013

The event concludes three months of study (called “due diligence”) by the group of more than 30 angel investors, about half and half from the Oregon university towns Corvallis and Eugene. I’ve been a member since it started in 2009. . This year’s event was held on campus at Oregon State University.

Software Review 69

Software Review Oregon Portland Technical Review 69

ReadWriteStart

SEPTEMBER 9, 2019

According to Title 21 (Part 11) of the Code of Federal Regulations, all computer systems used to create, modify, and maintain electronic records and signatures (including mobile devices) are subject to FDA validation. All hardware and software must be readily available at all times for FDA inspection.

Technical Review 111

Technical Review Software Review Canada Startup 111

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. For software, the easiest batch to see is code. Every time an engineer checks in code, they are batching up a certain amount of work. This comes in all shapes and sizes.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Version One Ventures

JANUARY 10, 2017

Back in 2009, Bitcoin became the first decentralized cryptocurrency. The prevailing thinking then was that the cryptocurrency market was going to be a winner-takes-all race due to the strong network effects around mining. What makes tokens particularly interesting is that they enable built-in monetization of software projects.

Software Review 60

Software Review Technical Review OTC Due Diligence 60

Cracking the Code

JANUARY 7, 2009

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Wednesday, January 07, 2009. Happy New Year 2009 and thank you for your continued readership! Cracking The Code on Facebook. software. (10). ▼ 2009. (9).

Software Review 48

Software Review Technical Review Europe Venture Capital 48

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. Every change required a server restart.

PHP 166

PHP Software Review Ruby San Francisco 166

Cracking the Code

JULY 10, 2009

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Friday, July 10, 2009. Cracking The Code on Facebook. software. (10). ▼ 2009. (9). Software 2.0: Cracking the SMB code. Subscribe in a reader.

Software Review 63

Software Review Technical Review RSS Europe 63

Cracking the Code

OCTOBER 8, 2009

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Thursday, October 08, 2009. Labels: SaaS , software , Venture Capital. Cracking The Code on Facebook. software. (10). ▼ 2009. (9). Software 2.0:

Software Review 48

Software Review Cloud Technical Review Venture Capital 48

Cracking the Code

OCTOBER 9, 2009

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Friday, October 09, 2009. Labels: SaaS , sales and marketing , software. Cracking The Code on Facebook. software. (10). ▼ 2009. (9). Software 2.0:

Software Review 48

Software Review Technical Review Cloud Europe 48

Cracking the Code

FEBRUARY 24, 2010

Cracking The Code. Thoughts from a Venture Capitalist on Software, Software-as-a-Service (SaaS), Cloud Computing, Internet and more. Cracking The Code on Facebook. software. (10). ► 2009. (9). Software 2.0: Cracking the SMB code. Wednesday, February 24, 2010. Posted by Philippe Botteri.

Software Review 54

Software Review Technical Review Europe Venture Capital 54