11–20 of 23 posts
Maybe you're not slow compared to other developers. Maybe they were expecting you to work lots of extra hours?
when i left they asked my friend to start working weekends, so maybe
Did you feel like you were a good fit at that company? Whenever you were fired, was it a surprise? Did you feel like you should have been delivering more or more often, or was it a surprise?
I am often slower than other developers. However, I produce far fewer inconsistencies (bugs...), my code is highly reusable, and my documentation skills make it easy for someone to come behind be and know what is going on without asking any (or very few) questions. Perhaps you were not a good fit there but another place you will be an amazing fit. Keep your head up. Quality over quantity.
thanks :)
I am often slower than other developers. However, I produce far fewer inconsistencies (bugs...), my code is highly reusable, and my documentation skills make it easy for someone to come behind be and know what is going on without asking any (or very few) questions. Perhaps you were not a good fit there but another place you will be an amazing fit. Keep your head up. Quality over quantity.
do your higher ups notice you produce less bugs? is this something you communicate to others or let your actions speak themselves? thanks :)
Perhaps I need to add a function to accommodate a specific item we didn't anticipate. This isn't a bug.
However if I have a function that does x,y,z and it turns out it can't do z or it doesn't do y as it should then we consider this a bug. We count these numbers and we ask each other to submit something that states their logic and design process. We also consider inadequate design or lack of a process a bug as well. Poor planning.
We also track time on how long it takes us to fix these bugs and implement the original design. We also ask each other for estimates on how long it would them to implement and we build a schedule on an average of these estimates.
I just ran the query for last year. I had 1 bug each quarter. One of the developers has 178. The last hire has almost 400.
I implemented a plan to reduce draw call overhead. It took me 3 months. That was almost double what other developers estimated it would take them. So far just one issue has been reported and it was more an error using to0 few words in the code comments but I added an `assert` just to warn the developer to look at this and I also fixed the code comments and provided an example.
Edit: Yes, higher ups do and look at this quarterly and I'm not sure what they do with the info to be honest.
Yeah, don't sweat it. Most likely it was a cash flow problem.
Speed depends on external factors too, did you have the resources available to succeed ? Was the problem well defined and well understood by you ? Were someone available to ask if you needed additional information? Were your manager following up on your issues? Did requirements change, was this expected and understood? Were your expectations aligned with regards to prioritizing production speed versus quality versus documentation?
Just look for a non-tech company, but don't expect to get to a senior level or higher.
I'm a slow dev when it's something new. My company only cares about speed. I'm still a midlevel dev after 10 years and probably always will be. Just look for a non-tech company, but don't expect to get to a senior level or higher.