I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
"there by" should be "thereby"
"junkie" should be "Junkie"
"largescale" should be "large scale"
"An web application" should be "A web application".
But "Performance Junkie" is probably not a good phrase to use, go with "Performance Oriented" or something else safe.
Overeall there are a few inconsistencies in terms of capitalisation, punctuation and tense. Make sure if you use a full-stop at the end of a line you do it for all similar lines (see "Projects" section) and pick whether phrases like "Native of Bilingual Proficiency" have any cause to be title-case (they don't)
In terms of sentence structure, you change from actions to descriptions:
"Designed a thing"
"Prototyped another thing"
"A thing that does something"
This feels like the section hasn't been proofread (which is what you're asking us to do so that's fine!)
As long as it's true, you could change phrases like "Fixed several severe security issues", which sounds vague, not to mention alliterative, into "Conducted a security audit to expose and address issues with..."
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.
In addition to these:
"there by" should be "thereby"
"junkie" should be "Junkie"
"largescale" should be "large scale"
"An web application" should be "A web application".
But "Performance Junkie" is probably not a good phrase to use, go with "Performance Oriented" or something else safe.
Overeall there are a few inconsistencies in terms of capitalisation, punctuation and tense. Make sure if you use a full-stop at the end of a line you do it for all similar lines (see "Projects" section) and pick whether phrases like "Native of Bilingual Proficiency" have any cause to be title-case (they don't)
In terms of sentence structure, you change from actions to descriptions:
This feels like the section hasn't been proofread (which is what you're asking us to do so that's fine!)
As long as it's true, you could change phrases like "Fixed several severe security issues", which sounds vague, not to mention alliterative, into "Conducted a security audit to expose and address issues with..."