Sometimes, I wish that I am a billionaire, so that I could let people using my software for free, completely. And the key point is, they know that it is free, absolutely. Because I am a billionaire, they know.
So, just keep it up. Anything you wrote is not important than the thing you do. Don't let people sink you in their perspective about the world they saw.
Open-source software needs a ton of efforts, tears, bloods. Above of the passion, you know that it should be pay-off, fair-price at least, for you and your people hard-works.
At the end, plan is just a plan. Just go to have a chance to fix it.
oh! I am a CTO, and, I code everyday. so, you don't need to step back (actually, anything you choose, it should be a step forward). no-one can stop the things you love to do. also, no-one can justice on the things you do to feed yourself too. find the thing you love, the thing can feed yourself, do it, both. at the end, goodluck with your choose.
Thank you, your feedback help me alot @theamk. The document, term `free`, `forever` will be fixed.
At the first point of view, I want to create a tool which can help our team run the bash script easier, faster, safer, with clearly reports, so I build rfsh, free for usage. You can input a .csv file, a bash script .template file, rfsh will take care the rest.
Please let me know in-case there have anything else you think I should do for improvement.
Good software should be Free, basic needs should be fulfilled. I don't want to make rich by charging on things running on your own resources (your computer, your sever, your cloud,...), so I build RFSH.
I have worked for my current company since 2015, so these are tactics I used:
1/ 30m meeting. Everyone who wants to make a meeting with me must via the invitation ( send to my calendar ), and the meeting duration must be 30m ( or less than ).
2/ Document by priority. I track the top 3 problems by their frequency and make the document ( troubleshooting ) next week. Automate your work first, after that, do delegate.
3/ Keep the fire burning. I mean you have to find your top 3 reasons, why you are still here, and work for the company. If you tried but can't find them, leave.
I built several tracing systems, but none of them capturing & storing the API's response, cause too expensive, you know. Could you share more about your tracing system? I think we can learn from others.
I think that, the author is focus on the strategy, but not tactic. He mention more about the important of understanding your own value system and which position the salary is in this system. How to increase your value in current company instead of finding others.
1/ We should have an API tracing system, hosted in a server for example, which capture all requests, including the params, headers, response. with some secure rule, e.g. hide Secret-Token header.
2/ Each request will have a header, its value is the request-id for example
3/ Whenever a bug come, we just need use request-id from 2/ and search the information in 1/
you’re just copying their meeting notes prompts and turning them into your own summarized apps. dude!