3 ms·

We've all been there. Things take much longer than expected. This is, as you've already stated, something we come to realize in our careers. However, I would l

We've all been there. Things take much longer than expected. This is, as you've already stated, something we come to realize in our careers. However, I would like to share a different angle, if I may. I don't think your speed is necessarily the problem. I think your time estimation skills might need some work. It's easy for us to think things "should be simple". Unfortunately, the modern world of software is becoming more and more diverse and complex (a symptom of software "eating the world"). It's only natural in a world that has evolved from 8086's and terminals to interconnected-everything, multi-OS, multi-platform, multi-device magic is going to be orders of magnitude more difficult to build on at any reasonable scale of business. There are just so many small things that can go wrong! I would gently suggest you stop being so hard on yourself and instead of beating yourself up for "being slow" just take each technology one at a time. Ultimately, the way to survive in this career is embracing change and staying sane while doing it. It's not easy, but it's the only way. As for you being dumb, I would also like to say that it is clear you choose to deeply understand the topics you put in your head. Many folks "learn enough to get the job done" and very little more. It seems you have an appreciation for deep learning. This is not a bad thing, it is usually this trait over a long time that differentiates a truly senior engineer from an intermediate one. Your path may be slower, but it is probably more thorough and more informative in the long term. Keep in mind though, this breeds imposter syndrome in your mind. When you accept you still have lots to learn, it is easy to feel like you know nothing at all. I would suggest not letting this get to you. We all feel it, it is real, we're all just trying to do our best day-to-day. Oh, and always 2x pad all your estimates at minimum, cause if we know anything about computing, it's that it always has hiccups.

hsn915 3y ago
It's ok man. I don't need to be cheered up. It's completely fine to accept your situation without giving up on improving it. The problem is when people refuse to acknowledge reality because they really hate certain labels and are too invested in not having that label apply to them. I'm slow and it's ok. I'd like to become faster in the future. But for now, I'm slow, and that's ok.
- softfalcon 3y ago
  I'm also slow. It is also okay. I have met many, many brilliant engineers. They fly real fast and really far. The funny thing about it is that they tend to crash and burn sometimes too. Sometimes they even break orbit, but even then, someone has to stabilize that orbit from time to time. Life takes all kinds of people. Folks who are willing to simplify things while ignoring fads are just as useful as those who jump into the unknown of new technologies. What you think of as a weakness you need to compensate for so you can get work done is what other employers will consider an asset because you refuse to add complexity where it is unwarranted. What you call "slow" others might call wisdom. I'm really not trying to cheer you up. I'm sharing facts from over a decade writing software being the "slow one".

hsn915 3y ago

It's ok man. I don't need to be cheered up. It's completely fine to accept your situation without giving up on improving it. The problem is when people refuse to acknowledge reality because they really hate certain labels and are too invested in not having that label apply to them. I'm slow and it's ok. I'd like to become faster in the future. But for now, I'm slow, and that's ok.

softfalcon 3y ago
I'm also slow. It is also okay. I have met many, many brilliant engineers. They fly real fast and really far. The funny thing about it is that they tend to crash and burn sometimes too. Sometimes they even break orbit, but even then, someone has to stabilize that orbit from time to time. Life takes all kinds of people. Folks who are willing to simplify things while ignoring fads are just as useful as those who jump into the unknown of new technologies. What you think of as a weakness you need to compensate for so you can get work done is what other employers will consider an asset because you refuse to add complexity where it is unwarranted. What you call "slow" others might call wisdom. I'm really not trying to cheer you up. I'm sharing facts from over a decade writing software being the "slow one".