A new Flower in the bunch: Karel

About me

I have been in academics for the last 14 years and still today I am a parttime guest professor in civil engineering. So, I guess that figuring out stuff and making that stuff explainable has always been a part of me. When it was time to make a choice in career paths, I decided to take a leap and I joined the friendly faces at Flow. 

I feel passioned about developing solutions that actually help the user to find new information, regardless of whether that information is an unknown material property or a new sequence of buttons to press. For me, the value is in digging up the missing pieces and put them in the right place so our collective productivity increases.

When it comes to writing, I bring a fair bit of experience in authoring articles, manuals, books, patents, ... The writing tools used to create those products show high resemblance with the suite of instruments inherent to technical writing. It comes down to understanding structure. Discovering and revealing that structure I find pretty exhilarating.

The quick-fire question round

Flow: Software or hardware documentation?

Karel: "For now, hardware. That is probably related to my experience with physical prototypes I have built before."

Flow: Internal or end-user documentation?

Karel: "Both require a huge amount of care and the objective is to help each reader in the end. For now, I am most curious about end-user manuals and everything involved."

Flow: Agile or waterfall development?

Karel: "Although I like the sound of agile better, I would stick with waterfall for now. To grasp the complexity in my current project, a proper level-to-level approach proofs so much more valuable."

Flow: Time travel to the past or to the future?

Karel: "A chance to learn the answers on today’s collective questions? To the future please! 😊"

A glimpse of the future

I am happy in my current project and I am looking forward to learn – and perhaps build – new tools for making the writing process even more productive.