I'm wondering about two things related to development of customer-facing programs that use paid APIs in the background:
Are you using your own API key and pay for the usage? How can you justify operation of programs that produce high costs but no income?
Isn't the API publicly exposed to the client-side and possible subject of theft and abuse?
This renders the extension pretty useless for older papers, doesn't it? There doesn't seem to be a fallback to prompt older papers in a whole because it exceeds the prompt limit.
Act is truly helpful and I appreciate its development but it has its caveats. For instance, I face problems with passing parameters to composite actions.
Git's Most Wanted is a ready-to-use online presentation of Git commands needed in the everyday workflow.
It targets developers who just started with Git and need a curated source of what is really important, who are already familiar with Git but need a refresher or who are already familiar with Git GUIs but intend to switch to the CLI.
Shell environments, why didn't I thought about this earlier? I'll definitely enjoy this as soon as I've figured out the best way to integrate it with my development processes.
Usually, I use Viscose development containers where system programs are installed via Docker. However, it's quite tedious to manage installation and versioning of these programs.
I can only second learning from documentation rather than using (video) tutorials or blog posts.
If you're strong in reading and gaining knowledge from documentation, you will generally be able to decrease your time to create working solutions. The reason is that you get faster in finding the information you need and become independent of the availability of explanations by other developers.
I'd only consult other explanations if the documentation is poorly written or my way of using the software is uncommon and I'm looking for opinions or alternative solutions.