Hi everyone, Day 4 of this series of daily updates. I don’t have a lot to share today, just one of those days where I spent a lot of time going through whatever I’ve done already. I take some time to look at the things I learned so far, and see if I could be more intuitive back then. I’m going to continue doing the same for the next day, though this time for the problems I’ve solved on Leetcode. ...
Hi everyone, Day 3 of this series of daily updates. Woke up fairly early (~6 AM), and started working. Though it seemed productive to me, but you won’t see a lot of content here today - just one of those days where I didn’t do a lot of different things, I guess. :) Projects/Learning: I made my rust-leetcode repository public today. It currently contains 12 solved problems, you’ll see huge difference between the first few codes to the last few codes. I’ve been learning, please don’t refer it for learning. I’m just documenting it there. Autogenerate README once a new file is added to my Rust Leetcode repository: I first started with writing a Python script to auto-generate the README.md file, from the modules registered in the src/lib.rs. The script is here. Since I wanted to explore how it can be done in Rust, I ported it to Rust as well. The script is here. Took some break from doing leetcode today, had a lot of work which I unfortunately can’t mention here. ...
Hi everyone, Day 2 of this series of daily updates. Started my day earlier than yesterday, at around 9 AM (work). Learning: Watched this nice video from Jason on The Right Way to Write C++ in 2022: I like when he advocated on using different compilers, or at least verifying that it works for all (and if not, then you’re aware). Interest: take warnings seriously. Need to start doing it, I’ve been following this with Rust, but C++ never raised Rust-like “good enough” warnings. Might as well start doing it now. Code coverage analysis: hmm, it used to stay at around 87 to 90% for the libraries I worked with. I agree, most of it should be tested, but as the library grows longer, you can’t block PRs on coverage (specially by the community). But it’s underrated, I’ve seen developers ignore it until they face the wrath of weird bugs. 100% testing coverage, will always be difficult, but if the goal is kept in that direction, it might reach to 95-100%. Never heard of fuzz testing before…after reading about it, just another word of what we have done before. Never got a name to it though. ;) Ship with Hardening Enabled: Again, no idea about this. I’ll have to read about it. Marked as a TODO. Missed watching Edward’s stream on TorchDynamo, I woke up late. :/ Going to re-watch the stream now. I’ll share the notes in a separate blog once I’m done, I could only watch some of it today. I’ve started learning Kernel Fusion, how does it work and why it can help (and when it can not). This is going to be a long road, hopefully I’ll be able to share something concrete soon. Leetcode Problems: ...
Hi everyone, I’m back to - writing daily update blogs. Just sharing what I did today, and documenting my progress. Now of course it won’t contain everything I do, but yep - everything related to learning and things I’m passionate about. Reading Just In Time Compilation (Wiki): Wiki: https://en.wikipedia.org/wiki/Just-in-time_compilation Honestly, I wanted to start with a few papers on it, but Wikipedia does give enough background and sets some context. Leetcode problems ...