Skip to content

Instantly share code, notes, and snippets.

@toddhgardner

toddhgardner/abstract.md

Last active December 24, 2021 08:35
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save toddhgardner/2589b8bc75a0831737b62c3d1916255d to your computer and use it in GitHub Desktop.
Save toddhgardner/2589b8bc75a0831737b62c3d1916255d to your computer and use it in GitHub Desktop.
Download ZIP
We Didn’t Stop to Ask If We Should: Understanding Build vs. Buy
Raw
abstract.md

Software Conference talk proposal for 2018/2019 season. Thanks for taking the time to review this for me. Comments and criticism welcomed.

Title

We Didn’t Stop to Ask If We Should: Understanding Build vs. Buy

Topics

Architecture, Business

Abstract

We were so preoccupied with whether we could, we didn’t stop to think if we should! Before debating React vs. Angular or .NET vs Node, we must ask ourselves, should we even build this? Whether you’re an entrepreneur launching a new project, an enterprise developer stuck integrating middleware, or a architect moving logic to the cloud, you’re making decisions that will have lasting consequences. Deciding which problems are worth your investment is at the root of success or failure.

Join us as we dig into real case studies from enterprises and startups. We’ll explore the options, costs, and risks inherent in deciding what to build, what to buy, and alternatives in between. We’ll consider the opportunity cost of building systems, the sustainability of open-source, and the risks of vendor lock-in. You’ll leave equipped to make better decisions in your daily development and solve the problems that matter.

@taylonr
Copy link

taylonr commented Feb 6, 2018

I think this is an important topic to be sure.

Is there a way to highlight the last sentence more? Perhaps move it up from the last line? I think the real case studies is what would separate this from talks that are just going to give you bullets to consider, and would make me more inclined to say "This is a talk I would go to" and/or "This is a talk I'd take for a conference."

@kwelch
Copy link

kwelch commented Feb 6, 2018

I really like this topic. Last round of reviews I didn't accept many soft talks, but this would be a good contender since I agree so much with the premise. As developers we are so quickly get deep into a solution that we lose what the initial problem was.

I agree with Nate, I think teasing the case studies would really add some appeal to this.

@toddhgardner
Copy link
Author

toddhgardner commented Feb 6, 2018 •
edited

@taylonr, @kwelch: I like it, I've heard the case study preference before. I reworded to bring it up to the top of the 2nd paragraph. Thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment