Ain't nobody got time for unit tests

Content Could there be a mistake in my code? No, it's the unit tests that are wrong.

The universal developer solution to compiler warnings: just put a decorative plant in front of the screen! Who needs to fix those 43 warnings when strategic foliage placement solves the problem instantly? This is basically the software equivalent of putting tape over your check engine light. Sure, your code might explode in production, but at least your desk looks nicer!

Content References 418 I'm a teapol Y Filter 414 URI Too Long 415 Unsupported Media Type 416 Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Content 423 Locked English (US) 418 I'm a teapot The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffeetea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014. Some websites use this response for requests they do not wish to handle, such as automated queries. Status 418 I'm a teapot Specifications

Content How To Tell HTML from HTML5 Try it out on Internet Explorer, Did it work? No? It's HIMLS.

Content You when the DB code you were using for testing makes it to production. You the moment you realize it's still named FuckMyLife2169

Content When a Developer Finds a Bug VS When a Tester Finds a Bug Bug Let's hide