Mastodawn

As a programmer, I wish I could help people understand that the fastest part of any project is writing the code...

Non-programmers always want to throw more code writers at a project to speed things up. The "Mythical Man Month" problem aside,

the bottlenecks are all the legwork involved in defining the problem, the scope of this particular task, and fully testing it.

Even before AI, writing code was fast and we already have a lot of tools to crank it out...if we're clear on *what* to crank out.

This is prolly true in all fields, this difference in understanding between the people who actually work in a field, and the people who are adjacent to that field.

Show thread

Curt Olson

@codebyjeff I am a software guy that works with a bunch of friken engineers. They all know how to build physical stuffs and know all the right things about defining the problem before picking the solution ... until it comes to software and then they forget everything. The solution magics it's way into existing somehow ... the solution that they are picturing (and not close to fully describing) will flow easily. And bonus, it will be easy because I'll be using the tool they already picked out for me to do the development with (that I've never seen before, but the youtube videos talk about how you can build all kinds of cool stuff with zero coding) and it should probably take about a week or two. We are an achievement based organization so ... results ... now!