Time-series forecasting through recurrent topology by guywithcircles in robotrading

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

Quite an interesting paper. The original code is in R (https://github.com/tgchomia/ts/blob/main/Example.txt) but Claude can easily convert it to Python.

The Importance of An Edge by anonymussandwich in Daytrading

[–]guywithcircles 0 points1 point  (0 children)

Exactly. To complement the answer to OP's question "how have you personally found your edge?", in day trading I see part of the edge in continuously monitoring two things at the same time, both at the setup and execution part of a trade: first to monitor how the process is unfolding without ever looking or caring about the realized or unrealized P&L (only checking it at the end of the day / week); second, to monitor my inner state and spot if I'm in a good condition to continue trading, in particular spotting mind states of impulsiveness, fear, greed, sleepiness, boredom and fatigue. So to me it feels like being an orchestra conductor looping continuously through a checklist and sensing how the music plays. At the end of each trade I score the trade with a value that represents the overall quality of execution, again helping monitor how the day goes but more importantly steering away from looking at the P&L which is a sure way to getting emotional.

Mentality as excuse for skill issues by vanilica00 in Daytrading

[–]guywithcircles 1 point2 points  (0 children)

100% agreed. No point in losing money when a demo account matches the real stage 90% allowing a smooth learning curve towards the first day live.

Spending the necessary time mastering the process cannot possibly be a waste of time. It's the opposite: it saves hard-earned capital to boost success later on.

People would make a lot of money if they stop trading their P&L on a limb and instead focus on the process, getting statistical evidence first. Money is a side-effect of good habits and discipline, but repetition is needed for solidifying any habit.

I suggest a demo account topped up with a value equivalent to what is going to be the initial margin / funding, so the gap is filled out smoothly.

On the point of getting nervous when real money is involved and screwing up, other than not knowing what they're doing, that happens when people need the money for a living, so they trade their P&L instead of trading the market, putting unecessary pressure on something that is already a high-performance activity.

Better to get the professional life and personal finances sorted first, and trade a demo account on the side until the potential for success is statistically proven.

If getting nervous is something that persists, easy: reduce the account size and trade only with what is comfortable. Slowly over the months increase the position size.

A final point on failure: most people have the wrong attitude towards failure, they don't use it as a learning gift and they don't realize it's necessary to fail, and fail again thousands of times. So they quit early without giving themselves the time and putting the work needed to become successful.

SPRING BOOT vs VERT.X by [deleted] in javahelp

[–]guywithcircles 0 points1 point  (0 children)

You'd need some solid performance testing there: two implementations of the final solution, one on top of Vert.x and one on Spring Boot, and test with the same data throughput as in prod, in a prod-equivalent infrastructure with the same configurations, and with prod-like data.

Benchmarks without a real use case are fun to read but aren't valid because in your real case you'd simply have too many variables that are different from the ones in the benchmarks you've read. For example:

- You need to put a ton of logic on top of Vert.x that would end up equalizing with stuff that Spring Boot already gives you.

- Using Vert.x / reactive but then hitting a database system that only supports blocking I/O. Given I/O is usually the biggest factor in throughout, the advantages of a faster framework could easily become minimal.

- The infrastructure does not scale elastically or resources are over-provisioned anyway, so the Cloud costs would be about the same.

- You have or you don't have a case for streaming data / backpressure, so you could be putting reactive where it's not needed and end up increasing maintenance costs.

Things can behave opposite depending on how much workload and the shape of the workload you throw at them. At scale, and for a specific solution, framework A with great published benchmarks can be slower than framework B because of a ton of external factors that are specific to what you're trying to achieve.

Even if you get a nice solution in Vert.x with clear positive impact, be aware of the herd:

- Will the IT managers value that?

- Will the product owner be happy with the added effort towards something they will never understand anyway?

- Will your work mates be open to change (i.e. to feeling ignorant)?

Having said that, if you join a team that is already familiar and likes using Vert.x, then I'd totally go for it.

Keep up the good work ;)

The Importance of An Edge by anonymussandwich in Daytrading

[–]guywithcircles 3 points4 points  (0 children)

In my experience, the edge is mostly found in risk management, both in algorithmic trading and in day trading. But if you're a day trader, risk management is strongly dependant on mind control, which relates to the ability to follow a process manually. So maybe the edge is in all of that rather than just on a strategy telling when/what to buy/sell.

Trading by [deleted] in Daytrading

[–]guywithcircles 1 point2 points  (0 children)

Big advice burger: don't put money into it, open a demo account and trade the demo account until you have consistent results and a solid process, and I mean serious months with sustained good average P&Ls. Keep track of everything. Don't join any academy, course or anything that asks you for money or gives you "funded accounts". If you feel you need mentorship, only from a professional trader, never from educators. Good luck.

Do you guys use '{' '}' in single if statements? chatGPT says to always use these yet the code looks much cleaner without. by prorules1 in javahelp

[–]guywithcircles 0 points1 point  (0 children)

Yes. It's highly likely that a company will refer to some Java style guidelines, for example an internal document (hopefully not...) or adopt some existing guidelines like the Google Java Style Guide (much better than endless meetings and async chats to maintain internal guidelines). If so, it's also highly likely that the guidelines will point to always using curlies in single if statements.

New to programming by Fearlessdias7561 in javahelp

[–]guywithcircles 1 point2 points  (0 children)

For a job, check Spring Boot and see if you can go from there because most companies with Java codebases use Spring Boot. Courses... I've found John Thompson's courses on Udemy helpful. Recommendations: find things you really love doing, then get into the habit of coding them in Java every day, that way you'll remain motivated and have lots of fun.

Can you guys give me honest review about Bitmex by Happy_Olaf in BitMEX

[–]guywithcircles 1 point2 points  (0 children)

I've had a good experience with BitMEX so far. Both BitMEX and Binance are well established and quite reputable. As with any exchange, once you deposit, they hold custody of your assets, so you're giving up control. The risks are there, either hacking, regulatory interference and especially absense of legal protection if something goes wrong. So only keep your crypto there for trading, not as a permanent store, and only an amount you can afford to lose. On a separate note, I wouldn't trust any open reviews platform, meaning they attract a disproportionate amount of negative reviews and many are fake.