50 There Are Two Types of People: Developer Edition

There are two types of developers: those who write tests, and those who will.

There are two types of developers: those who review the pull request, and those who type "LGTM" in four seconds.

There are two types of developers: those who say "it's not a bug, it's a feature," and those who have to document the feature.

There are two types of developers: those who write documentation, and those who are the documentation.

There are two types of developers: those who use a debugger, and those who claim they use a debugger.

There are two types of developers: those who test in production, and those who lie about it.

There are two types of developers: those who name the branch clearly, and those with a branch called final-fix-2-real.

There are two types of developers: those who finish the feature, and those who refactor the whole codebase to avoid finishing the feature.

There are two types of developers: those who blame the framework, and those who wrote the framework and now blame the users.

There are two types of developers: those who said this would take an afternoon, and those reading the postmortem.

There are two types of developers: those who read the stack trace, and those who scroll to the red part and guess.

There are two types of developers: those who understand JavaScript's "this," and liars.

There are two types of developers: those who delete dead code, and those who commented it out "just in case" in 2017.

There are two types of developers: those who write small commits, and those whose one commit is titled "stuff."

There are two types of developers: those who handle the promise rejection, and those whose console is a wall of red.

There are two types of developers: those who estimate two days and ship in two weeks, and that is the same person.

There are two types of developers: those who reproduce the bug, and those who close it "cannot reproduce" and feel wonderful.

There are two types of developers: those who write a comment explaining why, and those who explain what, which we can already see.

There are two types of developers: those who push to a feature branch, and those who push to main and apologize in the channel.

There are two types of developers: those who catch the exception, and those who catch it and swallow it silently like a crime.

There are two types of developers: those who say "quick fix," and those merging it on a Friday at 4:55.

There are two types of developers: those who profile before optimizing, and those who rewrote it in Rust on a hunch.

There are two types of developers: those who write the README, and those who say the code is self-documenting about a function named x.

There are two types of developers: those whose commit history reads like a story, and those whose history is "fix," "fix again," "actually fix."

There are two types of developers: those who validate input, and those who learned about emojis in the database the hard way.

There are two types of developers: those who upgrade the dependency, and those who read the changelog and chose to live in fear.

There are two types of developers: those who add the loading state, and those whose users stare at a frozen screen and wonder.

There are two types of developers: those who name things well, and those with a function called doStuff2.

There are two types of developers: those who handle time zones, and those whose calendar shows the meeting twice.

There are two types of developers: those who keep the build green, and those who say "the test is flaky" with no evidence.

There are two types of developers: those who write the migration carefully, and those who run it on prod to see what happens.

There are two types of developers: those who reach for a library, and those who reinvent it badly and call it learning.

There are two types of developers: those who left at 5, and those who said "let me just fix one thing" at 4:58.

There are two types of developers: those who use feature flags, and those who deploy on Friday and pray.

There are two types of developers: those who narrate the bug to a rubber duck and solve it, and those who book a meeting.

There are two types of developers: those who keep dependencies minimal, and those whose node_modules has its own gravity.

There are two types of developers: those who understand the regex they wrote, and those who wrote it six months ago.

There are two types of developers: those who write the changelog, and those whose users find the breaking change in production.

There are two types of developers: those who close the laptop on a green build, and those who push "one more thing" into the red.

There are two types of developers: those who said "we should rewrite it," and those maintaining the rewrite of the last rewrite.

There are two types of developers: those who write the integration test, and those who found the integration broken from a customer.

There are two types of developers: those who document the workaround, and those who became the workaround.

There are two types of developers: those who use the framework as intended, and those who fought it and lost.

There are two types of developers: those who write the test first, and those who write the test to match the bug.

There are two types of developers: those who fix the root cause, and those who add another if statement on top of the last one.

There are two types of developers: those who ask in the channel, and those who spend three hours not asking in the channel.

There are two types of developers: those who clean up the console.logs before the PR, and those whose logs say "here," "here2," "WHY."

There are two types of developers: those who read the requirements, and those who built the wrong thing beautifully.

There are two types of developers: those who handle the null, and those whose app crashes the instant a real user shows up.

There are two types of developers: those who learned from the outage, and those who scheduled the same deploy for next Friday.