let's see, in no particular order:
1. I don't have any standardized way of naming my shit. Like I can name a working, production file "cum_erection.py" and not really care about the consequences. I've definitely improved, but I often name WIP files in NSFW manners just because I can.
2. I'm too much of a nice guy. Like one dude on the team could be fucking up badly, but I'll still try my best to cover the asshole just because I don't like dealing with all the drama associated with asking the guy to clean up his act. I guess I have trouble finding my niche and asserting myself in the workplace (don't worry, I'm not liek that IRL
).
3. Related to that, I'm too much of a boring stiff at work (again, not IRL), but I do warm up and "be myself" after a couple of months.
4. I rely too much on code snippets or templates I already made for myself and normally can't code from absolute scratch. I CAN however explain code relatively well, and generally know what I'm doing so I think it's some kind of psychological thing.
5. I'm kind of afraid of work-related criticism, especially regarding my work, in fact I feel that I get too defensive/discouraged about my shit sometimes.
6. I'm a pretty fast worker, so I tend to lax and cram wayyy or right before a major deadline.
HOLY SHIT those are bad.
the "i sell myself short, but..." isn't bad, IF it is qualified. "i often sell myself short BECAUSE i don't like peer scrutiny" is honest, and can then be followed by "but i understand that being judged is something that is part of a team environment like this AND i've come to accept that i shouldn't be worried by praise -- in fact, positivity by example is a powerful motivational tool." that sounds insightful without being indirectly self-aggrandizing.
Seems more in line with the answer I was thinking of, but I wonder if this shit actually flies in an actual interview (then again Prole is a pro interviewer so I guess such an answer is acceptable).
