I always looked at software as a flow of data: Data comes in, it is transformed and it gets out -- sometimes, the transformation part is just a collection of a sequence of transformations.
This is a whole book about looking at the data instead of the code. And it's free.
Yet another silver lining in this quarantine: The reduction of polution it causing people with asthma to have less attacks, reduced the deaths of respiratory problems and so on.
I'm not saying "Hooray for COVID!", but governments need to take a look at this kind of reduction and start working on ways to keep it more permanent.
A few years ago, I got the opportunity to become a technical leader in two different teams and I really enjoyed. Since then, I've been reading everything I can about leadership, management and such. But I've never seen a such succinct and direct list like this.
While I don't agree with a lot of points here, I think it is worth sharing it.
In general, while the business rules you learn in one job do not automatically transfer to another -- for example, the way a pharmaceutical company works, and its business rules, do no translate directly to an auto shop -- some aspects do transfer: Both of those have to manage their resources, specially money; both of these have to deal with customers and give them a good experience. Again, those do not translate directly, but knowing what they tried and didn't work, no matter what it was, is always good knowledge.
But some are really gold: "Estimates serve more for creating pressure than for project planning" is actually a hell of a truth.
After pointing most of the problems with Windows are memory safety issues (one thing Rust aims for) and after working on its own version of the borrow checker with Project Verona, now Microsoft released a version of the Windows Runtime Libraries aimed for Rust developers.
It seems Microsoft is getting really in love with Rust.
... and that's not only it.
Microsoft is checking the use of Rust and WebAssembly to make Kubernets "kublets" -- the worker parts of a Kubernets cluster.
The interesting part is "For the first week or so, we lost much of our time to learning how borrows worked. After about two weeks, we were back up to 50% efficiency compared to us writing in Go. After a month, we all were comfortable enough that we were back up to full efficiency (in terms of how much code we could write)," writes Thomas.
This is not related to the speed of the resulting app, but the speed of development. And the learning curve of Rust is well known, but the curve is not permanent, with the final results pointing that you have better security in the end.
And I'm left wondering how long till Microsoft starts sponsoring Rust development, as AWS did in the end of last year.
The configuration I was always looking for Tmux: Using alt to switch between contexts, no leading key.
Maybe I still need to mess a bit with my terminal emulator, but that's basically it.
Where do you want to keep your files? Do you have lots of money? What kind of data you want to keep?
Awk. The first time I saw Awk, I though it was simple a text processing of
sed on steroids. But there is a lot more about than just that. And
here is a short intro about the language itself.
This post was built with the help of