This was a tweet I read about a few weeks ago. It really got me thinking. Not sure what a "cracked dev" means exactly but I'm guessing it's got something do with competence. It's really true as well especially when it comes to programming. Thankfully for us developers the constraints made for more performant programs and programmers in the past, so when the constraints have been lifted so have the celing of possibility. Which also made me realize that I haven't brushed up on the fundamentals or maybe never got good of them to begin with. So I've been cooking. Luckily the fundamentals are widely known. All there is to do is go over them, more importantly see how they could work in the real world. Admittedly at my time in College the second part I totally neglected. Which is highly weighted part of the whole equation. Also helps with comprehension.
The strategy is quite simple, do some Leetcode, yes a lot of people think it's unnecessary so did I. Yet I think it has value. At the very least I can practice some of my algorithms. As for the algorithms themselves, I find it easier to grok if someone explains it to me. Luckily one Mr Primeagen has a brilliant course on it. As has been the case I'm also using it as an opportunity to practice more Zig. Just today I came across the concept of dangling pointers. It's a term I've heard before but for the first time I got to experience it myself. Once while working on my compiler yesterday and then a second time while doing some tree traversal today. It's both frustrating and exhilarating at the same time.
Heres to being competent.