HN user

_gy5c

106 karma
Posts0
Comments22
View on HN
No posts found.

i haven't used git range-diff but when local master is behind origin/master and I am trying to diff, I use a `git changes` .gitconfig alias:

    changes = !git diff $(git merge-base HEAD \"$REVIEW_BASE\")
Typically, that's:
    git diff $(git merge-base HEAD origin/master)

The only computer i've ever had with what I consider an acceptable level of line noise was a macbook pro

even a $15 USB-to-dual-3.5mm adapter sounded significantly better on other machines

I experienced this annoying line noise on ASUS, MSI and Dell motherboards

Before the meeting starts I confirm there is an agenda present, and ask the organizer to provide one if it's missing, and skip the meeting if no agenda is provided

I also usually ask at minute zero for the organizer to state the desired outcome of the meeting

I drop if I am not providing or gaining value

I explicitly prefix Error: when I am requiring a change, Warn: if I am suggesting a change, Info: if I have an unrelated comment

Error: `< n` is an off by one error, the last element won't be processed

Warn: Consider dropping the loop altogether. We know there are always eight elements.

Info: Nice name!

Mechanical Watch 4 years ago

you can expect a quality automatic movement (imo seiko is lowest end of quality) to be off on the order of single digit minutes per month

GitHub Copilot 5 years ago

There's a good amount of discussion on this topic in "The Mythical Man-Month". The entire book is discussing the factors that affect development timeframes and it specifically addresses whether AI can speed it up (albeit from 1975, 1986 and 1995 viewpoints, and comparing progress between those points.)

Coway AP-1512HH Mighty Air Purifier, based on Wirecutter reviews. Home ventilation isn't as good as the office, this makes a very noticeable difference with dust and cat hair. If needed I move it to the kitchen, it cleans up heavy smoke or odor from burgers/steaks/popcorn in about 45 minutes (for a ~6000 ft^3 volume)

I consider this essential: The ability to decouple the task from your ego.

Specifically:

- Never say "Got it" or "OK" when someone is explaining a problem or solution and you don't follow. It feels awkward to say "Sorry, I'm still not following. Do you mean that when..." five times in the same conversation but it is worth your time and embarrassment to come away with a correctly framed and well understood situation. Otherwise you will figure out what they meant after wasting hours/days/months solving the wrong thing.

- You'll be faced with situations where your colleagues/organization expect you to implement solutions you think are not the best. Understand that "the best way" for the team or business is not necessarily the same as "the best way" for you personally or "the best way" overall. You are likely missing some context about the choice. Be mindful of reputation risks, time costs and maintenance costs involved in changing the approach.

When you're asked to code something you don't agree with (including ethical issues) your options include: silently accept their approach, refuse to do their approach, propose an approach (with conversation or code) and gracefully accept the result, or find another job. Be aware that different organizations will react differently to those approaches. Under no circumstances should you fall into the trap of spending a week to convince the team to adopt a change that would save a week of costs.