Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hehe, I agree with what you're saying here, but I think you might've misunderstood me.

> put the logic where it fucking goes, inline with its use! right there! nowhere else! don't nest it behind abstractions you don't NEED.

What you're talking about here looks more like over-abstracting. What I'm talking about is having understandable components with simple, easy to understand behaviour. I think we're on the same page.

I want to be able to understand what the component does at the first glance. I also want to be able to understand what a larger part of the system does at the first glance. But, overall, I'll always err on the side of _under-abstracting_ and duplication, like you.

One might argue that software development is about 1) defining a business problem, _then_ 2) communication (usually with "ghosts" i.e. another developer who is not in the room with you[1]), then writing the implementation. My philosophy on the subject is like this: https://sonnet.io/posts/code-sober-debug-drunk/

TL;DR it's always easier to write code than to read it, be kind to the next person reading it (it might be you)

[1] https://sonnet.io/posts/emotive-conjugation/#:~:text=Ghost%2...



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: