4 ms·
Making everything dull won't benefit the field. Sure we can remove every joke, every code comment that contains "FUCK", we can forbid commits that contain swea
by frenchman99 9y ago
Making everything dull won't benefit the field.
Sure we can remove every joke, every code comment that contains "FUCK", we can forbid commits that contain swear words, we can ask engineers to wear suits, we can remove animated GIFs from Slack and we can remove "418 I'm a teapot".
This kind of joke is what makes the job fun. You look at an implementation of an HTTP request and see "418 I'm a teapot", you smile for a second and keep working. That kind of fun contributes to happynness, increases psychological well-being and ends up contributing to long-term productivity.
In addition, removing the 418 code would break backwards compatibility. It will create way more problems than its availability does right now. This is the kind of thing you have to think about before-hand: add it and keep it, or don't add it. Now that we have a fun status code, we shouldn't add new ones. But removing the existing one is useless and damaging.
- wfunction 9y agoI suspect you might also enjoy this, which was also posted a while back: https://github.com/karolmajta/git-xd-hook https://github.com/karolmajta/git-xd-hook
- FrozenVoid 9y ago418 can be reused as "i'm an IoT device without web interface"
- SmallDeadGuy 9y agoThere are also many, many, many 4XX status codes which are free. Any of those could be used for that, why (possibly) break compatibility with previous frameworks when not necessary?
- FrozenVoid 9y agoThe teapot is essentially an early IoT device and creating extra statuses is extra work. Just a minor change in "teapot code" without rewriting standards and software.
- guilhas 9y agoSo sys admins all around the world will start receiving 418 teapot warnings from legacy systems