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

help-circle

  • Nifty! I built something similar for my university graduation project. Did a PCB, ESP8266 based as well. Temperature, humidity, sound, vibration, airborne particulate sensor, and some other stuff.

    Wrapped a server up in docker for receiving the data, basic dashboard in JS for minor reactivity in components. Never ended up actually doing it cause I didn’t have a consistent host, but maybe I should spin it up again now that I have a home server.

    Cool project, looks neat! Anything you were caught off guard by when doing this?



  • Do you understand why people play games though?

    I understand why I do. I can’t speak to your motivations, I’m not you. I can, however, point to studies that discuss groups of people’s preferences in aggregate, as I have done. You’re an outlier, and that’s ok! Play what you want how you want!

    SBMM is, unfortunately for you, the current utilitarian optimal for multiplayer PvP gaming. It maximizes both adoption and retention metrics, as well as self-reported enjoyment scores (Likert scale) for the highest number of people. Bummer that it doesn’t optimize for you, but the other good part is that there are plenty of games that still support custom lobbies. Find one you like and have fun!












  • 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.