Omarchy, a set of pre configured arch Linux tools from DHH and company. Tried it on my old MBP 2015, the machine felt brand new almost as snappy as my MBP M4 so I went and bought a ThinkPad the next day and started daily driving arch
Graphics programming, I have done some basic stuff but moving into 3d and actually make stuff that looks good and using like vulkan is a goal that I never get around to.
Also writing my own dbms, but this one I have at least seriously started reading up on and play around with.
For graphics, I was eager to play with rust and the pixels crate was recommended to me - which has been great! It abstracts away a lot but doesn’t get in the way when you want to dive in deeper. But it’s also all in Rust, so that’s one caveat.
> Each commit of this project corresponds to a section of the book. For this purpose, not only the final state of the project but each commit was carefully written with readability in mind. Readers should be able to learn how a C language feature can be implemented just by reading one or a few commits of this project.
I mean Beff or the dude behind Beff has said that he does not see himself as the leader in that sense, in fact he encourages forks from what he says. All this to say that your characterization is unnecessarily negative.
Ever since I read this: https://cognitiveresearchjournal.springeropen.com/articles/1... in uni, i have followed the techniques mentioned to super great success. So much so that people are frequently surprised how I can know/do so much at work for someone so young.
There some title inflation going on I think most people can see / feel that. But having said that I dont think it is unreasonable to be promoted to senior after 2-4 years at all, it all depends on the skills you have show and what level responsibility and impact you have had. Especially with a degree, you have then spent almost 8 years getting educated and working in the same field so with that in mind its even less of weird thing.
Is there some more examples or blog posts that talk about this? I find the idea interesting and possibly very applicable in my work but just from this post alone I don’t feel like I have grasped it well enough to implement this.
apologies for not getting into more detail--wanted to start by covering things at a high level.
There are a few key concepts that might be helpful.
* data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/
* logical state - this is everything you use in processing the data in your pipeline (i.e. code, config, info for connecting external services, etc.). This can all reside in git
We found the key was associating our logical state (git branch) with our logical state (lakefs branch). We make this association during our branch deployment process.
Let me know if this helps at all. I was planning to write a follow up post about what we learned about managing the logical state of a data pipeline. If you have suggestions for a different topic to dive into, I'd love to hear about it.
I use tmux/neovim so I basically live in the terminal 100% of the time when working and when playing around with sideprojects. And I find alacritty to be super easy to use and more responsive compared to iterm2 :)
For math I think this book has a great collection of theorems and ideas: All the Math You Missed: (But Need to Know for Graduate School). Although You probably need a certain level of mathematical maturity (A concept which the author of the book is quite passionate about) to really get the most out of it.
