Meteo from Poland is a great source for numerical weather forecast. Website is in english, but their forecast is mainly for Poland + Border regions of the neighbours. http://www.meteo.pl/index_en.php

If you know the coordinates, you can access a jpg-generated meteogram directly over the URL - example for Berlin: http://www.meteo.pl/um/metco/mgram_pict.php?ntype=0u&fdate=2...

One idea out of many (many have been mentioned by others already): I set linter to always report failure in CI when TODO or FIXME markers are found. So my PR never gets green until I fix them all. I place o lot of such markers if I know that I will not finish in a given focus block (doesn't have to be an end-of-business-day).

Looks very nice to get the first impression over a person. There is usually a lot of hints and information in the Internet about how to build such first-impression CV. However, EU companies (maybe elsewhere too?) often ask about second-impression CV with more technical details.

I search for a tool helping you to build your coding experience matrix. Imagine a chart looking similar to Github activity tiles or a spreadsheet, where on the x-axis you present time, and on the y-axis you place the coding languages or technologies that you have used in that time.

Such thing would help telling the interviewer, that you have 3 years of C++ experience, but your last project on this was in 2013. Anyone seen something like this?

edit: grammar & typos

Not so fancy, but a one-liner

  # Remove all local branches for which there is no remote
  git branch -r | awk '{print $1}' | egrep -v -f /dev/fd/0 <(git branch -vv | grep origin) | awk '{print $1}' | xargs git branch -D

> # Remove all local branches for which there is no remote

The merged branches part is missing.

I setup Github repos to automatically delete merged branches - in this case, the remote counterpart will be gone. There might be just the following missing to sync remove `origin/*` branches locally: `git fetch --prune`

Your newly created local branch might be gone as well.

Careful with "git branch -D" — it's a sharp knife.

Yes. See "Process Substitution" in "man bash". It works great, e.g. with diff (or meld):

  # diff -u <(echo $'one\ntwo') <(echo one)
  --- /dev/fd/63  2020-08-13 16:14:44.449379498 +0200
  +++ /dev/fd/62  2020-08-13 16:14:44.450379506 +0200
  @@ -1,2 +1 @@
   one
  -two

Gotcha. I wanted to know if it was POSIX compliant (it wasn't clear to me last time I looked it up).

< is a redirect operator, the out of the item on the right is redirected to the in of the item on the left; () are just grouping operators like math to ensure that bit is self contained inline for the parser.

That might be a way to remember what it does, but I don't think that's how it works. Try doing `echo <(ls)` to see how it differs. Or, from the manpage:

> Process substitution is supported on systems that support named pipes (FIFOs) or the /dev/fd method of naming open files. It takes the form of <(list) or >(list). The process list is run with its input or output connected to a FIFO or some file in /dev/fd. The name of this file is passed as an argument to the current command as the result of the expansion. If the >(list) form is used, writing to the file will provide input for list. If the <(list) form is used, the file passed as an argument should be read to obtain the output of list.

I skip reading articles with white background when in bed, because the screen light is too bright even at the lowest screen brightness setting. Fortunately HN client can display comments white on dark :)

Nice try with the: "You are currently {random} in the queue."

Did it work? :)

Please keep both versions up to date! Once you get the attention of recruiter (using your one-page Resume) then they usually ask for more information - longer CV, skills matrix, etc.

I invested some time to shorten my resume to exactly one page and now I get a bit irritated when people ask me for a longer version.

Thanks for your feedback. I will keep both and call the short one my resume and the long one my CV.

:norm(al) command Allows you to do some of the vim magic also on remote systems where you don't have all your plugins.

Example:

(1) Select block with `C-v`

(2) Hit colon `:`

(3) Write norm and enter any sequence as you would be in normal mode: `norm I# ` (prepend selection with a comment sign)

(4) Admire the result.

yes, awesome!!!