HN user

HerrMonnezza

1,585 karma
Posts90
Comments114
View on HN
maryrosecook.com 2y ago

Little Lisp Interpreter (2014)

HerrMonnezza
46pts4
jameshfisher.com 2y ago

The golden rule of PR reviews

HerrMonnezza
1pts1
www.theatlantic.com 2y ago

The 67-Hour Rule. Married couples are working as much as ever.

HerrMonnezza
1pts0
siderea.dreamwidth.org 2y ago

Up the Slope: On Mastodon and What Social Engineering Should Be

HerrMonnezza
3pts0
theconversation.com 2y ago

The enduring wartime spirit that powers classic Christmas songs

HerrMonnezza
1pts0
everything.intellectronica.net 2y ago

The One Best Programming Language, One Year On

HerrMonnezza
2pts1
medium.com 3y ago

Develop Your Custom AI on Azure Using OpenAI and the Cheshire Cat

HerrMonnezza
2pts0
newspeaklanguage.org 3y ago

The Newspeak Programming Language

HerrMonnezza
2pts0
dvc.org 3y ago

Data Version Control

HerrMonnezza
161pts59
neal.fun 4y ago

Universe Forecast

HerrMonnezza
1pts0
jaydaigle.net 4y ago

Hypothesis Testing and its Discontents, Part 1: How is it Supposed to Work?

HerrMonnezza
1pts0
en.wikipedia.org 4y ago

Space-Filling Curve

HerrMonnezza
5pts0
www.zimbu.org 4y ago

The Zimbu Programming Language

HerrMonnezza
1pts0
betterexplained.com 4y ago

What to know about the stock market (2007)

HerrMonnezza
394pts361
www.blog.google 4y ago

Making Open Source software safer and more secure

HerrMonnezza
2pts0
pythonrepo.com 4y ago

Lambdex: Write multi-line anonymous function expression in Python

HerrMonnezza
2pts0
nyxt.atlas.engineer 4y ago

Towards Open Source Sustainability

HerrMonnezza
1pts0
github.com 4y ago

Wasp: WASM Programming Language

HerrMonnezza
73pts21
www.washingtonpost.com 4y ago

Why is everyone quitting, and how do I know whether it’s time to leave my job?

HerrMonnezza
7pts0
sha-mbles.github.io 4y ago

SHA-1 Is a Shambles

HerrMonnezza
1pts0
cloud.google.com 5y ago

The new Google Cloud region in Warsaw is open

HerrMonnezza
2pts0
github.com 5y ago

ZickStandardLisp: A Lisp Evaluator in Lisp

HerrMonnezza
2pts0
cloud.google.com 5y ago

Google Workspace

HerrMonnezza
58pts15
astrobiology.com 5y ago

Phosphine Detected in the Atmosphere of Venus – An Indicator of Possible Life?

HerrMonnezza
1pts0
medium.com 6y ago

Why Some Developers Are 20x More Efficient Than Average

HerrMonnezza
1pts0
github.com 6y ago

RLGL: Git-centric policy mgmt and enforcement tool to accelerate CI/CD pipelines

HerrMonnezza
2pts0
norvig.com 6y ago

A Retrospective on "Paradigms of Artificial Intelligence Programming"

HerrMonnezza
3pts0
users.rcn.com 6y ago

The Lunar Programming Language

HerrMonnezza
27pts1
jvns.ca 6y ago

PaperWM: Tiled Window Management for Gnome

HerrMonnezza
3pts0
www.businessinsider.com 6y ago

A look at landing a tech job at one of Wall Street's largest trading firms

HerrMonnezza
1pts0

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.

Why GitHub won 2 years ago

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).

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?

    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.)

I find that the experience of writing (La)TeX depends a lot on what you are using to write it. For me, Emacs' AuC-TeX [1] is nearly perfect: it has shortcuts and autocompletion for almost all the environment names and commands, inline preview, BibTeX searches (via RefTeX), and a number of other minor features that make it easy to write LaTeX. Honestly, I wish that other text-writing modes (like markdown-mode) would implement the interface and functionality of AuC-TeX and not the other way round.

As for the syntax: I love Markdown for writing very simple text content, but as soon as you need to do something just a little more complicated it becomes awkward (e.g., table entries that span multiple paragraphs) and some task are simply impossible (e.g. referencing a list item by label value, the way you do it with TeX's `\label` and `\ref`). The programmability of TeX-based systems is actually a great thing that lets you write shorter documents and push many aesthetics decisions to a `.sty` file (e.g., you can at any time change your mind on how `\vector{u}` should be rendered).

[1] https://www.gnu.org/software/auctex/

What you lose on arxiv is peer review.

Or, instead, you get a much larger audience reviewing your article, instead of the 2 to 4 reviewers involved in the paper publishing process :-)

You can get comments from critical and interested readers, you upload a new version of the paper to arXiv, and repeat the process until the article is ready for submission/publishing.

In other words: I think that an article on arXiv (on average and as a whole, individual articles may be exceptional) is subject to much wider and more extensive scrutiny and verification than the average article during the paper publication process.

From the article:

But moderators frequently intervene, delaying posting by days or weeks, reclassifying papers or even outright rejecting submissions.

Definitely not my experience. I haven't posted to arXiv in a while now, but I wasn't even aware a moderation queue exists -- none of my papers were delayed, reclassified, or other...

EDIT: I see the article provides a few examples, but then they also provide numbers: "At arXiv, roughly 6 percent of submissions receive a hold, and about 2 percent are rejected." -- 8% of heavy-handed moderation intervention wouldn't qualify as "frequently" IMHO.

We should also not forget that a lot of maths is spoken (in classes and seminars) so there the distinction between, say, \theta and \vartheta would be lost was they are pronounced the same...