Prove it with results, not code
Four years turning a 1.9 rating into a 4.6
Four years after founding Connect Code. It was a stretch of bringing back customers who had left.
Four years after founding Connect Code. If I had to sum up that stretch in one line, it would be this.
Four years of bringing back customers who had left.
1.9 → 4.6 stars
The GS Caltex Energy Plus app was sitting at a 1.9 rating. Customers who had left weren't coming back.
Over three years that rating became 4.6, and the journey was documented in a Longblack interview.
The core was not "adding features." It was re-asking why people left.
- On which screen did the customer get angry?
- Which step pushed them away?
- What do we have to promise again to bring them back?
Code was the last tool we used to act on those answers.
360k+ visits, certified top freelancer
Over the same stretch, the blog passed 360,000 cumulative visits, and I was officially recognized as a top freelancer on Wanted.
What these numbers meant was one thing.
You can build an identity on top of results.
One-line conclusion
What an engineer has to be responsible for, all the way to the end, is not the code, it's the result.
→ The starting point came from [why I built Connect Code](/stories/why-i-built-connectcode).