tjvc

I noticed this too and clicked this thread wondering if it would show up! Still an awesome watch.

I think this is a good take. I hope to do the same.

For the understanding part, Andrej Karpathy has a YouTube playlist that explains neural networks. I made a start on it today and found it quite accessible.

https://www.youtube.com/watch?v=VMj-3S1tku0&list=PLAqhIrjkxb...

I'd be interested to hear more about this, as someone potentially in a similar position. What kinds of problems did you come up against where you felt your math skills were a limiting factor? What branches of math did you focus on learning?

> I'm reading online that I was stupid for buying a house in a bubble and that rates need to go up and house prices need to fall.

I don't think you're stupid. You couldn't have foreseen the sequence of events that has produced this situation. For what it's worth I did a very similar stress test, with similar assumptions, when I bought my home. I feel like this volatility is something of a rude awakening for our generation.

What does the 500,000 figure represent? There will be many people whose fixed-term mortgage rates expire in a now much higher-rate environment, including those on longer-term fixes negotiated before the pandemic.

This is great! Really creative use of different data sources.

You should expect some pushback on your pull requests, particularly early on. It’s a good opportunity to learn, and a good sign that your team cares about code quality and continuous improvement.

You mention bugs specifically, for which I think the best remedies are good unit tests and careful consideration of edge cases (which often go hand in hand). Other smaller issues such as deviation from framework conventions and performance problems can be helped by getting to know your languages, frameworks and database better, which comes with time. More generally, there are lots of good resources out there to help you improve the readability and structure of your code - Clean Code by Robert Martin (particularly the earlier chapters) and Sandi Metz’s books and talks are both good starting points. Issues with your general approach to solving problems are harder to address, but reviewing others’ code, learning about design patterns and pair programming can all help here.

In terms of actionable advice, I’d encourage you to briefly discuss your intended approach to a problem with a colleague before starting work: this can help expose issues in advance. Even better, pair program on the implementation with another engineer. Just pairing on the review can also help to reduce the back and forth and get code shipped faster.

That makes a lot of sense - thanks for explaining! :)

Great article, many thanks.

> Rails auto-management needs to be conservative and cautious, therefore inefficient

Can you help me understand this better? Are you saying that Rails tends to hold onto connections for longer than it needs to?

This has been my experience too. I was looking forward to the feature and upgraded straight away to try it out (something I'd never normally do!). But I've found that response to commands is flaky, there's a noticeable performance impact, and, worst of all, dictation doesn't seem to be supported in non-Apple applications, e.g. Slack. Pretty disappointing.

I'm still using the "basic" dictation feature, which works well enough, but doesn't support editing.