Scheming a mise-en-abîme in BQN(panadestein.github.io)

38 points by todsacerdoti 1 year ago | 0 comments

Tuple Space (2014)(wiki.c2.com)

98 points by paulgb 3 years ago | 50 comments

What Is Type-Level Programming?(blog.sulami.xyz)

54 points by bo0tzz 3 years ago | 45 comments

The soloists and populars of the software world(mihaiolteanu.me)

5 points by molteanu 3 years ago | 0 comments

Extending ts-Wolfram: dropping OOP, kernel/userspace interop, better printing(spakhm.com)

5 points by lioeters 10 months ago | 1 comments

Functional Programming with TypeScript's Type System(desislav.dev)

74 points by evolveyourmind 3 years ago | 30 comments

Notes apps are where ideas go to die (2022)(reproof.app)

598 points by pps 3 years ago | 182 comments

Blog post from Reproof arguing that notes apps act as insurance for the mind, letting ideas be forgotten, and that this is a good thing.

AI Made Writing Code Easier. It Made Being an Engineer Harder(ivanturkovic.com)

343 points by saikatsg 7 months ago | 242 comments

Blog post by Ivan Turkovic arguing that AI tools make producing code easier while making the broader job of being a software engineer harder.

AI tools are spotting errors in research papers(nature.com)

555 points by kgwgk 1 year ago | 200 comments

Nature news article on a growing movement using AI and large language models to detect errors in research papers, sparked by a flawed black plastic utensils study.

Updated practice for review articles and position papers in ArXiv CS category(blog.arxiv.org)

483 points by dw64 11 months ago | 228 comments

arXiv blog post announcing that its computer science category has updated moderation practice for review/survey articles and position papers.

ArXiv now offers papers in HTML format(blog.arxiv.org)

1130 points by programd 2 years ago | 296 comments

arXiv blog post announcing that research papers are now available in HTML format to improve accessibility for users with disabilities.

Writing a good design document(grantslatton.com)

509 points by kiyanwang 1 year ago | 130 comments

An essay by Grant Slatton giving advice on how to write a good software design document, prompted by a question from a friend on Twitter.