Technical Writing, Training, and Documentation Service Provider in Singapore


    How I became a Tech Writer

    As a child, I dreamed of being a pilot, as a young boy I dreamed of being a doctor, but there are dreams that cannot be and storms we cannot weather. 

    I am now a Writer in the business of creating knowledge base, designing information architecture, informing, persuading, and evangelizing users, through engineering blogs, white papers, and product documentationI communicate technical knowledge, arousing the reader's curiosity. The process of learning excites me. I love to research and convey complex information in a simple, understandable, and user-friendly format. I am energized by the steady and deliberate journey from ignorance to competence. 




    As a writer, I delve in three worlds - one world where I put myself into the shoes of target readers, gauging their levels of expertise - novice to an expert; the second world where I spend my time researching and interacting with the application; and the third world, where I craft my writing until it's perfect. 

    After a piece of writing has been developed, I make it better, cleaner, and more efficient. I take the engineers' and users' feedback to polish it further and make it the best possible version of itself that it can be.


    Technical Writer
    During my school days, I was a voracious reader. I read comics such as Tintin, Archie, Chacha Chaudhary, Tinkle, Champak, stories from Enid Blyton, Hardy Boys, and Reader's digest.

    My goal was to rank among the top students in the class. I performed well in my studies. On rare occasions, my rank slipped below my expectations, but I always bounced back. Life’s biggest goals were finishing exams, scoring well, and traveling to my hometown - Kottayam, an adventurous journey by train for three days and two nights, passing through hills, mountains, rivers, fields, and tunnels. 

    After X, like every student in the science stream, my goal was to be a doctor or an engineer. I let go of all extracurricular activities and focused only on my studies. In XII, most of us had private tuitions on top of what school teachers were already providing. But things didn't work out as per my plans. I did not qualify for an Engineering or Medicine seat. Based on the merit, I enrolled for a bachelor's degree in Science from the M.S. University of Baroda


    While in the first year, I still pursued my dream. I studied for medical entrance while I was doing BSc but because of clashes in the examination dates; I let go of my dream and carried on with a renewed mind. I scored 62% in the first year and expected a similar performance in the second year, but to my dismay; I scored only 52%.

    During the last year of BSc., I wanted to pursue Masters in Computer Applications (MCA), so I started preparing for the entrance test. To qualify for the entrance test, I needed to score at least 60% in the last year, so that the average of the second and third year comes out to be 55%. By God's grace, I scored 62% in the last year. 


    I appeared for the MCA entrance examination in May 1998. It was a miracle from God to see my rank in the top 10. 

    When I attended the first semester classes, the subjects were different from what I had studied until then. The programming languages were foreign to me. The only subjects that I was comfortable, were Maths and Economics. During the first year, I performed badly in programming languages. But from the second year onwards, my grades improved. In the last semesters, I did projects at ABB and Railway Staff College, using Visual Basic and Oracle. It was during that time I was exposed to the 'Internet' and got fascinated with yahoo messenger. I could interact with people across the globe. In the overall three years of the MCA curriculum, I scored first class. Thank God for His mercy!

    During the college days, every student's goal was to get through campus interviews. In the fifth semester, 2001, companies like Amdocs, TCS, Patni, Wipro, MBT hired more than half the class of our MCA graduates. But in the latter part of the year, because of the dotcom bubble burst coupled with the World Trade Center attack, companies canceled or postponed their job offers. It was a blow to those who were given job offer letters. Miraculously, I got into a US-based startup company - Amtel Security Systems. I was interviewed by Suresh Gajwani, the founder when he was on a visit.


    Shortly after I got into the company, I learned that my primary responsibility was not coding but writing product documentation, providing technical support, gathering customer requirements, writing persuasive RFP responses, assisting sales in identifying customer's business requirements, and delivering technically correct solutions, testing, and even issuing purchase orders for controllers and chips. I had hands-on experience with almost everything except coding. I loved the RFID and security products and enjoyed my work there.

    I worked at Amtel for two-and-a-half years, but there was no salary increment. I decided to change the company. By this time, my programming skills got rusted, and I lost my passion for coding. The only option I had was to work as a Testing Engineer or Sales Engineer. While browsing for jobs in newspapers, I came across a post of a Technical Writer that caught my attention. Until then, I was not aware of a post called Technical Writer. 

    I gave two interviews, one with Impetus Technologies for Testing Engineer and another with Zensar Technologies for Technical Writer. I traveled to Ahmedabad to attend the Impetus Technologies interview. Zensar conducted my interview via telephone.

    While I was in Kottayam for a vacation, I got the offer letter from Impetus. After reaching Baroda, I put forth my resignation and joined Impetus, Indore, in Feb 2004 as a Software Testing Engineer. That was the first time I started living independently away from my parents. The company provided hotel accommodation for a week. 


    Cross Roads
    Two weeks later, after joining Impetus, I got the offer from Zensar Technologies, for the post of Technical Writer with a better salary. I was in a dilemma about whether to accept the offer since I was happy with the role of Software Testing Engineer. After much pondering, I decided to go for Zensar's offer that established my career as a Technical Writer, a road not taken by the MCA graduates.

    Two roads diverged in a yellow wood,
    And sorry I could not travel both
    And be one traveler, long I stood
    And looked down one as far as I could
    To where it bent in the undergrowth;
    Then took the other, as just as fair,
    And having perhaps the better claim
    Because it was grassy and wanted wear,
    Though as for that the passing there
    Had worn them really about the same,
    And both that morning equally lay
    In leaves no step had trodden black.
    Oh, I marked the first for another day!
    Yet knowing how way leads on to way
    I doubted if I should ever come back.
    I shall be telling this with a sigh
    Somewhere ages and ages hence:
    Two roads diverged in a wood, and I,
    I took the one less traveled by,
    And that has made all the difference

    At Zensar, I wrote documentation for the UML tool - BluePrint Foundry, created help file (CHM format) using a freeware tool “Cheetah”, and wrote ADDL syntax Programmer’s Guide.

    In Oct 2004, I received an email for a Technical Writing position with Samsung Electronics in South Korea. It was a marvelous opportunity. I boarded a Jet Airways flight from Pune and landed at Bangalore airport just on time, to attend the interview. From there, I took a taxi to the Samsung office. When I entered the meeting room, I was surprised to see a room full of Korean nationalities. The interview went well, but I was not sure of my performance.

    In November 2004, through God's favor, I received a confirmation letter from Samsung about my selection. During the same time, I received another offer from a company in Pune, but I decided to join Samsung Electronics. I resigned from Zensar Technologies on 10th Jan 2004.

    I arrived in S. Korea on 21st Feb 2005. It was one of the coldest days with temperatures below minus 15 degrees. You can read about my experience here http://www.thomasabeesh.com/2012/07/14/memoirs-of-south-korea/. I was with the Flash Management Software group, Memory Division, responsible for creating product documentation and white papers for Samsung's XSR, Whimory, RFS, and TFS4 file systems.



    Memory Division, Samsung Electronics

    The best thing about working in Samsung, Korea was that they provided a fully furnished flat, festival bonuses during Chinese New Year (Feb) and Chuseok Festival (Sep), performance bonus equivalent to 2-3 months salary, year ending completion bonus, two-way flight tickets to your home country, relocation allowance, and zero tax for foreigners with Master's degree and 3+ years of work experience. 
    Samsung Electronics Residence
    A view from my flat in S.Korea
    I enjoyed the weather in Korea especially the snow in winter. Some of the beautiful places I love there are Jeju, Busan, and Seoul. The company provided free training to learn the Korean language.

    When I joined the Memory Division, it was the most profitable division. But in 2009 due to the great recession, the company suffered losses, and the management decided not to renew the contract of foreign engineers. Most of my colleagues opted to work in Samsung India, Bangalore.

    Before the turn of these events, I wanted to work in the UK. So, in October 2008, I applied for the Tier 1 work permit (HSMP) and within a week, it was approved. I could stay in the UK and look for a job without requiring any company to sponsor my work permit. 



    After my contract with Samsung, I went to Cambridge, UK in March 2009. (Click here for pics). 

    But it was an economic recession there too. I stayed with an African family for a monthly rent of 350 pounds. It was through them; I got the chance to attend the African-American Worship service at the City of David Church - one of the most vibrant people I ever met in my life. While staying in the UK for three months, I attended three interviews in Bristol and Cambridge, but with no success. I decided to return to India to continue my career as a technical writer. On June 2nd, 2009, I left Cambridge and came back to my hometown - Kottayam. In mid-June, out of blue, I received an email from a consultancy in Singapore for the post of a technical writer with Savi Technology - A Lockheed Martin Company


    Singapore was never on my radar. I had never dreamed of working there. God's plan was different.

    Singapore
    Singapore
    There were five rounds of telephonic interviews with the Information Development (ID) Manager, Principal Writer, ID Director, Product Manager, and Vice President of Savi, Singapore. By God's favor, the interviews were successful, and I was selected to work in Singapore for Savi Technologies. I was supposed to join on July 15th, 2009 but later I discovered that I could not travel since my passport validity was less than six months. I applied for the tatkal passport in Kochi and got my passport after seven days. It took another one week to get my employment pass from Singapore MoM.  I was provided the flight tickets and two weeks of accommodation at Spottiswood Park, Tanjong Pagar. On July 26, 2009, I arrived in Singapore and joined Savi Technologies. It was my first experience working in an Agile Scrum environment. I wrote SDK Installation Guide, User Guides, Installation Guides for Savi’s SmartChain RFID applications, using  XMetal as a Single-Sourcing tool for generating content in various formats such as Online Help, CHM, and JAR files, and performed quality assurance and usability testing in the process of producing user documentation. 




    Savi Technology Collegues

    After working there for a year, in August 2010, due to the company's financial performance, the US office decided to outsource the development work to the Pune office in India. Nobody expected the closure of operations in Singapore. The employees were given the choice to work in India, but nobody opted for it. In the middle of September, through God's favor, I received two offers, one with Philips Electronics and another with Tagit Pte Ltd, for a one-year contract. I was in a dilemma to choose the company since both offered the same pay package, but I decided to go for Tagit. My responsibilities were to create user guides, installation guides, and training materials for the mobile banking application, Mobeix. 

    In August 2011, history repeated itself. Because of the financial situation, Tagit started cutting staff, and I was laid off. Since I was employed through consultancy, they tried their best to find another client but had no success. Meanwhile, I applied for PEP and got approval within three weeks. I could work for any company in Singapore without requiring any sponsorship.

    In the first week of October 2011, I got an interview call for a technical writing position with PayPal, an eBay company, at Suntec City, Singapore. It was a six months contract position. There were four candidates vying for the same post. On Oct 10, a day before my birthday, I got confirmation about my selection. Praise God. I was responsible to create API documentation for their SOA-based financial instrument services. 

    On February 29, 2012, I received a call from the consultant informing me that my last working day would be on April 16th, 2012. I was taken by surprise since I expected an extension of my contract.

    I started applying for jobs. In the third week of March 2012, I got an interview call from JDSU Test & Measurements Singapore Pte Ltd, a US-based telecom company. I attended the interview and within two weeks, I received confirmation about my selection. All praises to my Lord and Savior Jesus Christ. One thing I know for sure, God can do it again and again when you call Him. After my selection, PayPal wanted to extend my contract for three more months, but it was too late.


    After working at JDSU for three years and two months, the company split into two disparate groups, Viavi Solutions, and Lumentum. Because of the split, it carried a burden of 50 million USD. To manage the expenses, JDSU decided to close the R&D division in Singapore, phase by phase. I was given a month's notice period. The company provided the relocation expenses and three months' salary for the number of years I worked.

    A week before leaving Singapore, I got an interview with NextLabs, through a referral from an ex-colleague. I cleared the first round, which comprised a written test, an interview with a product lead, and with the director. The second round was a telephonic interview with a senior writer in the US. I cleared that and then there was a third round of telephonic interview scheduled on 29th July with the VP of the R&D division from the US. 

    I also had an interview scheduled with another company on 30th July, but my visa was valid until 26th July. I went to ICA Singapore, to extend my visa, but it was denied.

    While in India, I completed the third round of the telephonic interview and submitted three references from my previous company as per the NextLabs HR policy.

    After two weeks, I received confirmation of my selection. The company applied for my Employment Pass, which was approved within a week. Praise God for His favor. After I joined the company on 26th August 2015, I came to know there were other candidates vying for the same post. 


    Life was going smoothlyI was enjoying the workplace, people were cooperative, there were new products coming up that needed constant documentation. We went for occasional team outings and were having fun. In March 2017, we got our salary after a delay of 2 weeks. It was the first sign of financial trouble. During the quarterly all-hands meeting in May, the CEO indicated the possibility of pruning the workforce if the situation didn't improve. On June 7th, when I entered the office, the admin was not in her seat. I came to know she was let off the previous day. At 1 pm, as I was about to go for lunch, the director called me to a meeting room. I was informed that it was my last day in the office. With all the leaves and 2 weeks notice period, my official last day would be July 4th. I would get my salary until July 4th, but I need not come to the office. I was calm. I knew God was in control and something better would turn up. Few other employees were also given the termination letter.

    I started updating my resume on the job sites. I attended 5 interviews in a span of 2 months. Some interviewers gave high hopes as if they were about to hire me the next day, but at the last moment, they backtracked.

    Through a referral, I got confirmation from Xchanging, a DXC Technology company, but they wanted me to move to Kuala Lumpur, Malaysia. I gave my consent for relocation and they applied for my EP. Two weeks later, I got an interview offer with Veritas Technologies, in Singapore for a one-year contract via consultancy. They confirmed my selection after a week. I had to renege the Malaysian offer, but it was cordial. I had to leave Singapore as my pass was about to expire. While I was in India, the company applied for my EP on 3rd August. MoM approved the application on 25th, and I joined the company on 30th August.

    At Veritas, my primary responsibility was to create the documentation for the GovTech Singapore, Backup-as-a-Service Cloud project. I visited the GovTech Data Center daily, interacted with stakeholders and engineers to get the doc feedback and project updates. The deadlines were strict as it was a government project.


    GovTech Data Center


    While I was still with Veritas, in Jan 2018, I saw an ad for a technical writing position with Grab. I applied via Linkedin. There were 2 rounds of interviews. In February, I received confirmation about my selection. I submitted my resignation, gave 1 month notice period, and joined Grab in April 2018! Glory to God!

    Grab had just merged with Uber in March 2018. I was the first technical writer to join. In a span of three months, other writers joined. The engineering manager who hired us had worked in Uber, USA. Since Uber had technical writers, he experimented the same by hiring writers at Grab. All the writers were put in different teams. 

     In the initial days, it was a bit chaotic. I was confused as, why we were hired. Our documentation users were product analysts, data scientists, backend engineers, mobile developers within Grab. This was my first experience writing for internal users. In all the previous companies, I wrote for external users. After 6 months, engineers started seeing the value that we brought to their teams. We designed the structure and breathed life into the documentation. We published engineering blogsnewsletters, and technical tutorials in the Google Codelab format

    The office at Marina One was awesome. It was like being on a cruise ship with a sea view all around.

    Life was going smooth until Covid-19 stuck. In March 2020, our team was about to onboard a new Technical Writer. With a view of the looming recession, there was a sudden announcement of a hiring freeze. 

    There were regular town hall meetings via zoom with Grab's founders and HR heads. In May, they gave a hint of layoffs. And in the second week of June, just a few days before the government's decision to lift the lockdown, the management decided to strike the iron while it was hot. A total of about 360 Grabbers were impacted and that included me and another writer. Love this farewell card from Grab colleagues.

    Paul writes in Philippians 4:11-13: Not that I speak in regard to need, for I have learned in whatever state I am, to be content: 12 I know how to be abased, and I know how to abound. Everywhere and in all things I have learned both to be full and to be hungry, both to abound and to suffer need. 13 I can do all things through Christ who strengthens me.

    James 1:9 Let the lowly brother glory in his exaltation, but the rich in his humiliation, because as a flower of the field he will pass away. For no sooner has the sun risen with a burning heat than it withers the grass; its flower falls, and its beautiful appearance perishes. So the rich man also will fade away in his pursuits.

    Technical Writers are hired for a reason and for a season. As soon as the company finances head south, there will be layoffs. At such times, God works in a mysterious way. 

    Why Hire Me?

    I am surprised to see advertisements from high-tech companies in Singapore, looking for Technical Writers with just 2 to 3 years of experience. I believe it is because of the cost factor to hire experienced writers with 10+ years of experience.  

    Technical documents are designed to convey information clearly and persuasively but there are no definite, measurable standards to judge. It's possible that writing can be error-free and still not communicate effectively. There are no algorithms for writing. It takes years of experience and mentorship for writers to come out with quality documentation. 

    The key to writing a good document is that it has to be a good experience for both - the writer and the reader. The satisfaction of the writer and the reader are interwoven. 

    Technical Writing is an art and science. We practice our craft to service the reader. We don't expel raw material; we transmute it to provide what the reader needs. Like any art, writing involves collaboration. We cannot produce documentation in silos.

    My Advantage
    • Excellent interpersonal skills
    • Excellent communication skills 
    • IELTS score 8
    • Master of Computer Applications (MCA) and Bachelor of Science (Physics)
    • More than 19 years of writing experience with reputed companies
    • Mentored by Professional Writers and Editors
    • Expertise with documentation tools such as Atlassian Confluence, XMetal Author, Robohelp, Altova XML Spy, Adobe FrameMaker, Microsoft Word, Microsoft Visio
    • Expert in creating product documentation such as User Guides, Installation Guides, Blogs, White Papers, Training Materials, and Standard Operating Procedures (SOP)
    • Worked in Agile Scrum and Waterfall environment
    • Expertise with version control tools such as GIT, Tortoise Subversion, ClearCase, and Snapshot CM
    • If you have questions, or you want to hire me, email me at abeeshthomas@yahoo.com.
    • If you want me to mentor you or assist you in writing technical documentation, contact me at abeeshthomas@yahoo.com.
    • To outsource your writing and documentation projects, visit ThomasEcafe.com, email: info@thomasecafe.com, or call +65-82086393. 

    Principles of Technical Writing

    This post provides a look at the "technical writing principles" I've found useful in helping writers to become highly effective and valued as a member of an engineering team.

    • Be a lifelong learner

    To be an effective writer, you have to be a lifelong learner, get motivated enough to learn new technolgoies. For tech writers, learning continues from the cradle to the grave.

    • Have a positive attitude

    You have to know how to collaborate and be a good judge of people. Additionally, you must be willing to interact with different personalities of the people you are working with. There is an innate skill to draw information out of people or get your work reviewed by the SMEs without aggravating them. The success you experience as a writer depends on your attitude. Sometimes, you may be given an assignment that has nothing to do with creating documentation. But you must display a positive attitude towards such requests. 

    • Quality should be the priority

    Your job is to make sure that your work is complete, correct, thoroughly fact-checked, and technically reviewed. Make sure that when you start something, you complete it. If people know they can rely on you to do high-quality work, you will win the trust.

    • Communicate, Communicate, and Communicate

    Writers should strive to be superior communicators, as ineffective communication leads to confusion and reflects poorly on the entire team. The writer will be judged by the quality of his work. For better quality, communication is the key factor:
      • Documentation Plans - Make it clear to all stakeholders' what outputs to expect at any given point of time in the product life-cycle.
      • Review - Use the Google doc or Adobe Shared Review process to receive feedback.
      • Communication via emails/slack/meetings - Keep the stakeholders informed about the progress of your documentation. Use the email meeting to schedule appointments with SMEs and Product managers. Ad-hoc chat also works depending on your relationship.

    • Know your assignment

    Like it, or not, writers are 'contractors’ who are hired to create User Manuals, API documentation, Training Materials, Engineering Blogs, etc. Technical documentation is meant for users of the engineering product. The users may be within the company or external; they may be engineers or layman. Understanding the users will help to improve the quality of the writing and, ultimately, the quality of the product.

    • Avoid ambiguity

    This implies "Never presume" and clarify whenever there is ambiguity. Making speculation about how a product’s features/functionality, schedules, etc. will lead to a variety of issues such as:
      • Wrong content
      • Incomplete work
      • Poor impression on the documentation team
    Writers must avoid ambiguity in the documentation so as not to muddle others.

    • Inhale and Exhale Content

    Writers 'live and breathe' content. They consume content, and they create content. Practice your craft to serve the readers. Don't expel raw material but transmute it to provide what the reader most wants.

    • Trust facts - Question assumptions 

    Related to the principle of avoiding ambiguity, writers must never make assumptions. 
    Doing so can have a significant impact on the entire business.
    Writers must:
      • Work with the cross-functional team to address issues with requirements, user stories, etc.
      • Clarify schedules/expectations when in doubt.
      • Leverage documentation plan to articulate and set expectations on the documentation.
      • Track/manage outstanding issues until they are resolved.
      • Ensure a thorough document review by engineers and stakeholders.

    • Think innovation

    Regardless of your busy schedule, writers must think out-of-box. Improvement ideas should be socialized, shared, and investigated with managers and writers. Small changes can make a huge difference to the organization. Innovation that can benefit the documentation is always welcome.
      • Tweaks to processes, templates, style guide
      • Suggest better tools
      • Use videos where possible
      • Gather analytics

    • Use Style Guide 

    On the surface it may appear as if style guide does, in fact, restrict the writer; however, if you dig deeper you will discover that style guide helps by improving communications by establishing consistency in all the documents.

    • Plan wisely

    A well thought out and a documented plan is worth its weight in gold. Create a documentation plan to set expectations for all the stakeholders. 

    • Identify priorities

    At the end of the day, the most important Technical Writing principle is "If you do not know - ASK".  Writers must ask questions until they are confident that they have the information needed to write content. Just remember, unanswered questions contribute ambiguity to the content.

    • Escape the curse of knowledge 

    Close the writing loop by getting feedback from users. Show the draft to people who are actual users or atleast to the developers / QA, and find out whether they can follow it.  Only when we get the feedback, do we discover that what's obvious to us isn't obvious to them. A writer should revise in response to comment when it comes from users. 

    • Have a thick skin while receiving feedback

    You want to encourage folks to share their honest reactions to what you write. And if your documentation is useful and focused, timely and fresh, and you've written it with passion and voice about a subject you know a lot about, then your readers are likely to leave terrific feedback. But occasionally you're going to hear from people, especially from Editors, who disagree with you or who don't like your style or approach and give you rude commentsAnd that's never fun. It's taken me years to learn not to take that stuff personally, but take it with a grain of salt. 

    Troubleshooting Grammar Problems

    1. Sentence fragments

    Make sure each word group you have punctuated as a sentence contains a grammatically complete and independent thought that can stand alone as an acceptable sentence.


    Incorrect

    Tests of the Shroud of Turin have produced some curious findings. For example, the pollen of forty-eight plants native to Europe and the Middle East.

    [2nd sentence = fragment]


    Correct

    Tests of the Shroud of Turin have produced some curious findings. For example, the cloth contains the pollen of forty-eight plants native to Europe and the Middle East.

    2. Faulty parallelism

    Be sure you use grammatically equal sentence elements to express two or more matching ideas or items in a series.

    Incorrect

    The candidate’s goals include winning the election, a national health program, and the educational system.


    Correct

    The candidate’s goals include winning the election, enacting a national health program, and improving the educational system.

    Incorrect

    Some critics are not so much opposed to capital punishment as postponing it for so long.

    Correct

    Some critics are not so much opposed to capital punishment as they are to postponing it for so long.

    3. Noun strings

    The bulk of government and technical writing uses too many noun strings, or groups of nouns “sandwiched” together. Readability suffers when three words that are ordinarily separate nouns follow in succession.

    Noun string: NASA continues to work on the International Space Station astronaut living-quarters module development project.

    Correction: NASA is still developing the module that will provide living quarters for the astronauts aboard the International Space Station.

    4. Subject-Verb agreement

    The subject-verb pair guarantees that the sentence means something. Without this core, a sentence fragments and loses its power to speak. Indeed, a sentence only becomes complete when it contains at least a subject and a verb. Subjects and verbs must also agree with one another. That is, the form of the verb has to match the number of things in the subject. A singular subject takes a singular verb, while a plural subject takes a plural verb.

    Incorrect: The two best things about the party was the food and the music.

    Correct: The two best things about the party were the food and the music.


    5. Misplaced Or Dangling Modifier

    A misplaced modifier is a word, phrase, or clause that is improperly separated from the word it modifies or describes. Sentences with this error can sound awkward, ridiculous, or confusing. A dangling modifier is a word or phrase that modifies a word not clearly stated in the sentence.

    A run-on sentence occurs when you connect two main clauses with no punctuation.

    Incorrect: After finally setting off on the trail, the morning felt more exciting.

    Correct: After finally setting off on the trail, he felt the morning was more exciting.

    6. Run-On Sentence

    Incorrect: She tried to sneak out of the house her mother saw her leaving.

    Correct: She tried to sneak out of the house, but her mother saw her leaving.

    Incorrect: He ran through the field as fast as he could all the while the rain was soaking him to the bone.

    Correct: He ran through the field as fast as he could. All the while rain was soaking him to the bone.


    7. Lack Of Parallel Structure

    Faulty parallelism occurs when two or more parts of a sentence are similar in meaning but not parallel (or grammatically similar) in form. It often occurs with paired constructions and items in a series.

    Incorrect: The key directives of his boss were clear:

    • Meet monthly sales quotas.
    • Aggressive marketing techniques.
    • Reporting in every day.

    Correct: The key directives of his boss were clear:
    • Meet monthly sales goals.
    • Practice aggressive marketing techniques.
    • Report in every day.

    8. Split Infinitives

    An infinitive is the word “to” with a verb. A split infinitive separates the word “to” and the verb with another word (often an adverb). There are no grammar rules that prohibit split infinitives, but many experts disapprove of them. If the sentence sounds awkward by correcting the split, our rule of thumb is to go with what makes the most sense in the context of your writing and for the ease of reading.


    Incorrect: He wanted to gradually improve his strength by increasing the weight.

    Correct: He wanted to improve his strength gradually by increasing the weight.


    References

    • https://www.linkedin.com/learning/grammar-girl-s-quick-and-dirty-tips-for-better-writing