Technical Writer | Fullstack developer
Joined March 2021
- Tweets552
- Following354
- Followers122
- Likes2.2K
Zero your mind that nothing is easy. Work is meant to be hard. If it's not hard, it's not work. And doing hard things will stop feeling scary.
My head. 😮💨
The Google Style Guide is so voluminous. I’ve been studying it for days now.
It’s been an eye-opener, but still, it’s the kind of task I wouldn’t want to do a second time. 😂
Where did all the freelance technical writing gigs go? Seriously!
OpenReplay, Smashing Magazine, SitePoint, CSS-Tricks. Just to name a few. Their writing gigs are mostly gone. They are either no longer accepting writers, not replying, or have shut down their writing programs.
One thing I regret a bit now is that I don't have valuable experience or deep expertise in any of my skills (technical writing, frontend, full-stack) that I can confidently use to apply for a full-time job and hope to get a response. This is something I want to change.
I have achieved my goals for the time, precision, and recall, so I am done building the core of FluentDocs 🎉
The time went down from 2 hours for the full documentation to just 5 min. Precision improved from 52% to 96% while recall took a slight hit, dropping from 91% to 86%
🧵
Honestly, from the beginning of this project, I have had doubts about its usefulness because tools like Bluehawk can already test documentation code examples to keep them accurate. However, from what I understand, those tools work best for tutorial-style code examples.
Previously, I mentioned that I was almost done building FluentDocs before I had to pivot. I don't want it to seem like I was lying or simply jumping from one product to another, so here's what it looked like.
Founders might just be the most resilient people on earth, because when you hear about their failures, you will be left in awe.
One thing to note is that failure is not the end; it is part of the process. Learn from your mistakes, pick up the pieces, be humble, and continue.
This podcast is packed with insights. It's a must-watch for aspiring entrepreneurs.
From the Managing Director of PalmPay Nigeria and the Country Manager of inDrive.
youtu.be/DwiPvSSMLFI?si=0AXP…
This podcast is packed with insights. It's a must-watch for aspiring entrepreneurs.
From the Managing Director of PalmPay Nigeria and the Country Manager of inDrive.
youtu.be/DwiPvSSMLFI?si=0AXP…
Currently, I am trying to create traceability links between the docs and the code, which will serve as the foundation for drift detection.
Using a subset of the LangChain documentation as a test case, I have achieved ~50% precision, ~90% recall, and ~1 min recovery time.
Is FluentDocs dead?
To keep it short: no. To provide fast-moving teams with more reliable drift detection, I have pivoted to a deterministic-first approach using static analysis for accurate drift detection and LLM only where needed.
fluentdocs.dev/
