Monogamy in Software Development: One Product or One Field?

[binydev]

In the “Make Execution Matter: 13 Best Practices” section of “Unscripted ,” the concept of being “Faithfully Monogamous” raises an intriguing question for us software engineers. Does this mean we should commit to developing just one product, like a SaaS, or does it suggest a broader commitment to the field of software development itself? I’m curious about both the audience’s and the author’s perspectives on this. How do you interpret this advice in the context of our industry, and how have you applied (or not applied) this principle in your own career?

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[glitched]

My read is one product.

 

[Maxkaz]

My understanding is "one business - one need". Like you can focus on mens` shaving equipment and should not diverge to pet food supply. But if you are an expert in mens` shaving - it is ok to develop multiple products for various chunks of your client base and in different categories - from foam to instruments, like Gilette does.

 

[Jon822]

One business with one or more products. Opportunity cost is the primary reason this needs to be the case.

 

Dislike ads? Remove them and support the forum: Subscribe to Fastlane Insiders.

[NervesOfSteel]

In the “Make Execution Matter: 13 Best Practices” section of “Unscripted ,” the concept of being “Faithfully Monogamous” raises an intriguing question for us software engineers. Does this mean we should commit to developing just one product, like a SaaS, or does it suggest a broader commitment to the field of software development itself? I’m curious about both the audience’s and the author’s perspectives on this. How do you interpret this advice in the context of our industry, and how have you applied (or not applied) this principle in your own career?

Even before the age of the barter system ... only one field has dominated everything!

SALES!

Sales = Monetization. Rest is hobby!