Tagged “programming”

programming book from 1962

Curious to know where they got with diffs - I have had problems with sonnet generating diffs, using LLM to apply it usually works but feels very wasteful

look inside
it’s Dijkstra’s algorithm

this is exactly the kind of thing people wanted computers for

Paper on arxiv

counterpoint

I like that part 3 is “Ray tracing for the rest of your life”

Seems effective but maybe annoying?..

Getting started with Lisp, along with some history.

Also worth checking out https://tryclojure.org/

long read, good tldr.

Programming resources someone has built up over years. Like a “getting started” guide but they kept adding to it

I love this. Glad he finally found it. And youtube video still sub-200 views.

Things get more complicated as they get more complex

How to talk to aliens (other people, who are very different)
Ask Butler

Rigorous Systems Design - Joseph Sifakus
The Design of Design - Fred Brooks

really really good explanation

About scaling culture rather than codebases

for whenever you next need to C

everything is complex

Don’t cut corners. Don’t blindly use other people’s configs, learn to read the help pages to look things up.

I like the idea of small containerised binaries more than this specific use for it.

lot of the typical “a computer made it so it can’t be art” takes in there that I really can’t get behind. Let them help make things!

suggestions for config of different types of PWA

approximate numbers for computer timing and sizes

Interesting area, and the discussion on whether it matters where the knowledge is stored.

Good article, and some other good recs in the comments

I don’t know if I am as blown away as Alex but this is very cool. Like machine pair programming with text.

His projects website is coooool. So many awesome things.

Great writeup on the many challenges posed by adding doors to a game. Also quite amazing seeing how much people can do with Unreal without having to type code.

Generational loss of a concept! Growing up mostly with phones means less understanding of file/folder structure. Either the OS deliberately tries to hide it from you (mobile OSs grouping files by type), or on computers where people mostly use Downloads folder and Desktop.

Dense, short summary of GC in Ruby. Relevant to work bookclub book

A lot of programmers get to that second 90%, get tired and bored and frustrated, and change jobs, or lose focus, or find excuses to procrastinate. There are a million ways not to finish a project, but there’s only one way to finish: Put your head down and grind it out until it’s done. Do that, and I promise you the programming world will be yours.

Love this term - this is exactly how I learn. Start by skipping over the details,
develop a coarse understanding, then refine your knowledge by learning about specific areas in more detail.

Great way to learn things, and to make exactly the thing you want.

HN discussion

I recently went on a short anti-reduce rant at work. Was in defence of forEach and local mutations, but I came to the conclusion that it’s mostly just because I don’t like reduce. Mostly when combined with fat arrow functions (which I also don’t particularly like).

Writing reduce() makes you look smart. Reading reduce makes you feel stupid.

The recent HTTP 203: Is reduce() bad? covers many of my issues, the tldr:

• the method signature is unpleasant
• most of the time you could use filter + map
• use reduce if you want a single value (e.g. sum)

reduce has some use-cases, but they are rarer than its usage suggests. Most of the time I favor filter or forEach.

DRY code is not always better code. Duplication is often better than shitty abstractions