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

help-circle


  • Yeah… he was an idiot for choosing to bring a firearm near known civil unrest, but it was pretty clearly self-defense. I mean they ran after him and attempted to seize his firearm…

    Pretty good case for gun control as a concept, though. Ultimately both parties were endangered and forced into action by fear for their lives by the fact that the firearm was in the situation to begin with. As a protestor, I’d fear for my life if an armed counter protestor showed up, cause you know the cops aren’t gonna keep you alive if that guy chooses to start shooting. But any action I could take to prevent that puts the firearm owner in a position to reasonably fear for their lives. The mere appearance of the firearm puts the situation on a path to escalation. Maybe lethal weapons shouldn’t be allowed casually in public.




  • “Based” is pre-zoomer (Gen Z/Alpha) gamer slang for “great”, with a slight connotation of oppositional greatness.

    Original gamer use may include describing use of the N word for memes as “based” as its a counter-cultural thing that gamers saw as good. Nowadays it’s pretty “normie-core” and any time something upsets the status quo in a positive way that might make opposition upset, is based.

    For example, Dark Brandon, a reimagining of the “let’s go Brandon” MAGA meme to be a progressive, anti-MAGA meme used as kind of a soft middle-finger to the right-wing internet, was incredibly based.







  • Tech people tend to be very black-and-white when discussing ideology. Reality is more forgiving.

    If you can get your hands on it, the opening chapters of “Practical Event Driven Microservices Architecture” by Hugo Rocha gives a reasonable high level view of when you might decide to break a domain out of a monolith. I wouldn’t exactly consider it the holy grail of technical reading, but he does a good job explaining the pros and cons of monolith v microservices and a bit of exploration on those middle grounds.


  • The reality is, as always, “it depends”.

    If you’re a smaller team that needs to do shit real fast, a monolith is probably your best bet.

    Do you have hundreds of devs working on the same platform? Maybe intelligently breaking out your domains into distinct services makes sense so your team doesn’t get bogged down.

    And in the middle of the spectrum you have modular domain centric monoliths, monorepo multi-service stuff, etc.

    It’s a game of tradeoffs and what fits best for your situation depends on your needs and challenges. Often going with an imperfect shared technical vision is better than a disjointed but “state of the art” approach.