Most IDEs support automatic code formatting, and doing so on save. Or have it as a github hook.

Not required. Looks like Java, just use reflection.

Keeping the clean version around seems dangerous advice.

You know it won’t get maintained if there are changes / fixes. So by the time someone may needs to rewrite the part, or application many years later (think migration to different language) it will be more confusing than helping.

What does make out do?

Automatic code formatter with company style rules for more consistency across all developers.

Make those changes in an own commit, or keep it to files you already have to touch.

Autoformatter should fix that, unless you use python. (but even then they might fix it to the closest proper indentation level)

Maybe alignment more for the righthand side of assignments. If you have a block of variables with different name lengths, or within a constructor / function call.

With physics, but paused while coding. It only comes crashing down when the code gets executed.

May I introduce you to Usb 3.x renaming?

3.0, 3.1Gen1, 3.2Gen1, 3.2Gen1x1 are the 5Gbps version.

3.1Gen2, 3.2Gen2, 3.2Gen1x2, 3.2Gen2x1 are the 10Gbps version.

Just get copilot for vim /s

Good idea. Other: Let it return something long other than yes / no to waste token and possibly crash the service.

While you’re at it, also test

• one
• three fifty
• 69 nice
• 6.9
• 4,20
• null (it’s German for zero)
• pie (and pi)
• cake
• fruits
• One million three hundred (wonder if it gets confused by “one” and “three”)

We can add caching so numbers that have been checked once can be quickly looked up from an inMemory database.

Good point. Maybe that’s why they clarified “all knowledge in data structures and ml and ai” in the end.

Then again, just because you have all puzzle pieces (and a few extra) it does not mean you can solve it.

Sounds like they are the product owner :)

Heuristic: keep it until 512, afterwards powers of 2, and numbers like 1000, 2000,…, 10000, 20000,… (regex: [0-9]000+)

Checking the diff before commit, solve merge conflicts

Also if it’s well integrated into the IDE it feels less like using a separate tool. For 95% of what I do the ide/gui feels better (fetch, pull, push, commit, checkout, merge). Usually just 2-4 clicks and no need to type the branch name (ticket number and then some)

For Reflog, reset I use the terminal.

If I had to start github desktop or another seperate gui I would use the terminal that’s integrated into the IDE.

Even without algorithm knowledge it should be fairly obvious that you can just fast forward several minutes and check if the item has gone missing.

Not the most efficient solution, but beats watching the entire tape in real time.

Heard about that too! Is there an updated version for ipv6?