View from Seed

NOVEMBER 6, 2014

Then as your business grows, you’ve already established a culture of good engineering practices, you already have the senior staff up to speed, and you’ll find it easy to attract more talent. NVV: Startups are all about tradeoffs, and engineering is a great example. And your code already does what it’s supposed to do!

Technology 334

Technology Ruby Startup Engineer 334

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

YoungUpstarts

APRIL 21, 2013

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Customer development (the understanding of customer needs) must be married to agile development (a process which drives waste out of product development).

Lean 193

Lean Technical Review North America Startup 193

femgineer.com

JULY 18, 2010

HOME About the Femgineer Speaking Engagements Reading List Recruiting Startup Engineers With the startup market taking off, there is always a clamor to find good engineers, developers, and designers. Engineers love to build, solve tough problems, and make progress. When to start recruiting? Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Venture Chronicles

AUGUST 2, 2013

If we did anything egregiously wrong at Get Satisfaction in the 2010-1012 time period it was to under-invest in the product with the assumption that the existing product was good enough. engineers paired would jump from frontend to backend erratically at each sprint iteration.

Product 62

Product CTO Hire Architecture Startup 62

The Next Web

DECEMBER 2, 2013

Luck, timing and social engineering are bigger components than most entrepreneurs care to imagine,” adds Werdelin. With the existing product in mind, the $500,000 would be broken out evenly over the nine months with the first two months dedicated to design, specifically user architecture, brand and polish design. 3) Facebook.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Feld Thoughts

MAY 5, 2011

The first version of the product was based on an architectural approach that didn’t aptly satisfy all players in the ecosystem and wasn’t flexible enough. Oh, and they are hiring as fast as they can find great people ; across the spectrum (business, sales, & engineering).

CTO Hire 131

CTO Hire Cofounder Architecture Product Development 131

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The engineering team would then build that feature, mimicking the UI as close as they could using the current primitives supported by the system. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

OnlyOnce

OCTOBER 18, 2010

Why CEOs Shouldn’t Mess with Engineers. The sad story of its sinking seems to have several potential causes, but one is noteworthy both in terms of engineering and leadership. The sad story of its sinking seems to have several potential causes, but one is noteworthy both in terms of engineering and leadership.

Engineer 123

Engineer Poland Sweden Architecture 123

YoungUpstarts

APRIL 14, 2014

Not too long ago, German software giant SAP blew up the management framework for its 20,000-person development department and replaced it with “mini-teams” of roughly 10 people. As a result, product development time was cut nearly in half in a three-year period. Soldiers will jump on a grenade to protect their fellow soldiers.

Agile 196

Agile Leadership Architecture Product Development 196

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

NOVEMBER 14, 2013

We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. LSC: One of the biggest fears people have about a continuous deployment environment is that it introduces more risk to engineering. How do you address that?

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Steve Blank

JUNE 25, 2009

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. Their engineers hated us.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.

Vertical 144

Vertical Silicon Valley Marketing Customer 144

www.lanceglasser.com

MAY 13, 2012

A Model for Return on Engineering Expenses. Product development. Queuing theory and product development. A Model for Return on Engineering Expenses. The Essential Product Investigation Phase Gate. Growth, Profitability, and the Stock Price. Metrics for cyclical businesses. Let the Games Begin!

CTO 40

CTO CTO Hire Technical Review Architecture 40

adam.heroku.com

MAY 18, 2012

Everyone has to be a generalist and able to work on any kind of problem - specialists will be (at best) somewhat bored and (at worst) highly distracting because they want to steer product development into whatever realm they specialize in. If that’s the case, stop growing, and scale back down until you nail product/market fit.

Developer 92

Developer Database Architecture API 92

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. I have found this quite rare in engineers. At the time, I was a die-heard Java zealot.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. After years of engineering effort, changing these assumptions was incredibly hard. Even a great architecture becomes inflexible. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Austin Startup

DECEMBER 26, 2017

THE SPEAKERS MELANIE DISALVO Melanie DiSalvo began her fashion career in product development after graduating from the Fashion Institute of Technology’s Textile Development and Marketing program. in Mechanical Engineering (Product Design) and a B.A. She received a PhD & M.S.

Technical Review 48

Technical Review Technology Philippines Silicon Valley 48

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

ctotodevelopers.blogspot.com

JULY 11, 2012

The implementation and architecture can also suffer if the team under or over invests engineering time, implementation of standards, or testing discipline in the wrong areas. Left on its own, product owners and development teams just may make debatable and sometimes questionable decisions on priorities or implementation strategy.

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 13, 2008

Our bias as technologists is to over-focus on the product part of the problem, and five whys tends to counteract that tendency. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Steve Blank

AUGUST 27, 2012

Tossing their agile development process and at times their entire business model in the air, the company would go into fire-drill mode and engineering would start working on whatever his latest insight was. Some of the engineers figuring if the founder was declaring they were toast in 90 days were updating their resumes.

Founder 316

Founder Cofounder Advisory Board Burn Rate 316

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Thats good for QA and for engineers. Faster (and better) feedback.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&# In traditional batch-and-queue development, these two concepts are linked.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Up and Running

AUGUST 4, 2016

If you’re looking for news from literally everyone in the construction industry—both engineers and foremen—don’t skip this resource. This publication puts the spotlight on commercial interior design and architecture, an angle most other sites don’t take. See Also: Do You Know How to Face Your Fears and Get Out to Network?

United States 60

United States Architecture America Lean 60

Startup Lessons Learned

FEBRUARY 16, 2009

This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. As you suggest, Thought Experiment Part II is going to involve lots of changes to the classic MMO architecture that makes it more like the web. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Austin Startup

MARCH 22, 2010

million from the State of Texas through the Texas Emerging Technology Fund (TETF) for the development of its module?integrated SolarBridge Technologies announced that it has been awarded $1.5 integrated microinverter and management system. SolarBridge expects to add a total of 60 employees in Austin over the next 3 years.

Texas 54

Texas Architecture Austin Product Development 54

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. You can see the design of the program here. link] Roger September 9, 2009 5:26 AM StartBreakingFree.com said.

DC 90

DC Washington San Francisco SBIR 90