Skip to content
Hallway
0:00 / 0:00

#caseymuratori#apidesign#reusablecomponents

Designing and Evaluating Reusable Components - 2004

Casey Muratori

12K subscribers • 2 videos on Hallway

YouTube
  • Recommended by 3 people: 3 on Lobsters.
  • A classic. People kept recommending it from 2016 to 2023.
  • Presented by Casey Muratori
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

99K views12 years ago3 recommendations

Software designProgramming languagesAPI designDesign patternsC++

Casey Muratori presents a framework for designing and evaluating APIs and reusable software components, emphasizing usability and simplicity.

For more information, see caseymuratori.com/blog_0024

Why it's here

3 people recommend this

What people say. Engineers recommend this talk as a classic and highly influential guide to API design and component usability.

dbremneron Lobsters • Recommends

Designing and Evaluating Reusable Components (2004)
3View on Lobsters

friendlysockon Lobsters • Recommends

Designing and Evaluating Reusable Components
3View on Lobsters

pushcxon Lobsters • Recommends

Designing and Evaluating Reusable Components (2004)
2View on Lobsters

u/N-R-Kin r/C_Programming • Mentions

On “Best practices for library supporting custom allocators?”

> Of course it really depends on how low-level/high-level you want your library to be It also depends on the size/scope of the library. If it's just a small library with 3~4 functions, then there's rarely any need to provide a "high-level" interface since the "low-level" interface is small already. On the other hand, for bigger libraries, it makes sense to provide *both* low and high level interfaces *and* making sure that the transition between them is smooth. This allows for people to use the "high" level interfaces to quickly get going for prototyping purposes, but then smoothly convert over the low level interface when they need more control. Recommended watch: ["Designing and Evaluat…
2View on Reddit

u/DreamerSleeperin r/C_Programming • Mentions

On “what should be avoided when designing an API?”

Casey Muratori has a decent talk on API design on YouTube here link to this video
2View on Reddit

u/N-R-Kin r/C_Programming • Mentions

On “techniques for programming with no runtime memory allocations”

…is error-prone and inefficient, the user might be using a custom allocator that can manage memory in groupgroup instead. And so by asking the user for memory the library can fit a wider variety of use-cases and be more reuseable. lib: https://old.reddit.com/r/C_Programming/comments/14fh47s/a_couple_freestanding_parsers_in_c99/ lib-reuse: link to this video group: link to this video…
1View on Reddit