November has been a big month for me. I haven’t slept much in the last few weeks, but I still have some time to do a side project, and stacks- CLI is getting a good response on GitHub these days. I accidentally appeared on the homepage of HackerNews and GitHub Trending, so I decided to sort out the inner journey and share it with more developers.

Project Links:

  • stacks-cli

  • Sports – cli – making – a screenshot

  • Sports – cli – hackernews – screenshots

Incentive motivation:

Wappalyzer is basically a tool for analyzing the back of web pages using Chrome Extension. Usually, when I see a good website for development, I will automatically click on it, but recently I have seen a lot of CLI projects based on JavaScript development. I thought it would be a good side project if I could port Wappalyzer to the Command Line interface.

After all, Posting urls to the CLI is not as fast and direct as using Extention directly, but I still think that each Extension has its own market. Maybe A doesn’t like installing so many extensions, after all, Chrome is so efficient. Maybe B simply likes the low-key and fast style of CLI, so HE takes CLI as a priority.

Stacks – CLI’s goal as a side-project has been achieved by providing developers with one more option within the limited number of options available to them, in addition to being able to practice on their own.

Mentality mindset:

Don’t be discouraged if you have researched something new and made it and shown it to your friends only to get a comment from SoSO, because stacks-cli actually does that. Chances are that the product itself is not good enough, and it doesn’t have the highlight that will be noticed at first glance, but also it doesn’t have enough audience. If the Reddit community doesn’t respond, try HackerNews Po!

There are always more people with similar needs than you think.

Of course, the more important premise is that please roll up your sleeves first, and try to make things out of trial and error. Step by step, it is definitely closer to the imagination in your mind than a bunch of empty words.

Recommended tips:

README is important because, as mentioned in the myth of the Man-month, the time spent writing programs and writing files should be split as evenly as possible. Of course, this is the ideal state for free work, but corporate projects may not be able to do this, and even simple handovers can be difficult with high turnover.

However, since it is an amateur side project, you might as well try to do more. After all, from the perspective of the developer, what you take for granted is likely to be a black question mark in the eyes of others. If you think too strictly, you will easily lose yourself. It is also important to be able to clearly convey your ideas in words and make them widely understood.

As for where to go for publicity, I would suggest first visiting HackerNews, Reddit/ Programming and discussion forums. Foreign developers are quite willing to give you advice on these forums, such as Issues and PR. If you log on HackerNews, you can generate at least 5,000 ~ 10,000 unique visitors. If you feel that something is really good and solves some problems, give yourself more confidence and try to share it with more people.

Conclusion conclusion:

Stacks – CLI doesn’t have any technology in it, it’s just a port of Wappalyzer to the CLI interface, and being welcomed by foreign developers is pretty lucky, but overall it’s a pretty amazing experience.

After finishing one thing, I always ask myself repeatedly, what can I do better and what can I improve? At this age, I may be starting, and there may be a big gap from my imagination. At this time, I can try to think, anyway, AS a non-CS undergraduate, I have nothing to lose. Once you hit the wall, there’s nothing to be afraid of.