30+ years of tech, retired from an identity intelligence company, now part-time with an insurance broker.
Dev community mod - mostly light gardening & weeding out spam :)
I'll suggest a couple of soft-ish skills that are poorly taught in my experience:
evolution, not perfection: knowing when something is 'good enough' for now (which depends on a number of other variables, like the subject domain - medical anyone?, risk appetite and delivery needs) then knowing when/why to re-visit those earlier decisions.
understanding risk: in both technical terms (like infosec risk / OWASP) and business terms (like business continuity plans / contract terms - SLAs).
Business risk is unfortunately overlooked by a lot of developers (and I mean not just coders, but everybody in the company). It creates tension when not everybody is aware of the obstacles.
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.
I'll suggest a couple of soft-ish skills that are poorly taught in my experience:
Business risk is unfortunately overlooked by a lot of developers (and I mean not just coders, but everybody in the company). It creates tension when not everybody is aware of the obstacles.