//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfilePosts
Loading...
This is the guy who asked Twitter staff to PRINT OUT their last 30 days of code for evaluation. We all know that more and longer code is better, right? 🤣🤣🤣🤣
Agile software development rests on one key principle: we ship code quickly in small chunks, so that we can learn where we got it wrong and fix it as fast as possible. But what happens when that loop is embedded in a system that makes it functionally impossible to report anything but total success?