So, if you are a programming "ninja", does that mean you sneak into other repositories and burn them down or poison the author?

Oh, look. I incorporated yet another programming related metaphor in my writing.

I hope this isn't an automatic rejection when the agent requests a full MS. Most people don't appreciate any of my programming related metaphors for some reason.

The definition of torture: watching your non-techie wife attempt to setup a new computer and refusing to accept help.

... there are so many metaphors I can put here but if she sees any of them it would be grounds for divorce so I will leave it at that.

if there's one thing I love more than coding, it's using metaphors to explain to other people why they're not "getting it". like the all famous contractor:

"yeah I know you need 5 months to build my house, but can you do it in 2. Also, I'm going to pay half. Oh, and when the house is done, could you also add a cellar?"

any more good metaphors out there?

I'm currently explaining how SSH Keys work, did I do well?

Do you think the keywords used by git (or other version control systems) are intuitive?

I'm talking to a very junior dev about git and I find myself having to explain around the fact that I don't feel the keywords are great. They are asking good questions like
* Why do you say "push the commit" but then say "make a pull request" - when I want to push why isn't it called a "push request"
* "Why are the metaphors sometimes related to trees (branches), sometimes roads (forks) but you still call it "master" instead of tree trunk or main road?
* Why do you call it "commit", what kind of commitment am I making?

Yesterday at my career progression chat my manager told me that to showcase more seniority I would need to "stop moving the needle by myself and become a multiplier".

So in order to progress I need to change from being a sewing machine to a mathematical operator??!!?!?
Thanks, that's very fucking helpful.

I think that the metaphors we use to design software can hold us back sometimes.

Specifically, I’ve been thinking about file systems.

“File” is a fine metaphor for “chunk of data” I guess but we use two conflicting metaphors on top of that to describe the same thing: “folder” and “directory”.

Why do we limit ourselves to this rigid, hierarchical system for managing our data?

Maybe something based on tags, or attributes or some other metadata.

Hierarchy can be useful so I don’t want to completely get rid of it, or anything drastic like that, but we (or at least *I*) don’t think in those terms.