Shawn Hartsock

Where answers come from

Some pages can ask a language model questions. Set this up once; your choice is remembered in this browser for the whole site.

Model source
Use another source instead
You sign in on OpenRouter; it gives this page a key for your account.

I was wrong.

By Shawn Hartsock (author)

Originally published .

Republished from Thoughts and Ideas. The original writing is preserved; topic and concept suggestions are generated metadata, not part of the original article.

I was wrong about workflows. I was wrong about acceptance testing. I was wrong about scripting languages. It’s time to fix that. The next few weeks will begin my quest to change the world and right these wrongs.

  1. Workflows are not ever the right answer unless they can be tested and debugged. If you can not test it you can not validate it. If you cannot validate it you will eventually see code rot.

  2. Business needs should be modeled in testing not just whether a unit of code functions but whether it helps to fill a business need.

  3. Scripting languages are a vital tool in the software developer’s tool kit. You can create clean maintainable applications in the right scripting language. To dismiss dynamic scripting languages as toys is wrong.

Changing the world for the better…

Step one: Continuous Integration and Executable Documentation.

Explore the map · Browse by topic and date