that's dramedy

tam tersi ses için artık “lossy” hikaye. 2025 yılındayız. bi lossless flac şarkı 50mb. instagram’da feed’i iki sayfa kaydırsan onun 10 katı data yiyodur. bugün sanatçının ürettiği eseri “nasılsa insan kulağı onu anlamıyo abi” diye bilerek ve isteyerek bozmak saçma. bırak ben istersem bozarım onu.

unfortunately, yes.

cool! i didn't read that one.

IIRC, fog creek (stackoveflow) also kept an “estimated time” vs “delivery time” and kept it as an accuracy factor per dev so they could assess better. i think that’s too much (and probably hostile) because estimation becomes something to fight over. good categorization, good deadlines, good devs.

for devs, that can depend on the architecture, size of components, but you can probably start with story cards. you can size the them up like number of pages like scrum story points. then you can measure a developer’s productivity with “points / time”.

so, developers are expected to finish a deliverable by a deadline like music composers, illustrators, CGI artists, writers. you can measure a developer’s performance by how fast they can deliver on a category of task. for writers, that can be “number of pages”, for illustrators, size+details?

movie production is a good analogue to software production. here you have all these artists, writers, creative types, making something out of thin air, that requires a lot of thinking and coordination. but, the movie industry engineered it into a managable, predictable, optimized process.

the youtube music experience on carplay