Editor guide

Production releases on a Friday evening 😐


Doing this today. Yeah...


Thanks! We just happened to find a somewhat-critical error on Google Analytics and decided to pull the trigger ASAP to get it fixed. Shouldn't be too traumatic of a deploy :)


Hope you have some good CI/CD for that :-)

Yup! Jenkins rules :)

It didn't go as well as it could (some repo drama), but we managed to get stuff done. Yay!

Awesome! Late night deploys suck, we have to in some cases to reduce user downtime. We had to recently migrate an entire AWS VPN - business team was "shipping their pants". It went fine with minimal downtime. Which leads to a question, when should Developers NOT tell business about some changes? I have found that sometimes they make things worse off than they should be.


Been there, done that. Leave before they ask you to work weekends.


If they are asking, you don't need to say yes. If you need to get out the building before this, then they are not asking you, in which case you need to LEAVE THAT JOB!


I think the goal should be to get to the place where this isn't a big deal. Testing in production should be a thing. That's not a trolling comment, and I'm dead serious.

Get to where you can deploy multiple times a day, every day, all day.

For reference, read stuff by Charity Majors about observability.


Don't forget, "when a critical resource is starting two weeks' PTO the next day".


That's bringing it to a whole other level 😂


😆😆😆😆😆 great


I think this heavily depends on the risk and impact of the deploy


I definitely agree with you here, but on Friday evenings people can often get distracted with weekend plans. Then if something goes wrong with a deployment, asking people to stay late and resolve the issues can be hard (for everyone involved).

This can be challenging, and its why our team generally tries to avoid this (but it does happen sometimes).


Internet Explorer


A toxic unsupportive work environment.


Hopping into an already existing project that has no tests.


I understand the dread and I've felt it. I know I'm weird but writing tests or reverse engineering something is a great way to learn how something works :D

You shouldn't have to but still...

See it as an exploration adventure :D


One Word: Databases :D

So important, yet so dangerous if you're not good at them.


You're the second person to mention this in a few days. We (as in devs who don't share this dread) need to be better at communicating how to use these DBs because they are so important as you said 😭


I’m ok at them after a couple years having to manage some, but with legacy DBs with bad tooling I get very nervous ;)


Pushing/releasing sensitive information/data 😰


I'm not sure if a CodeClimate plugin could check for this.
I do know that all Lambda Security products will scan for sensitive information but then you have to go serverless and pay for said service.

I like how Amazon Macie can detect (Personally identifiable information) PII and api credentials.
I guess if you're CI/CD is CodePipeline and CodeBuild which places artifacts (zip folders) of your codebase in S3 that maybe Macie could detect these issues. Uncertain if it can peak into zips.


Maintaining legacy code that someone else wrote years ago.


Especially if "someone" is a younger, less experienced version of yourself


I can relate to that, on my first "actual" full-time job, I had to work on code that was more than a decade old, written by someone who didn't believe in commenting code.


Getting assigned to a project with an incredible level of tech debt...


...bad managment that decides to shift focus 10 times per day.



...bad managment that decides to shift focus 10 times per day.

That's so exhausting :(

  1. Comments that add no value.
  2. Comments that could easily be expressed with meaningful variable/function names
  3. Comments that are out of date and are misleading

Inheriting a frontend that was a spaghetti of jQuery, Angular, jQuery UI, Bootstrap 2 and Bootstrap 3. It was a some pages SPA and some pages not, and globals everywhere. CSS was a hot mess.

My biggest accomplishments in that project were refactoring out Bootstrap 2, and making the JavaScript code modular the old-school way (this was before ES6) using Addy Osmani's JavaScript Design Patterns.


Omg. This sounds like something FBI should use as a torturing interrogation tactics...😱

fun someUngodlyMess() {

First refactoring would be to remove this comment.


Same. You can't put that there and expect me not to touch it. I can't ignore a challenge like that.

The comment is a warning from someone who tried to refactor.


I saw different variants of this, usually:

somethingNobodyCanUnderstand(); // DO NOT CHANGE THIS

I die a little inside when I see this shit


walking into a code base with:

  • no test
  • no documentation
  • no types
  • no comments
  • no code quality
  • no automation
  • high complexity
  • high risk
  • no dev/test/stage environment

I hope no poor soul ever gets the check to all those boxes, but I'm sure there are people who have!


I have a project that checks all but two of those boxes. Thankfully I have multiple environments and some build automation


My own code from 24 months ago 😱


That one gets me every time too! 😂


Event-driven architectures.

It's basically no different from a goto statement, and we've known for a long time that gotos are considered harmful. Applications which use events to drive data flow and logic become impossible to navigate, which makes them impossible to maintain.


I have a feeling there is a lot more to be said about this, and I think you maybe right and those architectures should be considered as anti-patterns. The biggest problem I find with event-driven stuff is how easy it is to lose track of what is happening, and how easy it is to introduce circular event triggering. I think the cleaner architecture would mean that it would be actually impossible to introduce a circular dependency. For example, it could be done similarly to the creation of objects. If you have classes:

class A {
    b: B;
    constructor(b: B) {
        this.b = b;

class B {
    a: A;
    constructor(a: A) {
        this.a = a;

It would be impossible to have a circular dependency such as above, because the creation of A's instance requires a B's instance, while the creation of B's instance requires an A's instance. So, you'll not be able to successfully run

let a = new A(); // Error - need an instance of B as the 1st argument
let b = new B(a);

I think a similar way of thinking should be applied to events.


Wow. Want to hear more on this. I believe, not the architecture but the worst implementation which is harmful.
Event driven architecture works for many use cases.


You're exactly right, events by themselves are not bad, and can be very useful in large, modular codebases. But a bad implementation will only get worse over time, and the nature of it makes it nearly impossible to recover from beyond a certain point.

The problem is when the app is driven by events. When one event triggers another event, which triggers another, etc. One of the most extreme examples of this is WordPress, where in it's internals methods are rarely called on their own. They mostly call each other through events, which, while they can be augmented and overridden, means tools like static analyzers can't help, you don't have good stack traces, exception handling gets confusing. As a result, you really can't refactor that code anymore, since you can't really figure out who's all listening for the event anymore. But I've personally worked with many other examples in Android, JS, and PHP.

The alternative is to only use events as a reaction. Keep the logical path in normal function calls, send events as "notifications" instead, to broadcast what you just did or what you're about to do, without altering the execution flow.

Awesome point. Totally agree

  • publishing secrets to the internet (which I did a few days ago...luckily NPM flagged it and disabled it)
  • losing production data 😱😱😱😱
  • shitty co-workers/work environment (I'm lucky to have worked at an awesome place for years!)

Management that thinks developing software is not a difficult task.


I feel you, but if you think that's bad, work as a designer, where everyone thinks design is about moving pixels around the screen 😄. Or everybody thinks that "I don't like it or I like that more" is good design feedback. I could continue, but not today 😆


Making a mistake that costs a whole heap of money. I've done it twice in my career - it's never entirely my fault but I've played a part. I'd really prefer not to do it again!


Its used to be merge conflicts, but nowadays I'd say it's when I can't find the freaking logs. I get real mad. haha


CONFLICTS, I just hate them. Especially if I can't reach the developer I am conflicting with.


Not being able to code anymore. I'm serious, there are very few things I enjoy more and people actually pay me to do it.


Unrecoverable database corruption including all the backups. Bye-bye business.


Integration and its best friend: "It works on my computer!"


Taking a risk to improve some piece of code that has immense business value, and the thought of failing.

We have an Angular app that has been around for a long time. We are making plans to introduce ngrx to some of our core services so they cache data and improve our developer experience.

I'm the one person on our team with the most knowledge of ngrx, and its daunting.


I know the feeling


My imposter syndrome stopping me from trying new things


The possibility of a bug I don't know about silently altering or losing data across weeks to months to years without obvious failures or corruption.


Upgrading framework versions...


Loosing my passion for coding (and computing in general).

Coding is really a passion to me but since I started working as professional dev I almost never code at home and I don't enjoy my professional projects as much as I used to enjoy the personal ones.

I sometimes feel like I'm wasting away my passion by having turned it into a job.


With the obvious proportion of the case, one of thing that makes me lose sleep is writing/reading code that does not express the intent, I call this: code which talks about code VS code which talks about business


When your engineering team doing such an amazing work and a non technical person calling out your team velocity isn't consistent!


It happened to me not to long ago but using a Mongo function to clean a database and then wiping out all of the data luckily Mongo has an import function and we had a backup!


Having a language that you've invested a lot of time into, become obsolete


I hate the following scenario (which I've been part of many times in the past):

them: Here's a new urgent project. How long will it take to build it?

me: 2 weeks for a hack, 3 weeks to get it right. When is it needed?

them: We've already sold it, billing has gone out and we promised to deliver it last Thursday.

me: So, what is my drop-dead delivery date?

them: Last Thursday.


changes of business processes on last minute.


Unrealistic time expectations for work being done. Turns something I love into something I hate.


Hardware flaws that present as intermittent, inexplicable errors.

Basically, errors coming from below the lowest level I can inspect.


Upstream breakage {yells at cloud}


Screwing up authentication and leaking data.


Deadlines and bad project spec.


Hmm. That's a tough one. How do I choose? Well, if I had to pick just one it would have to be bees. As a coder, bees are my worst nightmare. Bees. 🐝🐝🐝


That tomorrow I won't remember anything about code.


That I'm not as good of a coder as I think I am, but no one will tell me or point me in the right direction.


Writing something that accidentally gets someone actually hurt, or worse.


The SQL query to update user preferences for over 20,000 users in a production environment because you found a security flaw with something being saved in the database


Intermittent Bug, that's creepy shit


Critical, process-blocking bug that I cannot reproduce in local...


Spending 3 hours trying to find a bug only to find out (after checking stack overflow) that its like one line of code and super easy fix.