peterstensmyr

Just brandur’s one. It’s good. Not very frequent. brandur.org somewhere.

Something very close to this example is in the fzf “advanced” documentation at https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...

Also 100% agree, the queue system as designed is almost unusable. I also raised a request on the community about it a bunch of years ago, but it was quickly closed. I’ll send another vote into the void on this one.

“The efficiency paradox”[0], saw a TEDx talk as part of agile training, and this really hammered in the fact that it’s more important to get stuff done than to be busy, or “efficient” with your time. If you focus on finishing a few things you’ll get more done than if you make sure you’re busy with something all the time.

This really has changed how I approach a lot of things in my everyday life, both inside and outside of work. Simple things like doing a load of washing here and there, and getting it done rather than trying to do a massive amount on the weekend, or washing some dishes as they come up rather than being efficient and washing all of them at the same time. In a work context, I guess it is more about not committing to too much work in a sprint, and ensuring there’s a bit of slack time so that multiple people can work on any items that get stuck, take more time than expected or similar. Developers helping out with testing where needed, ensuring quick code reviews, some extra pair programming and so on.

[0] https://www.youtube.com/watch?v=hGJpez7rvc0

Highly recommend “the wolf, the duck, and the mouse” which is written by Mac Barnett and illustrated by Jon Klassen. Absurd and funny.

I pivoted careers to software engineering. That wouldn’t have happened without HN. I actually make less money now, but I am much happier and have great work/life balance.

I generally agree with you, but I don’t think it’s unequivocally true. Facebook bet on the web/HTML5 for their iOS app, and Zuckerberg later referred to it as the company’s biggest mistake.

Their coworkers will tell you.

Same for me. As a previously solo half-developer, Gary's videos really drove home how to do best-practice development on a real project. He pushed TDD, separating concerns, and really diving into a single line of code and obsessing over getting it right. Thanks Gary! Sad that he's not making them any more, I really enjoyed the "Web framework from scratch" series. He's recently posted a new video about TypeScript types which is also very good: https://www.youtube.com/channel/UCDzfXZxesMP-LUICN-RWcbQ

They are describing Advance Wars, not chess.

Git has an option to ignore certain commits when doing a git blame, —ignore-revs. You can also point it to a file with —ignore-revs-file <file>. You can configure this per project with git config ignoreRevsFile .git-blame-ignore-revs. After doing this, you get nice diffs AND nice looking code. The price to pay is that every developer has to run one git command locally.

It wouldn’t be something provided by the CI tool, you’d have to write the test yourself. At the end of the day it’s just another test, albeit a more complex one than a standard unit test.

Fail verification in CI if the change doesn’t pass your checks. You can check anything, such as whether it has a duplicate name already in the codebase.

Have you tried the AdvancedNewFile plugin? It uses ctrl+alt+n by default, lets you create folders when you specify your new file and also has tab completion.