remember to always enable auto-save 🙃

Ah, the quarterly ritual of revisiting your own code from the distant past. First comes the shock and horror. "Why would anyone write this garbage?" Then the dawning realization that you are the criminal mastermind behind this atrocity. Twenty years in this industry and I still leave cryptic comments like "fix this later" and "temporary solution" that somehow survive three product releases. The best documentation is always that moment of clarity in the fourth panel when you finally remember what sleep-deprived, deadline-haunted version of yourself thought this spaghetti nightmare was a good idea.

Content SOFTWARE DEVELOPMENT PROCESS O. I can't fix this 1. Crisis of confidence 2. Questions career 3. Questions life 4. Oh it was a typo, cool

Content Me coding and debugging Me writing e-mails

Content The api always returns a 200: OK message even for wrong requests, however it gives an error message out with the exact reason should something be wrong. Error layout: "error": f'Error reasor

Content P . S 320 Ben.m.wikipedia.orgwikiR. B WIKIPEDIA Q Rubber duck debugging Article Talk XA In software engineering, rubber duck debugging is a method of debugging code by articulating a problem in spoken or written natural language. The name is a reference to a story in the book The Pragmatic Programmer in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by- line, to the duck.! Many other terms exist for this technique, often involving different (usually) inanimate objects, or pets such as a dog or a cat. A rubber duck in use by a developer to aid code review

Content Beth DeBold elizaaudacis My hotel room in London comes with a duck and like...I don't need a duck, but the card says "this duck is yours to take home and join you on your future travels" and yes I am fully aware that this is manipulative capitalism at its finest but I CAN'T JUST LEAVE EDWIN HELLO, I'M EDWIN