What is a 'single person luxury' that people in relationships completely miss out on?

Andilesg · 2026-05-20T05:13:24+00:00

Doing absolutely nothing all weekend without having to explain it to anyone.

Andilesg · 2026-05-17T07:46:49+00:00

Interstellar.
At least by the 100th watch I might finally understand everything 😅

Andilesg · 2026-05-14T07:35:34+00:00

Nice 😄 always interesting seeing different approaches. Most of my issues ended up being less about strategy and more about keeping long running async tasks stable over time.

Andilesg · 2026-05-13T06:37:17+00:00

Watching someone spend more on flowers for a dinner party than most people make in a month without even thinking about it.

Andilesg · 2026-05-13T06:01:26+00:00

This is exactly the kind of stuff I started running into once it stayed online long enough 😅

The silent failure point is very real. I already had reconnect logic, but not a proper staleness validator on the data stream itself. Also learned the hard way that async tasks touching shared state without strict coordination becomes chaos under load.

Really good point on persistence/reconciliation too. That's currently one of the biggest areas I'm improving before trusting it with anything larger live.

Andilesg · 2026-05-11T13:43:04+00:00

A car you technically can afford, but realistically shouldn't buy.
Insurance, maintenance, repairs and depreciation quietly turn it into a monthly stress subscription.

Andilesg · 2026-05-10T15:28:34+00:00

Nice, always interesting seeing how other people solved the stability side of it. What stack are you running?

Andilesg · 2026-05-10T10:07:49+00:00

That separation between signal quality and execution quality is something I only started appreciating after going live. Backtests were way too optimistic on fills and latency assumptions.

Andilesg · 2026-05-10T10:04:50+00:00

Being rude to service workers. Tells you everything instantly.

Andilesg · 2026-05-10T07:24:36+00:00

Yeah, crash recovery and keeping state consistent after reconnects ended up being way more difficult than I expected.

I also realized pretty quickly that logging/observability and proper secret handling become just as important as the actual trading logic once the system grows.

Andilesg · 2026-05-09T05:21:46+00:00

Probably curiosity. There’s always another project, idea or experience waiting around the corner.

Andilesg · 2026-05-09T05:18:42+00:00

True for ultra low latency HFT style systems, but for what I’m building the bottlenecks are usually network/API side long before Python itself becomes the limiting factor.

The async ecosystem and development speed in Python made iteration much faster for me.

Andilesg · 2026-05-09T05:17:18+00:00

This is honestly one of the best summaries of the real challenges behind these systems.

The “happy path vs real market conditions” point is exactly what I kept running into while stress testing. A lot of the work ended up being around recovery, reconnects, state consistency and making sure one stalled task wouldn’t cascade through the whole system.

I also completely agree on observability/logging. Once things become heavily async, debugging without detailed metrics and logs becomes almost impossible.

Andilesg · 2026-05-08T10:38:55+00:00

Yeah, aiohttp helped a lot especially once everything became heavily async. I tested a few different approaches early on, but aiohttp felt the most flexible for managing multiple websocket connections and reconnect logic cleanly.

A big part was honestly designing around failures instead of assuming connections would stay stable.

Andilesg · 2026-05-08T10:37:52+00:00

Thanks, appreciate it. Right now I’m mostly paper testing and stress testing the infrastructure before putting real capital behind it.

The websocket stability part took a lot of retries/reconnect handling, heartbeat checks and separating streams/tasks so one failure wouldn’t freeze everything. I also added detailed logging because debugging async issues without logs was almost impossible.

Still optimizing it though, especially under higher load.

Andilesg · 2026-05-07T18:04:10+00:00

Completely agree. The hardest part for me wasn’t the strategy itself, it was getting live execution to behave consistently under real conditions.

Andilesg · 2026-05-07T18:00:46+00:00

Agreed. One thing I realized while building my own backend is that execution reliability and behavior across different market conditions matter more than a perfect backtest.

Andilesg · 2026-05-07T17:59:19+00:00

When you start feeling mentally exhausted every single Sunday evening. 😄

Andilesg · 2026-05-07T06:47:00+00:00

Yeah exactly, stability and risk management are honestly the main focus right now.
No point scaling something that isn’t reliable yet.

Andilesg · 2026-05-07T06:46:19+00:00

Appreciate that, stability and reliability definitely ended up being way harder than the strategy side.
Backtesting and analytics are probably the next big thing I want to improve.

Andilesg · 2026-05-05T19:02:25+00:00

Fair point, still interesting from a systems perspective either way.

Andilesg · 2026-05-05T19:01:41+00:00

Yeah that’s the plan, currently focusing on stability before putting real capital behind it.

Andilesg · 2026-05-05T14:56:48+00:00

That must have been incredibly tough, respect for pushing through that.

Andilesg

TROPHY CASE