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

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 14, 2013

We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. Often the biggest problem is building up trust between the developers and the people who deploy and operate the systems.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Eric, Is this post about Architecture? Whats wrong with this picture?

Software Review 164

Software Review Engineer Management Technical Review 164

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. Learning is better than optimization (the local ma.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

YoungUpstarts

OCTOBER 8, 2014

But what if there was an easier way to have all your data in one place, accessible to all the programs that keep your business afloat? A well-planned system integration architecture and toolkit are vital to the success of your business.

Software 189

Software eCommerce Architecture Cash Position 189

www.lanceglasser.com

MAY 13, 2012

Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. So you want to ship the product early? Part of making sure one has the best technology involves reviewing programs and challenging teams. Metrics for cyclical businesses. Let the Games Begin!

CTO 40

CTO CTO Hire Technical Review Architecture 40

Hearpreneur

APRIL 13, 2022

I appreciate the thought and care that went into The Farmstand, a product developed by Zooey Deschanel and Jacob Pechenik that enables buyers to garden fresh vegetables without pesticides and less water than conventional gardening. They must, however, endure advertising and are unable to use the program offline.

Artificial Inteligence 77

Artificial Inteligence Entrepreneur Technical Review Software Review 77

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. Firmness: A program should not have any bugs that inhibit its function. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. Convergent Technologies was one of those OEM suppliers. I was surprised to see that they were in the room.

Technology 139

Technology Silicon Valley Fractional VPE Part-Time VPE 139

Hearpreneur

FEBRUARY 8, 2023

For business owners under the age of 45, it provides access to a global network and instructional programming. 11- Architectural professional group Photo Credit: Claudia Torres Your CV will appear better, and you'll have the chance to network with other people who work in the architecture field if you join a professional club for architects.

Community 96

Community Architecture Entrepreneur Networking 96

Startup Lessons Learned

JUNE 17, 2010

I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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

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. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

femgineer.com

JULY 18, 2010

If they’re coming up to speed with the product, development cycle, and company dynamics is good to let them ramp up slowly. Yes, building software is cheap and fast unlike other products. Remember people only have two hands! But there is still the overhead of testing, scaling, and securing.

Engineer 41

Engineer Software Review Startup Technical Review 41

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

The Startup Magazine

FEBRUARY 12, 2024

Twofish uses network applications involving frequent changes and programs that do not require RAM or ROM. Assurance of Quality The testing stage of the software product development process is vital. ZTA, or zero-trust architecture ZTA models differ from standard cyber security models, which depend on ongoing verification.

Artificial Inteligence 88

Artificial Inteligence Software Review Web API 88

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.&# Learning is better than optimization (the local ma. for Harvard Business Revie.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

NOVEMBER 29, 2008

If done right, a programming interview serves two purposes simultaneously. 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. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

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

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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

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. for Harvard Business Revie.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

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

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. Most engineers would ship code to production on their first day. for Harvard Business Revie. Amazon PostRank

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. The same principle holds for scaling a development organization. Stage 2: The first hires.

Developer 92

Developer Database Architecture API 92

YoungUpstarts

OCTOBER 20, 2020

You’ll need to implement transformation of four supporting elements to achieve an excellent customer experience:technical architecture, robust and secure data, business operations, and the organization’s economic business model. Use Design Thinking 2.0 to build the future. Step 5: Lead the Change.

Customer 162

Customer Architecture Leadership Database 162

techcrunch.com

OCTOBER 23, 2010

bfliris So it sounds like with Meebo (your claim to fame) you were passionate about the idea but had no programming skill, partnered with two people that had strong programming ability and did very little to assist them in creating a succesful application. I have had a programming job and tried to do side projects after work/ weekends.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

www.quora.com

JANUARY 16, 2011

Catalin Braescu • Jan 9, 2011 minor point : Microsoft : Bill Gates had been programming from age 14, and had been employed as a programmer writing software to control dams at 17. Paul Allen was even more technical, he wrote an emulator for the 8008 chip that ran on A PDP-10, that emulator was what was used to develop BASIC.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Software By Rob

AUGUST 18, 2010

But a more important question to which I don’t have a good answer is whether the Free/Premium strategy leads to better or worse product development. If you offer a product for free you get more users and more feedback on your product. But is it the right data? It could be a poem, drawing, whatever.

Software Review 78

Software Review Software Revenue Cofounder 78

VC Cafe

FEBRUARY 1, 2011

The Israel Parliament (“Knesset&# ) recently approved the new Law for the Encouragement of Capital Investments directed at supporting the industrial sector with a wide range of programs. These criteria can be interchanged with R&D investments or a large employment program by the company, as per the law. for the year.

Architecture 92

Architecture Dividend Minneapolis 92

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. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Even a great architecture becomes inflexible.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

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. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79