The discussion centers on recent Postgres code reverts and what they signal about project quality. sammatilda congratulated the team for listening to the community, calling reverts painful but necessary. esafak framed the reversions as a strong endorsement of Postgres’s commitment to quality. swiftcoder acknowledged that reverts are frustrating for the feature author but argued that, for a foundational project like Postgres, frequent reverts are preferable. Paracompact tied the higher bar to AI-assisted code review, noting that the reverted changes predate that era. pak9rabid added a general note that there is always room for improvement.
Other commenters questioned causes and context. glouwbug asked whether misunderstandings, offloading to external tools, loss of care, incomplete design, or unrealistic timelines led to the reverts and suggested revisiting schedules. TZubiri wondered if ongoing development of new Postgres versions remains necessary. andsoitis said they didn’t grasp the article’s title, while card_zero called the headline “Until morale improves” inept; DangitBobby and LastTrain explained it’s a darkly humorous play on “the beatings will continue until morale improves.” jvanderbot pointed readers to further documentation on the topic.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.