Skip Navigation
Believe it or not, git checkout

> Want to make a branch ?

> git checkout

> Want to make switch branches ?

> git checkout

> Want to get a specific file version ?

> git checkout

> Want to get remove changes to one file ?

> Believe it or not, also > git checkout

0
Apollo 11 Lunar Lander "Numero Mysterioso"

From the Apollo 11 github repo: https://github.com/chrislgarry/Apollo-11/blob/b56b8c3d03e810a6ceb69e1c0874d4c89d2c32f6/Luminary099/LUNAR_LANDING_GUIDANCE_EQUATIONS.agc#L666C1-L667C1

0
Our users are smart! They can figure out all the UI features.

Original tweet: https://twitter.com/DesignUXUI/status/576432203560685568

0
Rejected Github Profile Achievements
github.com GitHub - Flet/rejected-github-profile-achievements: 😵 GitHub achievements that did not make the cut.

😵 GitHub achievements that did not make the cut. Contribute to Flet/rejected-github-profile-achievements development by creating an account on GitHub.

>A collection listing Achievements that were rejected when creating the GitHub Profile Achievements feature.

>This repository attempts to list them all.

0
SlowDownAndWasteMemory()

// We play this game because we want this to be callable even from places that // don't have access to CallFrame* or the VM, and we only allocate so little // memory here that it's not necessary to trigger a GC - just accounting what // we have done is good enough. The sort of bizarre exception to the "allocating // little memory" is when we transfer a backing buffer into the C heap; this // will temporarily get counted towards heap footprint (incorrectly, in the case // of adopting an oversize typed array) but we don't GC here anyway. That's // almost certainly fine. The worst case is if you created a ton of fast typed // arrays, and did nothing but caused all of them to slow down and waste memory. // In that case, your memory footprint will double before the GC realizes what's // up. But if you do *anything* to trigger a GC watermark check, it will know // that you *had* done those allocations and it will GC appropriately.

Relevant code on line #269

0
I run into this seemingly every other day. Some XKCD's are timeless

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.

Link to original XKCD: https://xkcd.com/927/

0
Need to go deeper

This might skirt the lines between humor and horror :)

0
It's an older meme sir, but it check's out

Caption:

>In case of fire >1. git commit >2. git push >3. leave building

0
Reviews are great

Caption: > Ask a programmer to review 10 lines of code, he'll find 10 issues. Ask him to do 500 lines and he'll say it looks good.

0
[META] First 100 Users!

This community was started a little under a week ago, and in that time, over 100 people decided that this has some sort of worth to them and subscribed.

To them I say thank you for being here and for your vote of confidence. Hope you'll be here for a long time.

For the new comers, welcome, I hope you enjoy it here!

0
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)2E
2e8a9d6bb6935a54 @lemmy.world
Posts 22
Comments 0
Moderates