Mastodawn

@b0rk What I'd _really_ like is not more examples, but a volume of commentary and critique. Pauline Kael and Siskel & Ebert helped two generations of actors, writers, and directors be better tomorrow by taking apart what had been created yesterday and explaining how things worked (or didn't). We definitely need more model implementations, but I think we also need people to analyze the ones we have so that we can make the next ones better.

and in answer to a DM: if I thought I was insightful enough to write it, I would have done it by now. I haven't been shy in the past about putting forward opinions in areas where I'm not an expert (e.g., http://teachtogether.tech/), but this one's beyond me.

Teaching Tech Together

This is one of my dissatisfactions with both software engineering and computing education: neither thinks that criticism in the sense of literary, music, or film criticism is something they should do or reward. Twenty years on, most books and courses on software architecture & software design still don't describe actual, specific systems in pedagogically-useful detail https://third-bit.com/sdxjs/introduction/#introduction-history

Software Design by Example: Introduction

@b0rk "Software Design by Example" (in JavaScript) is free to read online at https://third-bit.com/sdxjs/, and I hope to have the Python version up for beta readers by August.

Software Design by Example

Julia Evans May 14, 2023

what are some other tutorials for implementing a toy version of a hard thing in a short amount of time? Like https://implement-dns.wizardzines.com or https://raytracing.github.io

I’m especially interested in the “in a short amount of time” aspect, I think nand2tetris is extremely cool but you definitely can’t do it in 3 days.

If possible I'd love to hear about a project you personally did and how long it took you.

Implement DNS in a weekend

And also failure is key part of reverse engineering too

Because failure reduces the complexity space

Exactly the thing our exams btw discourage and penalize

"To Engineer Is Human: The Role of Failure in Successful Design by Henry Petroski argues that engineering failures are crucial for progress, as they reveal flaws and lead to innovation, contrasting with the common perception that success is the only measure.

A key concept is that the "exact lifetime of a part, a machine, or a structure is known only after it has broken," and predicting this lifetime is a critical part of design"

RE: https://tilde.zone/@kirch/116346993593163889

Wow

To Engineer is Human: The Role of Failure in Successful Design (1985) by Henry Petroski

https://www.goodreads.com/en/book/show/271495.To_Engineer_Is_Human