You know, I've always been okay with calling myself a programmer; calling myself a 'software engineer', as my official role describes, is where I start to feel the familiar creep and anxiety of imposter syndrome. I might be creating something I'm really excited about but even then as I'm solving problems, I'll be struggling with the inner thoughts of, "This is a naive solution, it won't scale...how would a real engineer solve this problem".
The obsession with performance and scalability in this industry kind of a toxic thing to carry as you're just making things for your own personal enrichment and goals. It's in times like these that posts like this one remind you that 'good enough' is often more than good enough.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You know, I've always been okay with calling myself a programmer; calling myself a 'software engineer', as my official role describes, is where I start to feel the familiar creep and anxiety of imposter syndrome. I might be creating something I'm really excited about but even then as I'm solving problems, I'll be struggling with the inner thoughts of, "This is a naive solution, it won't scale...how would a real engineer solve this problem".
The obsession with performance and scalability in this industry kind of a toxic thing to carry as you're just making things for your own personal enrichment and goals. It's in times like these that posts like this one remind you that 'good enough' is often more than good enough.