Last week, I finished my project proposal. It ended up taking a bit more time than expected, but I think the planning will pay off. I now have a clear path forward, both in terms of technical requirements and in terms of overall direction and motivation.
I also did the basic setup for the repository I’ll be using for the project.
This week, I’ll be jumping into the implementation of the project. To facilitate staying closer to 3-5 hours per week than I did last semester, I’ll try setting one task to definitely do and one task to do if I have time left over or feel like doing extra.
For this week, the main goal will be to get a basic proxy working that accepts a connection and forwards to a single backend. This will give me my foundational I/O approach.
The flexible goal will be logging. I’ve used tracing before, and it doesn’t add too much boilerplate code or cognitive overhead. I might as well start using it early instead of using a bunch of print statements and then switching them over later.
There aren’t really any impediments in my way. It looks my other courses will be slightly heavier next week, and I need to get some solid job search time in, but I expect to comfortably be able to give this project sufficient attention.
I don’t think I had much of a conscious process last week. I pretty much had to just write and think until I was done. Since this week marks the beginning of hands-on coding, my process will look quite different anyway. If there’s anything to reflect on, I’d say I could be a bit more methodical about planning out the amount of time I expect a task to take beforehand.