TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Short clarification: Certification - Classes - IT - Career Ideas
Subject:Short clarification: Certification - Classes - IT - Career Ideas From:e -dot- dickinson -at- gmx -dot- net To:Jason L <dotlogue -at- gmail -dot- com> Date:Thu, 15 Aug 2024 13:06:20 +0200
Hello Jason
I just realized that my first answer seems a little generic, after all.
Partly that's due to the differences I observed so far, be that IT or a
more traditional, device-programming and -manufacturing branch. Among
companies that is. There are overlaps, but there are differences in
detail too.
As far as technical writing in IT goes, I can recommend to
enhance/complete XML/JSON knowledge.
Scrum, and other agile methods: Good basic knowledge, definitely.
Try loooking into APIs and their documentation, I found that extremely
useful: Understanding them and being able to doument them is definitely
an asset. Swagger, RESTful API and their techniques, the applications
available and how to use them. Postman, for example.
ITIL(c)Foundation: It's the basic idea of the wole of 'software
lifecycle management' in IT (services) and when you work with
ticketings systems together with development (and often support input
which provides hints where to work on the docs more), ITIL is very
enlightening, not just as a method but as an approach, I find.
You seem to have quite some experience in other branches of business so
I leave that for others to properly comment on. :)
Personally I have some experience in management roles but I prefer the
'ground work': Handling, updating documentation and working with SMEs
on it. The subjects related to 'texts and technology' to sink my teeth
into. Perhaps you would want to think (or even try) more what is really
the best kind of task(s) for you: Management is a lot of operative
work, so I oberserve - and found.
*How to find out what else they might need in future jobs?*
Look at the job ads and their skills requirements. After some 10 or 20
of them you will most possibly see the patterns emerge, the recurring
skills and most wanted applications to be able to handle.
Again, hope this helps.
Good luck
Nina
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com