Dan Dean @dandean@indieweb.social
Public

RE: mas.to/@carnage4life/115832534

The sleight of hand – or the fundamental flaw – of this observation, is that it took their team a year to understand the problem by actually building a thing. Once you deeply understand a problem, it's trivial to get the dumb code vomit machine to produce code.

But producing the code is not the hard part, and using the code vomit machine is not a great way to build a system you understand from scratch if you haven't already solved the problem.

So the shortcut is a mirage.

Dana Fried @tess@mastodon.social
Public

@dandean this is what I'm confused by.

Like, if you described something like this to me I could probably write something that "isn't perfect" in a few days; any really good engineer should be able to. (Also: never underestimate the cost of getting from rough draft to production.)

The key would be describing it in detail, and to do that you'd have to already know what you were going to write.

The year is a year of debate, trial and error, etc. The code is almost never the hard part.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/tess/statuses/115834799653847564 on your instance and quote it. (Note that quoting is not supported in Mastodon.)