design

aposd-vs-clean-code/README.md at Main · Johnousterhout/aposd-vs-clean-code

Discussion between Robert “Uncle Bob” Martin and John Ousterhout on software design principles in “aposd-vs-clean-code.” Key disagreements focus on method length, comments, and test-driven development. John emphasizes reducing complexity for easier understanding, while Bob champions small functions. They debate the risks of over-decomposition, balancing function size with clarity. They analyze the PrimeGenerator class for its design flaws, particularly method entanglement. Both find the other's approach lacking but agree on the challenge of maintaining code clarity amidst complexity. Ultimately, they encourage a careful balance between decomposition and comprehension in software design.

https://github.com/johnousterhout/aposd-vs-clean-code/blob/main/README.md

When Imperfect Systems Are Good, Actually: Bluesky’s Lossy Timelines

Imperfect systems can be beneficial in tech design, exemplified by Bluesky's timeline architecture. Achieving perfect consistency, availability, and low latency simultaneously is infeasible. Bluesky's “lossy timelines” decrease write consistency to enhance performance, addressing challenges posed by high user activity that can create “hot shards.” By introducing a mechanism that probabilistically limits writes based on user follow counts, Bluesky has improved scalability and reduced the time needed for timeline updates from minutes to seconds, demonstrating that embracing imperfection can enhance system throughput.

https://jazco.dev/2025/02/19/imperfection/

BentoGrid.js

BentoGrid.js: Smart library for responsive grid layouts, auto-positioning elements based on size, just 2KB, no dependencies.

Installation: Via HTML or npm.

Usage: Define elements with data-bento for layout; fillers can fill gaps automatically or be styled.

Config: Customize target, cell gaps, aspect ratios, responsive breakpoints, and more.

https://bentogrid.mariohamann.com/

Scroll to Top