14
submitted 3 days ago by yogthos@lemmy.ml to c/programming@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] gary_host_laptop@lemmy.ml 1 points 3 days ago

essentially they were using a database that needed much more than what they required which made everything super slow, so they used a more precise and small tool for the job they needed exactly, reducing the db's size. am i correct? i've been touching on this topic a bit recently so it's all still very new to me.

[-] yogthos@lemmy.ml 6 points 3 days ago

Yup, that basically sums it up. The key part though was that doing the inefficient thing first allowed them to make progress and to understand the problem better by working through it, which later led to a more clever solution. The moral of the story here is that it's always better to solve the problem even if your solution isn't optimal, and then reflect on it.

this post was submitted on 11 May 2026
14 points (100.0% liked)

General Programming Discussion

9904 readers
6 users here now

A general programming discussion community.

Rules:

  1. Be civil.
  2. Please start discussions that spark conversation

Other communities

Systems

Functional Programming

Also related

founded 7 years ago
MODERATORS