To the Bored All Things Are Boring(comment.org)

58 points by yamrzou 2 years ago | 51 comments

Apple's Software Quality Crisis(eliseomartelli.it)

1052 points by ajdude 1 year ago | 1028 comments

Blog post by Eliseo Martelli arguing that Apple's software quality has declined, citing problems with his iPad Air M2 despite its premium hardware.

Mea Culpa – Dark Hours(blog.terrygodier.com)

568 points by satvikpendem 2 months ago | 255 comments

Terry Godier's blog post apologizing for problems with Dark Hours, a website he launched to show what can be seen in the night sky.

Any Technology Indistinguishable from Magic Is Hiding Something(fromjason.xyz)

68 points by jayveeone 2 years ago | 10 comments

How do we stop Meta in 2024? We fix the information loop(fromjason.xyz)

59 points by moritzruth 2 years ago | 69 comments

Why paid masterminds are mental masturbation(jimclair.com)

42 points by _trackno5 3 years ago | 34 comments

Fuck it, make it anyway(joelotter.com)

504 points by JayOtter 1 month ago | 495 comments

A personal blog essay by indie game developer Joel Auterson encouraging people to make their creative projects anyway despite doubts.

I wasted weeks hand optimizing assembly because I benchmarked on random data(vidarholen.net)

376 points by thunderbong 1 year ago | 148 comments

Blog post recounting how the author spent weeks hand-optimizing assembly for a Java platform, only to find the gains came from benchmarking on unrealistic random data.

Some things just take time(lucumr.pocoo.org)

788 points by vaylian 7 months ago | 250 comments

Blog essay by Armin Ronacher arguing that some valuable things, like mature trees or established software and communities, can only be achieved through time.

I started programming when I was 7. I'm 50 now and the thing I loved has changed(jamesdrandall.com)

705 points by jamesrandall 8 months ago | 556 comments

Personal essay by a 50-year-old developer who began coding BASIC in 1983, reflecting on how the craft of programming has changed, including with AI.

Nobody ever gets credit for fixing problems that never happened (2001) [pdf](web.mit.edu)

881 points by Jtsummers 2 years ago | 390 comments

PDF of Repenning and Sterman's 2001 California Management Review paper on why organizations underinvest in process improvement and capability building.

Nobody ever gets credit for fixing problems that never happened (2001) [pdf](web.mit.edu)

722 points by sam_bristow 4 months ago | 243 comments

A 2001 California Management Review paper by Nelson Repenning and John Sterman on why process improvement programs often fail and how to create and sustain them.