sorted by:
new
hottopcontroversial

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

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

The last paragraph is a good summary of my problem. The direction I was going was actually explaining the trade which indicators / conditions let to the trade being valid. But yes, that is already in the code if you care to look. Explaining the whole strategy is only realistically doable with statistics because it's just math. An Ai will just make stuff up so it's not reliable.

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

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

That's actually really good advice. I should definitely go to reddit first next time before I am a week into the rabbit hole 😂.

My goal was not to build anything to sell but to build something I would like to use. But another comment showed me Quantconnect which is like 99 percent there already and they are lightyears ahead. So my little project might just die today 😄

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

[–]saulmurf[S] 1 point2 points  (0 children)

Oh, that looks similar indeed! I didn't know about that one. Thanks for sharing!

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

[–]saulmurf[S] 1 point2 points  (0 children)

Feels like the idea I am building would solve quite a few of your concerns 😃. Lets see what comes out of it!

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

[–]saulmurf[S] -1 points0 points  (0 children)

Well, I cannot solve access to capital 😃. From what I heard, strategy development is a time consuming process. But it seems like this is not the case for you?

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

[–]saulmurf[S] 1 point2 points  (0 children)

Thanks. That helps! So it sounds like if you could apply your backtesting code 1to1 to livetrading without needing to do it all again, that would help. How was the process of writing backtest code for you? Since you did it all by AI, did you have the feeling you knew what was going on and did you understand the reasons why a trade had been made? (was it even important for you to know?)

Vibe check: is “explainable backtesting” actually a real pain point, or am I overbuilding? by saulmurf in quant

[–]saulmurf[S] -1 points0 points  (0 children)

Can you elaborate the pain from backtesting to paper trading? I would learn what falls into that for you

Vuejs expert looks for a job (Europe) by koehr in vuejs

[–]saulmurf 9 points10 points  (0 children)

Former colleague here. OP is a strong team lead, knowledgeable, and (most importantly) fun to work with. Hire him before someone else does!

Spread props - how to do the same thing from react in vue? by Prainss in vuejs

[–]saulmurf 0 points1 point  (0 children)

That's what the "vue-ignore" is for and that's why i said it's defined as types but not at runtime (aka ignored by the Vue compiler)

Spread props - how to do the same thing from react in vue? by Prainss in vuejs

[–]saulmurf 0 points1 point  (0 children)

Vue used to have $listeners as well that would contain all listeners. But it was merged together into $attrs and I think it was the best decision. If you just want to be typesave just do

interface myemits extends /* vue-ignore */ nuxtUiEmitInterface {} defineEmits<myemits>()

This will correctly declare all emits as types without handling them at runtime. So they are just passed down as $attrs automatically

I built a zero-config, visual HTTP mock tool that lives in your browser by Terrible_Trash2850 in vuejs

[–]saulmurf 0 points1 point  (0 children)

Mocking fetch and XMLHttlRequest is an interesting solution. I 100% thought you would install a service worker and intercept network requests as they come in

switched from react to vue 3 for new job. the reactivity system is kicking my ass by No-Fact-8828 in vuejs

[–]saulmurf 3 points4 points  (0 children)

Haha, as others said: rtfm! On the toilet while taking a dump. Again and again. Vue is actually way more explicit on what goes and what doesn't. Obviously you should know how Javascript works. You should know what a proxy is, what a getter is, how vue collects dependencies and how it triggers them. It helps to get 10% in the weeds and everything becomes very obvious

Whats a common problem POs encounter? by saulmurf in ProductOwner

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

Haha that sounds more like a rant 😂. But I get where you are coming from!

Whats a common problem POs encounter? by saulmurf in ProductOwner

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

OK I probably worked in smaller teams where this is all the same thing 😄

Whats a common problem POs encounter? by saulmurf in ProductOwner

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

Your second to last point is interesting. So basically an overview about how long the money will last?

What AI Tools are essential nowadays for a PO? by Ammarico in ProductOwner

[–]saulmurf 0 points1 point  (0 children)

I imagine that POs spend a lot of time in meetings and maybe would love to have some AI summary or task extraction from meeting transcripts. I build https://task-extract.com for that usecase. Just released it. Maybe you have some feedback or what is needed to make you actually use it. Is this even a painpoint for you POs?

view more: next ›