You must log in or register to comment.
LOL how about horizontal gene transfer, and Eukaryotes being a merger of Alphaproteobacteria (and cyanobacteria for the photosynthesizing ones) and Asgard Archea.
It’s all interconnected, intertwined, nature man! Holobionts and shit.
When I first saw a platypus in person I was amazed by how small they where. They seem bigger in most photos.
Life has convergent evolution. It’s like when devs on different branches solve the same problem over and over again without telling anyone else or merging back to main so no one else has to code the same shit over and over again.
You know someone’s toddler took the controls for the platypus design.
“I want a duck…but you can milk it. Poison! Like bad bad sting. BEAAAVER tail.”Powerful homermobile energy.
To be honest, as someone who only very tangentially works with git – it fucking scares me.
It’s simple really. Like saving a computer game and then if something doesn’t work out you can go back to a previous save game.
It only really gets tricky when multiple people are continuing on the same save and you want progress from both when you load it. But you can leave that to the most senior person to figure out.
I understand the basic concept, but what with all the forked diagrams and heads and mains and I just want to try something with my one changed parameter in one config file
No no, I was joking that it was simple
It makes sense for distributed teams of contributors working on many features with governance what gets into main. For small co-located teams where probably collaboration and chronology are more important, not so much, but it’s the cool thing so people try use it for that anyway.
git reflog is my best friend
It can undo things that normally one would think are “undoable”
The idea of having to dig through a reflog is scary too if you don’t have a confident intuition of how the refs work in the first place
Evolutionary trees pretty much look like a git tree in a large company: always changing requirements, only patches, rarely less code. It somewhat works and nobody understands why.
I wanted to say that at least the programming language is always the same, but it’s at least two.
In both cases it works because that’s the only requirement. It doesn’t need to be elegant or make sense or even last very long
When you add a bunch of libs to the project but only use one function from each.
you know how all mammals were once fish? Well some of those intermediary species still survive to this day, like the lovable platypus :3 Also marsupials aka pouch things—one of those intermediary steps from layings like fish to incubating them in a placenta.
We still filter out all our salt, then mix it back into our blood, a slight modification of a marine fish’s method for dumping excess salt. Being terrestrial we can’t afford to lose salt
When the project contains decades-old legacy code, but it still works in modern environments.
Decades old code that only there because if removed it breaks everything, but does nothing otherwise.
That’s not the platypus, that’s crocodiles and sharks
test in production:
welp turns out it actually works fine, suck it losers
