Tagged “code”

for whenever you next need to C

this was like reading css from a different person

things to make you feel better about your own codebase

Mentioned in Don't be that open source user

Me too, buddy. Me too

Jupyter notebook by Peter Norvig working through some prob problems.

Good one to work through.

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

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.

Generally agree. Mainly tracking file creation/history gets a bit annoying (especially when files are moved/renamed/split up). But most of the time I don't think it particularly matters.

Also some good tips like ingorerevs in hackernews comments.

I don't have strong opinion on it one way or the other. But I think we can all agree that exploitative game mechanics do suck.

Twitter thread that apparently motivated the removal.

Found my first contributions to Zero-K! Was looking for commits but this predated the git repo

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

Honestly, skip all of the courses. Pick a problem to solve, start googling for common models that are used to solve the problem, then go on github, find code that solves that problem or a similar one

There is mixed consensus on this. But copy-pasting snippets to solve my problems is how I've learned to program so far; why should ML be any different.

Yet another vim alternative to try

This is glorious

Massive list of tools and SaaSes, some free, some with free quotas listed.

Refreshingly professional. My usual favourite commits are either Developers Swearing or awful puns.

The ludicrous complexity of everyday activities is never as obvious as when you ary to add it to a game.