DHRicoF

jq is an awesome tool and bothers me deeply having claude generating some big fat python script for a single line jq command.

Yes they are. They are transitioning through levels in the conduction band where you have plenty of them.

Every time you see a macroscopic phenomena, you are looking at a stupidly high amount of quantum levels with very similar energies.

How else are you sure your team does not conflict with itself?

/s

Imagine if they hired those 1111 to do the most massive nine-month-long live coding interview and only 11 pass the bar.

I want to learn Forth. Do you have any good reference or know about some good code examples?

Just learned the stack operations and trying to get used to them, but I have some bigger projects in my personal backlog.

The power to destroy a thing is the absolute control over it.

I don't have enough time now to work out how are the movement described in your representation to evaluate its convenience. If you have worked out something, could you share it?

I don't know anything about the cube world as I'm just a noob in this.

I don't understand why I would push to origin my local branch. This will (potentially) require multiple push -f. I prefer to share the work in a state I considere complete.

As an alternative, just create a new branch! `git branch savepoint-pre-rebase`. That's all. This is extremely cheap (just copy a reference to a commit) and you are free to play all you want.

You are a little more paranoid? `git switch -c test-rebase` and work over the new branch.

Then is not rebase your problem, but all your other practices. Long lived feature branches with lot's of unorganized commits with low cohesion.

Sometimes it's ok to work like this, but you asking git not being judgamental is like saying your roomba should accomodate to you didin't asking you to empty it's dust bag.

False

For your example, if both lists are small enough, the constant factor on the cost of creating the hashmap eliminates any advantage you could have. Anyway, it's not like most places were I've seen a nested loop used for search the developer had cared. Today I am in a bad mood.

I have to touch some of the most unnerving modules in a legacy project and everything is a trap. Lot's of similar repeated code with ugly patterns and some big brain trying to hide the ugliness with layers and layers of indirections and inheritance, and calling it clean because there is a factory class. The biggest joke? each implementation have a different interface for key methods, so later you to check what instance got created.

I want to keel myself. Anyone could assist me in a seppuku?

But most common noises are not white. you had to decolor it before.

Should Archeologist rebase or merge when new evidence is undercover?