After my tests with DAIN, I decided to go back and test the new set of frameworks that we have available for AI and DataScience. While Tensorflow 2 and PyTorch are the ones everyone mentions lately, I decided to give FastAI a test drive, and it’s incredibly easy to use.
I just finished reading SQL Performance Explained, by Markus Winand. This book, which is available for free in a web version at Use the Index, Luke!, is absolutely a service to the development community, and from the moment I started reading it, I could not put it down.
Chicken soup for the rational progress
I’m halfway through reading Algorithms to live by, by Brian Christian and Tom Griffiths. The book is really good – but this is not a review about the book. Rather, a thought that came to my mind while reading it.
I think that books (and other pieces of knowledge) like these are what are going to fulfill Kurzweil’s predictions on the future of humanity.
Is there such a thing? I believe there is.
I recently read this wonderful article from Vox called The biggest lie tech people tell themselves — and the rest of us. In it, they propose that the progress we’re making in technology, with the debates in ethics and in the erosion of privacy is usually justified by people with mantras like “it’s the natural evolution of technology” and “it’s the way progress works” and “it was going to happen eventually”. They propose that these are invalid excuses.
Play with the most powerful text generator so far
There has been a lot of controversy around OpenAI not releasing the full model for GPT-2. However, leaving that aside, they did publish the 117M model version, which is a small subset of the model that still works. And it works really nicely.
So let’s dive and see how we can run it for ourselves.
Why we need multiple skills in the search for AGI
About a month ago OpenAI published a post where they open their gates for social scientists into their organization. I think this is part of a profound matter that has not been completely discussed in that blog post. Aside from a short version of some points of it, I’ll also provide what is this subject that hasn’t been discussed yet.
How to configure HTTPS while keeping control of the nameservers
As a final step to moving my blog to GitHub pages, it was the matter of setting up HTTPS. The GitHub guides are very detailed on this. So much that it’s easy to get lost in them.
My case was particular, as it was a combination of a lot of conditions:
- My repository is a project repository (it is not a repository named after my user or my organization).
- I don’t want to transfer the whole domain DNS (apex domain) to GitHub nameservers, since I might want to use other subdomains (or the main domain) for my own purposes.
- I want the blog to have HTTPS enabled, even when only static content is served.
I couldn’t find anywhere how to setup the configuration for a case like this, but it’s really easy.