flail

10 ms·

121.
by flail 1y ago
That's just another great vantage point to consider when looking at product development. Accompanying many early-stage startups in their journey, I see how often the development (which we're responsible for) takes a back seat. Som
122.
by flail 1y ago
Oh, I agree that in many companies, internally, we create perceptions that development is, indeed, THE bottleneck. VP of Product put all the pressure on dev teams to deliver all the features against the specs. Then they release the new pr
123.
by flail 1y ago
We have this saying: Our clients always know what they want. Until they get it. Then they know they wanted something different. And don't take that as a complaint. It's a basic behavioral observation. What we say we do is differe
124.
by flail 1y ago
Whenever a development effort involves a lot of AI-generated code, the nature of the task shifts from typing-heavy to code-review-heavy. Cognitively, these are very different tasks. With the former, we actively drive technical decisions (de
125.
by flail 1y ago
If only "trying things" always equaled "developing things". There's a whole body of knowledge (under the Lean Startup umbrella) that argues otherwise. Do we always have to build it before we know that it will work (
126.
by flail 1y ago
Since I haven't mentioned the context in the article, it is a small agency with a customer target of early-stage (ideally earliest-stage) product startups. We have literally one half-hour-long sync meeting a week. The rest is as lightw
127.
by flail 1y ago
I wouldn't discuss with that part, although there are definitely limits to how big a chunk of a big product a single brain can really grasp technically. And when the number of people involved in "grasping" grows, so does the
128.
by flail 1y ago
I would agree if the only way to achieve (digital product) success were to implement as many versions of software as possible. That's not true. The whole Lean Startup was about figuring out how to validate ideas without actually deve
129.
Development speed is not a bottleneck(pawelbrodzinski.substack.com)
192 points by flail 1y ago|149 comments
130.
Where's the Shovelware? Why AI Coding Claims Don't Add Up(substack.com)
3 points by flail 1y ago|1 comments
131.
AI Has Broken Hiring(brodzinski.com)
2 points by flail 1y ago|0 comments
132.
Vibe Coding Doesn't Replace Tech Skills; It Requires More of Them(pawelbrodzinski.substack.com)
2 points by flail 1y ago|0 comments
133.
by flail 1y ago
Stories about CTOs heavily overrelying on their long-outdated coding experience are plenty. If that's an ego thing ("I can still do that and show them that I can"), they're going to do that with little care about the con
134.
by flail 1y ago
1. Organizations that care about controlling their data. Pretty much the same ones that were reluctant to embrace the cloud and kept their own server rooms. An additional flavor to that: even if my professional AI agent license guarantees t
135.
by flail 1y ago
Save for Gary Marcus' ego, which you're right about, most of the article is written by Nathan Hamiel from Kudelski Security. The voice of the post sounds weird because Nathan is referred to in a third person, but from the content,
136.
by flail 1y ago
One thing relying on coding agents does is it changes the nature of the work from typing-heavy (unless you count prompting) to code-review-heavy. Cognitively, these are fairly distinct tasks. When creating code, we imagine architecture, tec
137.
LLMs and coding agents are a security nightmare(garymarcus.substack.com)
194 points by flail 1y ago|96 comments
138.
OpenAl's Waterloo?(garymarcus.substack.com)
2 points by flail 1y ago|0 comments
139.
Fundamental Flaw of Hustle Culture(brodzinski.com)
61 points by flail 1y ago|33 comments
140.
The Renaissance of Full-Stack Developers(brodzinski.com)
1 points by flail 1y ago|0 comments
141.
Learnings from two years of using AI tools (at Thoughtworks)(newsletter.pragmaticengineer.com)
2 points by flail 1y ago|0 comments
142.
A Love Letter to Physical Whiteboards(brodzinski.com)
2 points by flail 1y ago|1 comments
143.
Things that have a bigger impact than coding assistants(codemanship.wordpress.com)
110 points by flail 1y ago|59 comments
144.
I Asked a Room Full of Leaders to Predict the Future, with Dice(medium.com)
1 points by flail 1y ago|0 comments
145.
by flail 2y ago
I generally trust the due dates printed on the items. But what would I know? Maybe it's a conspiracy to force us to drink old milk ;) On a more serious note, UHT milk can be stored for months, given it wasn't opened.
146.
by flail 2y ago
We don't need to "offer" that. Anyone can do this. Literally, anyone can make any decision (in a structured manner), so joining a core business initiative is obviously on the list. Also, she already does participate in core a
147.
by flail 2y ago
It wasn't just coming up with a system that works for software and taking a cool name from manufacturing processes. The methods in IT were built on the same principles (and, to a degree, values). It's just the implementation is di
148.
by flail 2y ago
Having more (all) the tasks in a backlog from the get-go might make sense if we knew that: a) requirements wouldn't change b) priorities wouldn't change c) we would be able to keep the understanding of the work throughout the effo
149.
by flail 2y ago
If we look at it from the systemic perspective, the goal is to have enough milk at the office just in time. Balancing the tasks between different actors within the system is a different concern. If 30 seconds of my time saves someone else 1
150.
by flail 2y ago
I failed to explain. In the ideal case, in manufacturing, we repeat the same set of tasks to manufacture identical goods. In software development, we have the same stages (development, code review, testing, etc.), but every task going throu

More ›