prototype or perish: why prd’s are dead & speed is god
signull.substack.com
prototype or perish: why prd’s are dead & speed is god
One of the lessons that TMitTB has tried to get across to you, the big message that matters most to him, is that code is never done; after shipping the new platform (no longer a website, this is a platform), with all its interlocking components, he and his team will continue to work on it forever. There will always be new bugs, new features, new ne... See more
PAUL FORD • Paul Ford: What Is Code? | Bloomberg
A popular idea in Silicon Valley is “Done is better than perfect.”10 The sentiment is not that we should produce rubbish. The idea, as I read it, is not to waste time on nonessentials and just to get the thing done. In entrepreneurial circles the idea is expressed as creating a “minimal viable product.”11 The idea is, “What is the simplest possible
... See moreGreg Mckeown • Essentialism: The Disciplined Pursuit of Less
The key to pursuing speed and adaptability at the same time is to view software technology as a continuously evolving asset, instead of something that is built once and then maintained.
Jim Highsmith • EDGE: Value-Driven Digital Transformation
The opposite of process is chaos, but an in-between is rapid adaptation, emphasis on rapid . Limit scope as much as possible, ship small things fast, and react to feedback quickly.
The design process assumes that dev time is the utmost priority, and this moves a bulk of labor into the design process. This is a faulty premise. The most valuable thing... See more
The design process assumes that dev time is the utmost priority, and this moves a bulk of labor into the design process. This is a faulty premise. The most valuable thing... See more
The Design Process is a Trap - Adil Majid
This was their system: prototype and test, prototype and test, prototype and test—until the time was up. When there is no set path, this system wins.
Eric Barker • Barking Up the Wrong Tree: The Surprising Science Behind Why Everything You Know About Success Is (Mostly) Wrong
Here is a simple process for shipping software projects that works. First, decompose the project into a stream1 of headlines. Then pick an aggressive date to ship the first headline and work like hell to meet that date. Have everyone work only on one headline at a time– the upcoming one. Ignore everything else. Don’t work on anything that doesn’t h... See more