• 0 Posts
  • 42 Comments
Joined 2 months ago
cake
Cake day: July 6th, 2024

help-circle





  • At my job, we have an error code that is similar to this. On the frontend, it’s just like error 123.

    But in our internal error logs, it’s because the user submitted their credit card, didnt fully confirm, press back, removed all the items out of their cart, removed their credit card, then found their way back to the submit button through the browser history and attempted to submit without a card or a cart. Nothing would submit and no error was shown, but it was UI error.

    It’s super convoluted. And we absolutely wanted to shoot the tester who gave us this use case.







  • I’m not as much vitriol as others about Clean Code, but I will argue that engineers who preach the book as some sort of scripture are really obnoxious.

    I love the Single Responsibility Principle, in theory.

    What I don’t like is when devs try to refactor everything to that idea to achieve “Clean Code”. I’ve seen devs over-architect a solution, turning one function into many, because they don’t want to break that rule. Then point to this book as to WHY their code is now 20x longer than it needs to be.

    It also doesn’t help that every recommendation about good programming books include this.

    It’s like recommending a Fitness book from the 70s - information made sense at the time, but new research has made a lot of the advice questionable.

    My main issue is the whole “Uncle Bob” persona. Robert C Martin is sexist and a racist, and has been uninvited by conferences. We don’t need that type of toxicity in the industry.