The Engineer: Frustrations About My Job
Hello people! Hope you guys are having a great week! We talk a lot about our jobs and the exciting things about it, so this week we’re talking about things that we don’t like. Here are some things that I don’t like about my job in tech:
A lot of times, I’m given a problem to solve but I’m not given the whole picture. And the whole picture isn’t something related to tech but more so on the business side. Although I’ve gotten better at connecting those dots, it is very frustrating when you feel like you’ve finished building something and it turns out to not be correct because of information that I didn’t have before.
When you’ve reached a point in your coding journey where the mistakes you made are almost never spelling errors or missing semicolons (they make Developer environments to check those for you) and rather your code works for 95% of all problems but doesn’t work for that 5%. Figuring out that 5% can be very frustrating and often times will lead you into having to rewrite your code completely. Sometimes you can spend hours debugging to figure out something so small and it can be so draining.
Having to code differently when you shouldn’t have to.
This is probably one of the more frustrating things. I’ll code something and for whatever reason, it doesn’t work and the only way to solve this problem is to code it a different way for no explainable reason. The problem I have with that is that there’s no reason as to the why the different implementation. This may tie back to the ambiguity but it can be discouraging thinking you’re doing something right and the reason why it’s wrong has nothing to do with you and you don’t know until after you’ve spent hours or days trying to figure out the problem.
This is definitely not the complete list of things I don’t like. I decided to focus on just the technical aspects of the job. Do you share any of these similar frustrations in your job? What frustrations do you have about work? -The Engineer