this post was submitted on 30 May 2026
-42 points (26.7% liked)

Technology

85055 readers
4177 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Deestan@lemmy.world 0 points 2 days ago* (last edited 2 days ago)

Frameworks can be fine. Using them before understanding what you make is not. At that point you often see it is faster and better to just make the parts you needed yourself.

Model as in you have a clear opinion on what your system does, why, how, and what it doesn't do. A model evolves during development, which is where it becomes hard: You always need to make room for things you didn't predict, so you need to adapt and refine the system model so that the change makes sense.

Adding features until a full system explanation consists largely of "but", "and also" or "except", things like "and you should ask Bea about how that part works" or the worst of all "this part can be anything", is the opposite of working from a model.