3 ms·

I'm sick of object oriented/non-functional programming. It's soul crushing to constantly be fixing problems that wouldn't have happened in the first place if pe

• deleted 2y ago
  [deleted]
• okamiueru 2y ago
  Object oriented and immutability are not mutually exclusive. Would I be correct in assuming that you're tired of people not doing proper data engineering, and in general having a irresponsible disregard for it? At least, "soul crushing to constantly be fixing problems that shouldn't have happened in the first place" resonates a lot. But I mostly see it as a result of the aforementioned.
  • namaria 2y ago
    Yeah in theory one can do everything correctly with assembly language. That sort of argument misses the point entirely. When you have to touch code that several other people work on, guardrails are the only guarantee you have that someone else didn't take shortcuts and left unnecessary levels of complexity behind for you to untangle.
• shrimp_emoji 2y ago
  When I see "state seeds" planted unnecessarily (sometimes by me!), I come down on it in code review, lest they germinate into bugs. ;p My team is receptive, and we refactor to remove them. Maybe that's why my soul doesn't feel anywhere near crushed, even though I totally empathize with the problem.
• gkhartman 2y ago
  I often feel this way l only to realize that the real cause is that the software was written before planning the architecture first. Usually caused by the rush to a minimum viable product rather than maintainability. Immutably can definitely lighten that burden though. The worst case is opening the code and finding mountains of global state that can be modified from who knows where.