blog.wepay.com

OCTOBER 23, 2010

» 6 Things a Non-Engineer Should Know Before Founding a Web Startup By Rich Aberman Despite the obvious look of shock and panic on the faces of my WePay teammates, I recently committed my first lines of production code. Non-engineers are not “designers” by default. The 90/10 rule. Software is never finished.

Engineer 53

Engineer Software Review Web Technical Review 53

blog.wepay.com

APRIL 28, 2010

» 6 Things a Non-Engineer Should Know Before Founding a Web Startup By Rich Aberman Despite the obvious look of shock and panic on the faces of my WePay teammates, I recently committed my first lines of production code. Non-engineers are not “designers” by default. The 90/10 rule. Software is never finished.

Engineer 53

Engineer Software Review Web Technical Review 53

YoungUpstarts

OCTOBER 19, 2017

by Steve Owens, Founder and CTO of Finish Line Product Development Services. In this article we explore the unique challenges of a lean start-up and how Outsourced Product Development (OPD) can be used to overcome them. Reducing product turn time. Extending the runway. The Lean Start-Up Environment.

Product Development 153

Product Development Lean Developer Product 153

Hearpreneur

DECEMBER 30, 2020

My expertise in product development and project management came after working as a consultant in many industries. I started my business simply because I want to be of assistance to those who want to learn through the internet. I don’t just focus on helping businesses grow by ranking them higher in search engines.

Technical Review 142

Technical Review Entrepreneur Software Review SEO 142

Up and Running

SEPTEMBER 11, 2020

Let’s take switching from landline to VoIP (Voice over Internet Protocol) as an example. Wouldn’t it be wiser to channel your funds to product development and let your products speak for themselves? Marketing VAs can handle SEO and content marketing to increase your ranking on search engines.

Cost 150

Cost Technical Review Salary Social Media 150

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. Want to learn more about me? Try About the author.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. The human tendency to moralize about debt affects engineers, too. Accept that good design sometimes leads to technical debt anyway.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

YoungUpstarts

JANUARY 10, 2019

Search engine optimization became an integral part of digital marketing. Companies use SEO strategies when creating their ecommerce website design and it enables them to up their ranking in search engine results pages. Create a User-Friendly Design. They should your primary concern when designing the website.

SEO 147

SEO Engineer Search Mobile 147

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

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

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. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." For Neopets, its simply a side-effect of their game-like product design. Thats why eBay advertises on search engines, and Facebook doesnt.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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 artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Ben's Blog

AUGUST 28, 2012

In 2012, most everyone takes the Internet for granted and believes its emergence to be a logical, evolutionary step. A review of the technology press in 1993 and 1994 reveals that almost nobody believed the Internet would be important. Unlike political regimes, technological rulers are comprised of products rather than people.

Romania 77

Romania Software Review Cloud Mobile 77

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Anyway, thanks Stevey for your thoughtful post.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. An engineer who can talk intelligently about gender!

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

DECEMBER 28, 2009

I understand why people would think that a consumer internet service like IMVU isnt really mission critical. Thats a perfectly reasonable reaction, given that most releases of most products are bad news. The second shift in mindset required is to separate the concept of a marketing release from the concept of an engineering release.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

APRIL 4, 2010

Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule. Take a look and let me know what you think. Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. Seth Godin: How often should you publish?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Seth Godin: How often should you publish? Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Seth Godin: How often should you publish?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Ben's Blog

AUGUST 28, 2012

In 2012, most everyone takes the Internet for granted and believes its emergence to be a logical, evolutionary step. A review of the technology press in 1993 and 1994 reveals that almost nobody believed the Internet would be important. Unlike political regimes, technological rulers are comprised of products rather than people.

Romania 44

Romania Software Review Cloud Mobile 44

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 26, 2009

You can learn more about that by reading The engineering managers lament.) And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. Revisiting the Software Design Manifesto (and what.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Seth Godin: How often should you publish? Take a look and let me know what you think.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

bizthoughts.mikelee.org

MARCH 8, 2012

BizThoughts Thoughts about business, technology, the web & entrepreneurship About Booklist Contact Nov 15 2011 Finding a Technical Cofounder By Mike Lee Categories: Entrepreneurship , Leadership Since I have a technical background, I get about one offer a month to join some engineering team, or to be a technical cofounder.

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

techcocktail.com

OCTOBER 23, 2010

be the manager and product developer). Developer – Most likely your product requires some engineering. Make sure you have the right developer(s) on board in whatever capacity you need them, whether it’s a part time HTML or Wordpress developer or a full time PHP wiz.

San Francisco 44

San Francisco Startup PHP San Diego 44

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Seth Godin: How often should you publish? Take a look and let me know what you think.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 5, 2010

While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. This new volume also tackles examples from the Internet and wireless startups of today, both B2B and B2C. It is incumbent upon you to listen. It is incumbent upon you to listen.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

AUGUST 2, 2008

Want to learn more about me? Try About the author. Trying to learn more about lean startups? See Four Myths about the Lean Startup or The lean startup. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule. Take a look and let me know what you think.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125