Hello!!
Days since last (and first) newsletter issue have been very busy to me.
Here is a chart, I worked on CodeQue around 78 hours since then 📈
It’s almost 10 hours per week on average, huh. It’s in addition to my full time occupation!
Feels like a little bit too much? For me, definitely.
I mean, I’m kind of proud that I managed to do it and I’m working consecutively on CodeQue for more 7 months now, but I need a break to enjoy life.
I moved to seaside in Poland for 3 weeks and I will pause on working CodeQue that much during that period. To get back later with doubled power 💪
Ok, time for news!
Visual Studio Code extension pre-release
TL;DR
I should say: FINALY!
It’s just pre-release, with basic functionalities, but I really wanted to share that with the World.
It would be awesome if you could try it and send me some feedback in DM on Twitter.
There is a plenty of features and improvements I will add soon.
I plan to make it possible to edit files directly in search results list!
It would be cool to be able to include/exclude paths as well.
Conclusions from public release of CodeQue CLI
At the beginning of July I’ve made a “public” and “official” release of the CLI tool for CodeQue.
And guess what! I highly doubt anyone really downloaded it and give it a try 🥲
All the downloads that it has is are probably from bots.
It was disappointing at the begging, but I then I realised it was a good lesson to release and fail fast.
I was waiting with the release for so long. I wanted to prepare website as best as I can etc.
To be honest I could release that CLI MVP after first 2-3 months of work on CodeQue and then I would realise no one is willing to use search tools via CLI anyway, so maybe it would be better to start VSCode extension earlier 😀
The good part was I’ve added tracking to the website and made get-started page to give impression that VSCode extension and ESLint Plugin are ready
33% (89) of visitors clicked “Visual Studio Code” and 24% (65) clicked “ESLint”
Which is not bad conversion (If we can call it conversion).
It gave me some validation that I’m not the only person finding CodeQue useful 😀
Plans, Plans, Plans
Lessons learned, I’m moving forward.
I will now release more often, and I will release smaller parts.
I will follow the Roadmap, which means I will:
- implement improvements to VSCode extension and make if fully featured
- probably skip extending docs for now, until I get some questions from users 🥲
- start working on ESLint plugin
- extend searching by various improvements and functionalities
ESLint plugin will be probably pivotal for future of CodeQue. To make it work I have to make search parser/language agnostic as much as I can.
It will open a path for extending search for other programming languages.
I also hope to get some directions from community at some point. Right now I’m developing what’s useful for me, but at some day I will run out of my own use cases (and motivation, I receive very little feedback comparing to my effort 😔)
We all have limited time, so I would love to focus on what’s most useful.
What’s your CodeQue use case? I would love to hear, it will help me to catch the wave!
Catch you soon, probably in month or so!