_thinx

you want to open source granola — so why not build a research team and create your own prompt system?

you’re just copying their meeting notes prompts and turning them into your own summarized apps. dude!

Just read your idea.

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.

Good luck and best wishes!

do self-research first[1], then, give it a try. small pet project should be. if it really fit your taste. go with it.

[1] https://go.dev/solutions/

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.

haha yes, me too!!! curl is useful, and so popular these day. Always use curl install for tools which I contribute to [1].

[1] https://github.com/docsion/rfsh#install

How do you avoid that at Bruno v1.0.0 ? I means Postman playbook > vc funding

me too! or, you can give httpie [1] a try

[1] https://httpie.io

https://github.com/docsion/rfsh if you are familiar with bash script , feel free to add feature request via PR (e.g run test for postman collection)

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.

Yes, the nice feature is snapshot the response to minimize teamate's efforts.

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.

Hope it can help.

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.

Agree! That's why I think a centralize tracing system is too expensive. Still looking for a better way to send API bug report.

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.

Why don't you use HN ?

Ah, I got some ideal here. So, you mean:

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/

Right ?

yes, thinking about that. Actually, an API bug report should be:

1/ secured, the credentials should not be exposed.

2/ enough information, e.g. the response must be snapshot, general parameters should be transparent.

3/ easy to re-produce and confirm resolved.

What do you think?

Hey @zhangruinan, could you show your product here? I can be your beta user :)

How does it works ? Could you give some example please :D

Sorry, maybe I don't say clearly enough :(. Let show some code, hope it easy to understand.

I found that, the order listing API doesn't work as expected. I send the curl to my teammate. Please take a look at `-H 'X-Access-Token: SECRET_TOKEN' \`

```

curl 'https://mocha.lozi.vn/v6/users/me/orders' \ -X GET \ -H 'X-Access-Token: SECRET_TOKEN' \ -H 'Host: mocha.lozi.vn' \ -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:101.0) Gecko/20100101 Firefox/101.0' \ -H 'Accept: /' \ -H 'Accept-Language: vi_VN' \ -H 'Accept-Encoding: gzip, deflate, br' \ -H 'X-Lozi-Client: 1' \ -H 'X-City-ID: 50' \ -H 'Origin: https://loship.vn' \ -H 'Connection: keep-alive' \ -H 'Referer: https://loship.vn/' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Site: cross-site'

```

The problem is:

1/ If I don't replace the real token by SECRET_TOKEN, others can use it to buying their own stuffs, by my token. :(

2/ If I replace the real token by SECRET_TOKEN, it's so hard to detect what the problem is, cause my teammate can't see the response, and can't request to re-produce the issue too.

I thought about that way. But, we can't re-produce or see the API's response. So, it so hard to detect the API's issue, right :?

Actually, I'm a terminal guy, and I like to use curl than postman

I think that way is not secure enough. For example, I can use Secret Token, which is exposed in curl, to do something like ~ buying my own stuff .

So, there have anyway to secure the curl ? But we are still easy to detect the API issue.

I was stressful whenever my teammates, talented developers, share the curl, which including the secret credentials like - Authorization Token, for detecting and resolving the issues. So, I am curious that how you guys do that ? There have any better way to send an API bug report ?

Updated:

--

I think that way is not secure enough. For example, I can use Secret Token, which is exposed in curl, to do something like ~ buying my own stuff .

So, there have anyway to secure the curl ? But we are still easy to detect the API issue.