• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle


  • Yep, it is mostly apparent in big companies I would say. I could go on and on, but basically your work is so disconnected from the final output that what end up actually “mattering” is a bunch of made-up bullshit. Putting in quality work and improving your product/service does not benefit most of the people you interact with directly, unless of course you’re working on the popular thing that will get people promoted.

    Anyways, I also left the corporate world to start my own business. Life is so much easier when all you need to care about is the quality of your work and not political points. I like my hard work to rewards me, and not just some guy spending his days in meetings claiming credit for “his” “initiatives”. Some of those folks would never survive a job that isn’t a mega corp paying them to improv all day in meetings.




  • Elderos@sh.itjust.workstoMemes@lemmy.mlLies! Deception!
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    1 year ago

    I have seen a doc about Home Depot (not the pictured store) some time ago. Apparently the overstocked facade was a big deal because those big stores want you to think they have everything that can possibly exist in their inventory so you only always go there and make no further stops.

    Of course, it’s smoke and mirror and a lot of stores adopted the big warehouse style for the same reasons. Some stores have legit empty boxes filled with crap all over. If you ever went into one of those store looking for something very specific tho, it is pretty apparent that they only overstock a few profitable items and the rest is no better, or worse than smaller locally-owned shops inventory-wise. Only exception around here would be Costco, which is a.legit warehouse.





  • What you seem to be describing is one big class with lots of responsabilities, and not circular dependency. Personally, I don’t think it is ideal, and I don’t know about your specific case so I could be wrong, but I have never seen a legit case for bloated classes. That being said, making a big class is still much better than splitting it into inter-dependant classes. Classes that know each other are so cohesive that they might as well be the same class anyway.

    To add onto the circular dependency problem, it is not just about readability and cognitive load (though there is some of that), but cyclic dependencies actively break things, and make it much harder to manage the lifecycle of a program. No dependency injection, poor memory management, long compile times. It is a huge hack, and I understand that you think it can be the proper solution sometime, but it is really just a bad thing to do, and it will bite you some day. And I am assuming here that you’re using a language that is friendly, in some languages you won’t even compile or run past a certain point, and good luck cleaning up that mess.

    edit: replaced “module” with “class” for consistency


  • It does not get more complicated to split your example. What gets more complicated is giving all sort of unrelated responsabilities to a single class, simply because it is the path of least resistance.

    In your example, all you need is an extra module listening for configuration changes and reacting to it. This way you leave your context-specific logic out of your data model, no need for cyclic dependency. There are so many downsides to cyclic dependency, to justify it because splitting your logic is “too complicated” really isn’t a strong argument.