We lost 54k GitHub stars
I really like this post.<p>While the author clearly feels bad about the fact that they&#x27;ve lost his community and that GitHub didn&#x27;t restore it (which is honestly what any of us would&#x27;ve felt under similar circumstances), they&#x27;re also focusing towards the future and using their personal experience as a parable all of us can learn from.<p>Lesson 1 on UI design I think is really important. I often think scary popup boxes are enough to get people to think about what they&#x27;re doing, but this example clearly demonstrates that what&#x27;s important is to use design not to scare (alone?), but to convey the information which makes a dangerous action dangerous as well. I also really like the fact that when the action isn&#x27;t dangerous, the distractions (&quot;Type this repo&#x27;s name&quot;, etc) just go away. It&#x27;s super intuitive, and (for a newbie designer like me) really helps build an intuition for various design principles put in action.<p>Lesson 2, which was to use soft deletes, is something I have more thoughts about. I assume that the cascading done on GitHub would be done on a FK constraint, but I&#x27;m not really sure how you&#x27;d do a &quot;cascading soft delete&quot; without making some kind of manual cascading logic? If anyone&#x27;s aware of a standard way to accomplish this, please do let me know. Of course, the best way may just be to simplify the model so they aren&#x27;t needed at all haha.<p>As designers and developers we&#x27;ve been given a chance to sharpen our toolkit. Thanks, HTTPie! You&#x27;ve gained a new star :)<p>Edit: Changed <i>GitHub couldn&#x27;t restore</i> to <i>GitHub didn&#x27;t restore</i>, as pointed out by @ncmncm (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31033758#31034195" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31033758#31034195</a>)