DPL Reading List – June 5, 2015


| June 5, 2015 | in

Here are some of the articles we’ve been reading around this office this week.

Who Will be Hurt Most When the Tech Bubble Bursts, Not VCs (Thanks to Steve Kiene for recommending this article) – “A speculative bubble requires a “who’s the greater fool” syndrome to fuel it. Timing of the burst is what determines who in the market ecosystem would have a harder fall. Right now, cross-hair is clearly on the employees and founders. Not the VCs, for sure.”

The Series A Crunch Domino Effect on Middle America – “Even multibillion-dollar, centuries-old brands understand the value of new technological capabilities, and Middle American startups are best positioned to bring them that value. Unfortunately, there aren’t enough A rounds to go around, so many of these startups may be ignored, won’t be given a chance, and will be left behind. Compare that to a $35 million anonymous messaging app with no revenue, and ask yourself: Where is the real value? The answer is clear: Middle America.”

4 Business Models for the Data Age (Thanks to Brian Zimmer for recommending this article) – “Data is invading every nook and cranny of every sector, every company therein, every department, and every job. As it does, it’s flexing its strategic muscles, and four ways to compete with data are starting to emerge.”

This Causes People to Purchase (Thanks to Jarrod Wubbels for recommending this article) – “As innovators, we are always chasing that question: What will cause someone to buy? To get the right answer, you first have to be asking the right questions.”

How to Earn Respect as a Leader  (Thanks to Brian Zimmer for recommending this article) – “When people respect you only because of your authority, they will give you the minimum effort. Some incredibly brilliant people have earned respect because they are so smart, but most people aren’t incredibly brilliant. So how do you go about it?”

Rearchitecting GitHub Pages (Thanks to Paul Bauer for recommending this article) – “When we started approaching the storage capacity limits of a single pair of machines and began to think about what a rearchitected GitHub Pages would look like, we made sure to stick with the same ideas that made our previous architecture work so well: using simple components that we understand and avoiding prematurely solving problems that aren’t yet problems.”

How to Manage Scope Creep (Thanks to Brian Zimmer for recommending this video) – “You routinely see scope creep in projects of all sizes in every industry and sector. Various stakeholders ask the team to produce more and more as work progresses without understanding the collective effect on the project’s schedule or budget.”

Related posts