But how would I describe myself as a web developer? Technology and graphics seem to come easier to me than words. Researching the internet, I find writing tips and text analysis tools, but they often contradict. One’s best practice is another one’s poor example for being too long, hard to understand or not personal enough.
Much of this was already clear to me.
It’s also clear that algorithms make mistakes, because they don’t really understand sentences. They tend to confuse conjunctions with filler words.
Write in short, crisp sentences! Talk to your customers directly! Talk about them, not about you! Thus no application letter style and no me-messages. Don’t write like you have learned in application workshops. Avoid hard to understand terms, but write what your readers (customers) expect. Another contradiction.
Dissatisfied with my previous texts, I tried to underrstand why I wrote that way.
I used Twitter to announce events with multiple talks. Title, name, date and link all had to fit in a limited character length, together with hash tags, also known as keywords for search engine optimization. Does that explain my frequent iteration of terms and synonyms?
Technical dokumentation is another source of unattractive language. Although that requires comprehensibility, it also implies using the correct technical terms. Long sentences are a plus here, typically starting with “as a …” to summarise a technical requirement in one sentence, like
“As a web developer I want to use dense titles to spare coworkers reading details so that my issue will be processed as quickly as possible.”
How I specifically want to improve my wording to present myself, you can see soon when I relaunch my website , www.ingo-steinke.de.
