To the incredible NinjaTrader Community,
After many years, I’m writing to share that I’m stepping away from my customer-facing role. This journey has been truly rewarding, and it’s been an honor to assist thousands of you over the years, watching your success stories unfold and learning from our failures.
While I’m not leaving NinjaTrader, I’m transitioning into a new role behind the scenes. This means I’ll no longer be the face answering your questions daily, but rest assured, I’m still part of the team working to make your experience even better!
I want to give a massive, heartfelt shout-out to all the NinjaScript (NS) Superheroes - the brilliant community members who over the years have tirelessly provided samples, test scripts, and expertise on the archived forums; competing with our NinjaTrader staff to make a true community. I have learned so much from your generous contributions over the years, and your efforts are a huge part of what makes this community so strong.
The Future of NinjaScript Support
The great news is that we are focused on making official support resources even better! We have more mechanisms completed and in the works to officially share examples, test scripts, tips, and official direction straight from our support teams on the support site. This will centralize and enhance the help available to everyone.
Notably, NinjaTrader Engineering Support has not gone away. We are staffed, knowledgeable, available, and still producing content. Our support is no longer on the forums. We’ve made the choice to redesign our support to be more intimate, focused, and reactive, while also making the highly valuable insight we gain publicly available for our entire community, not just those with the right search terms for a current stumbling block.
You can already see some of this progress here: https://support.ninjatrader.com/s/article/NinjaScript-Developer-articles
Staying Connected
This was the result of your requests to consolidate the support research we’ve provided to individuals as resource available to all of you.
I’ve made meaningful connections with so many of you, and those relationships don’t end here! While this chapter is closing, I am not gone. I can still be contacted, I’m still with NinjaTrader, and I look forward to seeing the amazing things you all continue to build.
Thank you, from the bottom of my heart, for making this such a wonderful part of my career.
Onward and upward!
Some tips I have for interacting with our support staff:
- Don’t be afraid to ask questions. This is the most important advice I can provide. Either you learn or we both do. That’s progress baby.
- If something has gone wrong, provide your full log and trace files. We start our investigation with the startup sequence in your log and trace. Sometimes that’s not in the most recent files.
- If you have an error, provide the full error message. A screenshot is just fine. A file or text we can copy and paste from saves us time, but it’s no deal breaker.
- Be reckless try things and break things using Sim accounts. Generally we can always get you back to a fresh start or we’ll learn more and report critical issues.
- Add debugging prints. If you need assistance with logic, the first thing we will ask for is debugging output. Even if the issue is a bug that’s our responsibility, we’re still going to ask for the debugging output to add to our report. https://support.ninjatrader.com/s/article/Developer-Guide-Debugging-using-Print-and-TraceOrders
- Reduce, re-use, and recycle. To report a bug, we need the most reduced, bare-bones, smallest script possible that can still reproduce. Our developers are running 10 mph over the speed limit at all times and always appreciate simple, easily reproducible, and concise direction. They don’t want to figure out the steps you took to encounter the issue. Those simplified scripts are good for more than reporting issues. A working example in the bank to use as a template for a future project is worth more than gold (at whatever price it may be trading at).
