Simplicity Reveals Design Flaws

3min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

The complexity of a function can often be assessed through the number of parameters it has. A high number of parameters, especially when disproportionate to the lines of code, indicates potential design flaws, suggesting a need for simplification. Striving for clarity in naming can further highlight issues; difficulty in naming may suggest that the function is trying to encapsulate too much. Clear inputs and outputs are crucial, as they form the interface of the function. Additionally, resorting to complex structures to minimize input count, such as hashes or maps, can obscure clarity and hinder proper design. In programming languages like Go, the emphasis on simplicity encourages better design practices, making it easier to identify and rectify complex or convoluted code.

Jerod is back with another “It Depends” episode! This time he’s joined by Kris Brandow from Go Time and they’re talking all things API design. What makes a good API? Is GraphQL a solid choice? Why do we do REST wrong? And WTF does HATEOAS mean, anyway?

Leave us a comment

Changelog++ members save 10 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

Neon – The fully managed serverless Postgres with a generous free tier. We separate storage and compute to offer autoscaling, branching, and bottomless storage.
Sentry – Get $100 towards your error monitoring with Sentry! Use the code changelog.
Fastly – Our bandwidth partner. Fastly powers fast, secure, and scalable digital experiences. Move beyond your content delivery network to their powerful edge cloud platform. Learn more at fastly.com
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.