One post says ideas and first versions are plentiful, but shipping something great feels like it demands more intentionality and focus.
Building is easier than ever, one post argues, with no shortage of ideas or first versions. Yet its author feels that shipping something great takes a greater degree of intentionality and focus.
—
5 Sources, first seen ago
—
Not ranked yet
—
Not ranked yet
@charles_irlRT @max_spero_: We live in a world with no shortage of ideas and v0’s. Building is easier than ever, yet it feels like shipping something g…
@annarmitchellThis is well put. I think we'll see a reaction in the best companies against the "ship it" culture of the mid-2010s. Shipping is easy now. Creativity, differentiation, and the patience to iterate to greatness will become relatively more important.
@VivaLaPandaat @elicitorg, one thing we've done recently that seems to be working is that for ~any feature now: - have a 10-30m pre-work chat w/ at least one-coworker to go over the plan - then you go and build it. Because of the agents, this is super fast - then, when you coworker goes to review it, they actually know what the hell is going on Lighter weight than having a huge Linear, but it still avoids the feeling of there just being constant PRs getting flung towards you at random. Costly in terms of meeting time in theory, but engineers need so much less "isolated focus time" now to write code that I think its very much worth it to ensure that: - people are working on the right problems - they're solving those problems in the right way - there is some bottleneck to just shipping a million features without due consideration - knowledge spreads around the team I think by default the models are making engineering much less collaborative in ways that make everything worse@charles_irlRT @max_spero_: We live in a world with no shortage of ideas and v0’s. Building is easier than ever, yet it feels like shipping something g…@annarmitchellThis is well put. I think we'll see a reaction in the best companies against the "ship it" culture of the mid-2010s. Shipping is easy now. Creativity, differentiation, and the patience to iterate to greatness will become relatively more important.@VivaLaPandaat @elicitorg, one thing we've done recently that seems to be working is that for ~any feature now: - have a 10-30m pre-work chat w/ at least one-coworker to go over the plan - then you go and build it. Because of the agents, this is super fast - then, when you coworker goes to review it, they actually know what the hell is going on Lighter weight than having a huge Linear, but it still avoids the feeling of there just being constant PRs getting flung towards you at random. Costly in terms of meeting time in theory, but engineers need so much less "isolated focus time" now to write code that I think its very much worth it to ensure that: - people are working on the right problems - they're solving those problems in the right way - there is some bottleneck to just shipping a million features without due consideration - knowledge spreads around the team I think by default the models are making engineering much less collaborative in ways that make everything worse@charles_irlRT @max_spero_: We live in a world with no shortage of ideas and v0’s. Building is easier than ever, yet it feels like shipping something g…@annarmitchellThis is well put. I think we'll see a reaction in the best companies against the "ship it" culture of the mid-2010s. Shipping is easy now. Creativity, differentiation, and the patience to iterate to greatness will become relatively more important.@VivaLaPandaat @elicitorg, one thing we've done recently that seems to be working is that for ~any feature now: - have a 10-30m pre-work chat w/ at least one-coworker to go over the plan - then you go and build it. Because of the agents, this is super fast - then, when you coworker goes to review it, they actually know what the hell is going on Lighter weight than having a huge Linear, but it still avoids the feeling of there just being constant PRs getting flung towards you at random. Costly in terms of meeting time in theory, but engineers need so much less "isolated focus time" now to write code that I think its very much worth it to ensure that: - people are working on the right problems - they're solving those problems in the right way - there is some bottleneck to just shipping a million features without due consideration - knowledge spreads around the team I think by default the models are making engineering much less collaborative in ways that make everything worse@charles_irlRT @max_spero_: We live in a world with no shortage of ideas and v0’s. Building is easier than ever, yet it feels like shipping something g…@annarmitchellThis is well put. I think we'll see a reaction in the best companies against the "ship it" culture of the mid-2010s. Shipping is easy now. Creativity, differentiation, and the patience to iterate to greatness will become relatively more important.@VivaLaPandaat @elicitorg, one thing we've done recently that seems to be working is that for ~any feature now: - have a 10-30m pre-work chat w/ at least one-coworker to go over the plan - then you go and build it. Because of the agents, this is super fast - then, when you coworker goes to review it, they actually know what the hell is going on Lighter weight than having a huge Linear, but it still avoids the feeling of there just being constant PRs getting flung towards you at random. Costly in terms of meeting time in theory, but engineers need so much less "isolated focus time" now to write code that I think its very much worth it to ensure that: - people are working on the right problems - they're solving those problems in the right way - there is some bottleneck to just shipping a million features without due consideration - knowledge spreads around the team I think by default the models are making engineering much less collaborative in ways that make everything worse
