Maybe I should write a technical blog post

Maybe I should write a technical blog post. I am a software engineer, after all. I do the things that constitute software engineering. You know, copying and pasting code around from the Internet and from our codebase to other parts of our codebase.

It seems like many software engineers, in their blogs, they talk about software engineering. Should I do that?

This is me talking about software engineering: You know when you’re trying to figure out why an input component that you’re using from a library isn’t behaving as expected in your React application, and it’s really annoying and dumb? Yeah, me too.

If I were to use a few words to describe most software problems, they would be annoying and dumb. Sure, every now and then there are “interesting” problems. But the interesting part is 2% of the work, and the other 98% are annoying, dumb problems.

If job postings were honest, they would be like: “We need someone to come and work here and try not to lose their minds solving these truly stupid problems that we have. As a reward for maintaining your sanity, you may get to work on something that one may even call interesting and sometimes we have pizza parties.”