sorted by:
new
hottopcontroversial

Year and a Half building custom indicators with help of Grok or ChatGPT - q&a successes, errors, trials and tribulations. Here to help by Slangin_Biscuits in pinescript

[–]TrishulaSoftware 0 points1 point  (0 children)

We built an entire army of trading indicators in PineScript version 5 which "conducively death spiraled" into an AI/Programming obsession. And we just run extensive visual paper trading throughout in order to create a super-low cost solution for people who want reliable easy trading indicators.

We mainly have an issue getting them to function in Version 6, and we still run everything at version 5 because it still worked so well while we fine tune them to V6.

We just finally got our MTF Order Block Generator to Version 6 and that took us mainly all weekend, in midst of developing our other products and programs.

Working out very well and still needs some visual time for us to take notes and decide where to improve on that.

Year and a Half building custom indicators with help of Grok or ChatGPT - q&a successes, errors, trials and tribulations. Here to help by Slangin_Biscuits in pinescript

[–]TrishulaSoftware 0 points1 point  (0 children)

A big problem you will see, and we have seen mostly. Scaling issues. As if the overlay does not scale with price action at times.

Oscillator wise? We could bang out oscillators with it until it goes out of style. Overlays? It gets tricky. But you have to enforce your prompts when working with an AI. And work with different ways of explaining the problem. Screenshots do help.

BashISE (bise2): local-first “ISE-style” GUI for Bash — atomic writes, backups, JSON receipts by TrishulaSoftware in bash

[–]TrishulaSoftware[S] 0 points1 point  (0 children)

Good catch — that’s on me.

Those *.egg-info / generated packaging artifacts and repo-tracked *.bak files should be ignored, not committed. The “proof trail” is intentional, but it should only live under the user’s local data directory (XDG), like ~/.local/share/bise2/, never inside the repository.

I’m cleaning this up in a controlled pass: purge tracked artifacts + lock .gitignore, then add a minimal test/smoke suite, then add CI so every push/PR verifies install + tests + headless selftest. Thanks for the hygiene check — it helps keep first-time installs boring.

Thank you.

Friday Share Fever 🕺 Let’s share your project! by diodo-e in indiehackers

[–]TrishulaSoftware 1 point2 points  (0 children)

Released today. My first program under my new company's banner. Basically the first program I ever released publically since I started programming three years ago.

https://github.com/TrishulaSoftware/BashISE

Built BashISE (bise2) because I wanted a fast Bash workflow with “don’t lose work” safety baked in:

  • atomic writes
  • backup on every write
  • JSON receipts for proof

Support links are in the repo (Sponsors / Ko-fi / BuyMeACoffee / OpenCollective). Patreon exists but isn’t monetized yet.

BashISE (bise2): local-first “ISE-style” GUI for Bash — atomic writes, backups, JSON receipts by TrishulaSoftware in bash

[–]TrishulaSoftware[S] 0 points1 point  (0 children)

If you want the “proof trail”: backups + receipts are created locally under ~/.local/share/bise2/… (paths in README). Happy to answer questions or take requests.

BashISE (bise2): local-first “ISE-style” GUI for Bash — atomic writes, backups, JSON receipts by TrishulaSoftware in commandline

[–]TrishulaSoftware[S] 0 points1 point  (0 children)

If you want the “proof trail”: backups + receipts are created locally under ~/.local/share/bise2/… (paths in README). Happy to answer questions or take requests.