• 0 Posts
  • 115 Comments
Joined 2 years ago
cake
Cake day: November 13th, 2023

help-circle


  • You make an excellent case for mentorship in all this. Thank you for that. Upon reading all this, it never dawned on me that was even how anyone navigated poly.

    But it also seems to be a crucible for learning how to negotiating needs and figuring out how to talk about it openly with each other to build connection - and that process both requires and builds respect for your partners.

    I can say, with confidence, that even if one completely fails to leave the hypothetical realm with their monogamous partner, the thought-exercise alone carries some of these benefits. Polyamory forces the need to do some hard work, but there’s no need to actually go there when hypothetical scenarios are just as provocative. In fact, it might even function on some level for platonic relationships, where sharing time with others is a concern.

    At first, it uncovers things like jealousy, envy, and co-dependence. So you hit the books - all the poly literature out there lays out how to navigate these common issues. For the rest there’s psychotherapy, which is probably needed to grow as individuals, since all those toxic behaviors are usually rooted in trauma. From there one can become stronger, and hopefully so does their relationship(s).

    And poly guys aren’t going to meltdown. They are ok with a no, they are emotionally braced for that and have been through worse feelings already. And they have other relationships to fall back on.

    This never occurred to me. Thank you for this invaluable insight.












  • What are the maverick git workflows?

    Okay, but be advised: this is how we start fights. Depending on where you’re coming from, everyone else is doing it wrong. Keep that in mind. That said, I want to have a discussion with you and others, if possible.

    If we assume that a GitHub PR, or GitLab MR, workflow is “typical”, then the oddballs I know of are:

    • Geritt - It endorses a unit of review/work that is always exactly one commit. I have some strong opinions about why this is a thing, why it’s not great, why you shouldn’t if you’re not Google, and how Google got here, but that’s a whole other discussion. It’s a super-polarizing approach to Git in general.
    • Gitflow - takes the usual branching strategy of MR/PR work and dials it up to 11. This too is polarizing, as the added complexity can be a bit much for some folks.

    IMO, a lot of the trouble we run into with Git is largely due to training problems. Also, one has to architect the git space to fit the company, culture, and engineering needs at hand. This means planning out what repositories you need, how you’re going to solve CI/CD, what bar for code review is needed, how to achieve release stability, and how to keep the rate of change steady and predictable. To do any of that, everyone needs to learn a bevy of git commands to do this well, and not enough companies bother to teach them.




  • On the home-gamer gameplay side, this is a solid list. On the technology side, I think there’s even more that makes sense for a curated museum tour. There were big leaps made in arcade tech through the 80’s and 90’s that were pushing all manner of graphics and sound, head-and-shoulders above the previous generation.

    Sega’s “super scaler” boards come to mind, allowing for games like Hang-on, Outrun, and After Burner. Digitized sound samples started with Sinistar and Tempest. Dragon’s Lair amazed everyone with an interactive LaserDisc experience. There were also notable forays into AR with Time Traveler, and VR with Virutality. Lastly, we have the fully-enclosed and immersive cockpit of early Battletech simulators.