I've had this conversation with a number of financial-savvy friends. It seems that we all have different methods depending on what you're after.
For myself - I hate spreadsheets and updating and categorising data.
I have also tried a number of tools that will "attempt" to automagically present useful reports. But I've found that in 90% of cases - I'm well aware of what I spend on and how much I spend.
The data that really interests me personally is - savings, pensions, asset wroth tracking and scenario simulation.
I find that looking at growth over the past 3,6,12 months motivates me to do even better or look for more efficient ways of organising my finances.
At the moment here's what I do:
- Following a guide like (UK Personal Investing Flowchart)[https://ukpersonal.finance/flowchart/] to judge where I am at and what my short/long term goals are.
- I have automated transfers at salary date (T+3 days to account for variations) to investments and savings.
- I do a monthly scan through of current and credit accounts to make sure nothing unusual occurs as well as monthly credit-rating check.
- For Stocks and Shares I track current positions via Yahoo Finance.
- Lastly - every now and then I check-in to see how my Pension accounts are doing. So far I've gone through 4 different pension providers and tools - but none of them see to have good forecasting, scenario tools.
As a side topic recently got shown (Casual)[https://causal.app/] by a friend - I've been contemplating giving it a try.
> To slow down or stop attacks, we limit requests made by a specific user / IP. [...] While that confirms that we can limit unauthorized and bad users who make too many requests, the testing failed because we also blocked the simulated good users on the same IP.
I don't understand the problem this is trying to solve.
In the test setup both good and malicious actors are simulated on the same IP address (which coincidentally might also be a real world situation).
So you're trying to load test - but failing because you get throttled/rate-limited - which is good.
But how does Squid help in this case - doesn't it just mask away the actual load by caching content?
In that case are you actually testing the ControlAPI load - or how good Squid's caching is?
Aside from that - pretty interesting read. Would live to see a bit more technical detail and depth for the next blog post!
I ended up in twitter/reddit rabbit holes until I found a somewhat dodgy guy on twitter (@TerribleQuant - account is now deleted).
The person compiled a guide with study resources, courses, YT videos, podcasts, textbooks and everything else you can think of in 21 pages.
If you look for: BBM PUBLISHING INC “Roadmap” Resource Guide 3rd Edition you might be able to find a copy.