• 0 Posts
  • 13 Comments
Joined 10 months ago
cake
Cake day: September 6th, 2023

help-circle


  • CorvidCawder@sh.itjust.workstoScience MemesLPT Do it.
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    It depends heavily on region. I personally don’t think I ever had issues with parsers. I used the awesome CV template as a base. It’s fairly simple while still not being completely boring. You can find it on GitHub or overleaf iirc (it’s been a while).



  • It’s my belief that it’s rare for evolution to screw up.

    That’s not how it works, I’m pretty sure… Mutations will have random effects and the species evolves based on characteristics being selected for based on better survivability, reproductive effectiveness, etc.

    I would do everything I could to find an alternative solution and talk them down from it.

    I’ve read your other messages and it seems that you’re thoroughly convinced that this wasn’t the case here. I suggest that you get a bit more context about this whole situation, as it has been a long path of trying multiple treatments and approaches, without any success. So it’s not even remotely close to what you suggest here. No Futurama suicide chambers here.







  • Shared branches should always only move forward. Most Git-* systems support stuff like protected branches.

    I personally like tidying up your own feature branch with rebasing and then merging it into main (preferably using only FF merges). However this is not scalable for some larger projects, and for example monorepos also make this hard to accomplish. In those cases the solution ends up being squash+merge.

    The extra information about the squashed commits is usually persisted to these systems (GitHub PRs, GitLab MRs, etc) so you don’t really lose much, I guess. Although I do prefer keeping it all in plain git.