Skip to content
hello@zborys.dev v0.2 · beta
← Back to notes // notes tool

Pine Script archive: 50+ indicators, what survived

I have written more than 50 Pine scripts. Five or six survived as daily-use tools. The rest is a graveyard, and the graveyard taught me what survival looks like.

[tool] 19 Feb 2025 #pinescript #tradingview #trading #tools

// body

If I open the cloud folder, there are 53 Pine Script files. Most of them are dated 2021–2023, when I was building a personal toolkit and pushing publish on TradingView every other week. Today I use five of them daily, two weekly, and the rest sit there as a graveyard.

What the survivors have in common

  • One job. Every survivor does one thing. The dead ones tried to be three indicators in a trenchcoat.
  • Readable on the chart. Two colours, one or two lines, labels only where they matter. The dead ones look like a Christmas tree.
  • No magic parameters. Every input has a clear meaning. The dead ones have multiplier, tolerance, filterStrength with no story.
  • Stable defaults. The survivors work out of the box. The dead ones require ten minutes of tuning before they make sense.

The five I use daily

Keltner Zones with squeeze. Volume profile by session. Wyckoff event labels (a port of my cTrader one). A custom range-day detector. A simple multi-timeframe trend ribbon.

Together they take maybe 40 lines of inputs and 600 lines of code. That's a healthy ratio.

What the graveyard taught me

The instinct, when an indicator "doesn't work," is to add a feature. That instinct is wrong. The correct move is almost always to remove a feature. Every survivor in my list is the third or fourth version, after I deleted code, not after I added it.