HerrMonnezza

Interesting remarks, thanks!

When discussing remote vs non-remote with a colleague some time ago over lunch, he mentioned that "remote is an extreme version of yourself", so those inclined to slack off will slack off way more to the point of being unproductive, and those inclined to work longer hours will eventually just spend all their time working... Maybe over-simplified but I think he was onto something.

arXiv replaces any URL in the text of the abstract with a link with text "this http url"; it seems the authors did not know this and just embedded a bare URL in their abstract.

One thing that Git and the other DVCS's massively improved over Subversion is that commits are local, and you only need to talk to a remote endpoint when you push/pull. In Subversion, every commit would require uploading changes to the repository server, which encouraged larger commits (to amortize the overhead).

`s6-sudo` [1] is an alternative that does exactly this: connects to a running privileged daemon and asks it to execute a command.

[1]: https://skarnet.org/software/s6/s6-sudo.html

I'm curious: why the `printf '%s\n' "$(pwd -P)"` ? wouldn't just `pwd -P` achieve the same?

It really depends on what your current and wanted roles are... When it happened to me, I would have had to interview again because there were no other roles in my career ladder left in town.

IIRC, Linux' ext2/3/4 support an 'a' attribute that make a file append-only.

I guess they redirect you to a different IP than they publish in the public DNS?

I agree, but how is this different from polls, fidelity programs at department stores, statistics on various topics, etc - all of which have existed for decades?

So Ur- comes from Urdeutsch? :-)

Impressive! But one stated goal of the software is to be compatible with STOS and AMOS, so one has to use an 80s BASIC for programming AOZ.

    Maybe we should establish a sort of expert-led central archive of rock-solid, battle-tested C libs/functions/snippets that one can trust ?

GNUlib [1], albeit marketed as a "portability library", in fact shares a lot of that goal and includes data structure implementation, OS interfaces, etc. A couple of excerpts from the docs:

* "Gnulib is intended to be the canonical source for most of the important “portability” and/or common files for GNU projects. These are files intended to be shared at the source level" [3]

* "We develop and maintain a testsuite for Gnulib. The goal is to have a 100% firm interface so that maintainers can feel free to update to the code in git at any time and know that their application will not break." [3]

[1]: https://www.gnu.org/software/gnulib/manual/html_node/index.h...

[2]: https://www.gnu.org/software/gnulib/manual/html_node/Gnulib-...

[3]: https://www.gnu.org/software/gnulib/manual/html_node/High-Qu...

(There should be a 2nd part to your post, where you send a very good report to the colleagues, and note their reaction.)

Julia [1] has macros (not necessarily based on s-exprs though you can use s-exprs if you want) and a REPL [2] with some decent tooling (e.g., [3] [4])

[1]: http://julialang.org/ [2]: https://www.youtube.com/watch?v=CRiD12Y75wM [3]: https://timholy.github.io/Revise.jl/stable/ [4]: https://kristofferc.github.io/OhMyREPL.jl/latest/

`empty` is a similar tool.

Source (clone of the original SF repo): https://github.com/ierton/empty

Man page: http://manpages.ubuntu.com/manpages/trusty/man1/empty.1.html

Might be worth a "Show HN" of its own...