261–270 of 275 posts
Having been a programmer for forty years, I am senior in every sense of the word. Also, I hate everything I have ever written. When I look at something I wrote three months ago, it is embarrassing. Now, today's code, that's a different story. It is awesome. And it will be until I turn my attention elsewhere. When I come back to it, it will also suck. Which is to say, Of course you hate your previous work. You learned…
What am I doing to overcome this situation? - I have clearly understood and made up my mind that I cannot be a PM. - However, to stay in the job I always have to prove my technical skills. - I am trying to get into competitive programming which I discovered recently and my aim for 2021 is to at least solve one codeforces round - I started enjoying Flutter and I also did 30 days of live streaming on youtube (Just screenshare with music). - I have a mobile app idea that I plan to work in coming days. - I try to write 1k words per day
During work hours, I try not to think about hobbies and concentrate on finishing my work. However, during free time, I fire up my personal laptop and start focusing on my hobbies.
Earlier quoted context omitted.
I don't know what it is about "imposter syndrome" but it's clearly having a moment. People are quick to label things "imposter syndrome" these days. Imposter syndrome is feeling like you are an imposter or fraud even though, objectively, your job performance is adequate. If anything, the original poster is describing the opposite of imposter syndrome, because they cited specific objective criteria showing that their…
Read the title again. That is impostor syndrome. OP is not reacting by wanting to do self-improvement, OP has decided their 10 year experience is a fraud and wants to quit software development.
2. OP wanted guidance about how to improve as a developer, if they wanted to quit they wouldn't have made the post.
>I'm not sure if I can be a PM if I'm not able to code things the right way myself. You don't need to know how to code the solution to be a good PM, it's a different set of skills. QA - writing testcases, automated regression tests is also a possible path. Lots of companies want QA engineers that can write automated regresion tests (selenium etc)
> " QA - writing testcases, automated regression tests is also a possible path. " No. QA automation code is still code. If a person can't write solid code, they're not going to succeed in QA doing automation either.
And that's Product Manager. Project Manager. Product Owner. People Master. etc.
That said, you sound like you are having a down day/time. Sucks.
You might be a bit burned out, too.
If you are not completely addicated to the salary, then there are a zillion things you can do.
Tho, all these other roles make decent money too.
One thing that I have done is 'developer support'.
'Support', to me, as in 'Support Engineer', can be, and often is, the lowliest, most wretched and grinding position in the company -- often depends on the company.
But doing 'Developer Support' can be more interesting and even fun because the customers are just more technically competent on average, and you'll basically be overqualified for the position -- i.e. you will not have any performance issues.
Forget coding during the day -- it sucks -- save your coding for after-work hours when you can create your own shit and have fun.
Earlier quoted context omitted.
Well, actually... it could be a good practice, if the values are used in multiple places.
What's the good practice advantage over just using " http://www "? If we later change over to use https, it's not like I'd think public final static string HTTP = "https"; was any kind of improvement.
Some devs are such stuck-ups smh
It sounds to me like you haven't internalized a lot of the advice in the first half of "Clean Code" and/or the entirety of "The Pragmatic Programmer". Either of those books takes a few weeks to read slowly and a few months-to-years of deliberate practice to internalize and synthesize as your own. The good news is that admitting you have a problem is the first step. Personally I find I still frequently write pretty at…
The Pragmatic Programmer serves as inspiration for me every time I read it. I know everything in it, but somehow I always come away with at least one "I could totally be solving my current problem with this!" insight from a re-reading.
I'd argue differently. Congrats for having the courage to recognize your problem. The analogy that comes to mind is I've been playing basketball in my local town, and now I've gotten promoted to play in the big city. I now feel like a small fish in a big pond. If you enjoy software engineering, I'd say, double down. Now that you're at the medium software company, seek mentorship and coaching from others. In addition,…