As engineers, it can be really satisfying for us to implement clever, terse solutions to problems, relying on advanced tricks and techniques. As a result, we often write code that is hostile and inaccessible to the junior folks on our team. This article makes the case that we should strive to write simple, accessible code, using the dumb old primitives that everyone knows.
binarypie
link
fedilink
817d

tl;dr write maintainable code and don’t prematurely optimize.

The real cleverness lies in being able to write code that seems self evident in hindsight. Anybody can write convoluted code that’s impossible read after, but it’s a lot harder to express the problem using simple and clear code. The ability to understand a complex problem then express it using clean and maintainable code is what separates junior developers from senior ones.

Kromonos
link
fedilink
117d

Never heard of them. What do they do?

poVoq
admin
creator
link
fedilink
117d

Them?

Kromonos
link
fedilink
117d

Clever Code? Sounds like a company 🫣

Helix 🧬
link
fedilink
115d

Try reading the article.

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

  • 0 users online
  • 3 users / day
  • 14 users / week
  • 44 users / month
  • 233 users / 6 months
  • 11 subscribers
  • 348 Posts
  • 742 Comments
  • Modlog