A tale of contributing to
pytest and becoming a member of the pytest-dev organization.
I like to build and break things. Currently, Site Reliability Engineer at Talkdesk, formerly at Claranet. These days I write Python and Go, while looking for ways to optimize and automate infrastructure, at the same time.
You can get future updates via RSS.
A tale of contributing to
PostgreSQL 11 (Beta) is out with some very interesting features worth taking a look at. PostgreSQL is already my go-to relational database and - no science to support that - is the easiest, most performant relational database management system.
Sometimes you run scripts that take a lot of time to finish, through SSH. Also, the server, sometimes, closes your connection. This is bound to create issues. I have recently faced similar issues and went searching for a possible solution.
SSL is a mess, sometimes. It is increasingly important, yet it is also hellishly difficult to debug and, if not perfectly understood, it seems that it can also be a pain to implement correctly. With the rise of automated tooling to help with implementation and management of SSL (certificate-wise and more), we have seen an increase of encryption usage in our HTTP connections (, ).
Recently, I have had to reinstall my OS (Ubuntu) several times due to a mix of filesystem and HDD corruption issues. This, invariably, has led me to a situation where Asus K450J’s wireless networking doesn’t work.
Tim Berners-Lee wrote an open letter about the perils of the internet, as it currently stands, and how it is getting increasingly centralized, on the hands of a few selected companies.
An excellent article, Google’s nemesis: meet the British couple who took on a giant, won… and cost it £2.1 billion, written by Rowland Manthorpe, in Wired: For the Raffs, this remains the burning issue, which the technicalities of auctions and algorithms all too often obscure. They see it simply: Google, or any other search engine, should present only impartial results that do not benefit it financially. It sounds idealistic, but why should it?
This week I read an incredible article about maintainers.This article is mostly focused towards infrastructure maintenance. It completely adapts itself to the current reality of software development. The reality is that maintenance is not as shiny as innovation. But maintainers are, mostly, what keeps society, and code, working. If it weren’t for the software maintainers most of our software would already be broken, by now. This excerpt, from the article, beautifully, explains what I feel about this:
This week I was working on HackerRank’s Arithmetic Operations. Turns out, to my surprise, that Bash does not support floating point operations. I had no idea. Off I went, in my searching. I searched through a lot of StackOverflow answers. The best one I found is this one - a summary of possible solutions. This answer is objective and straight to the point, offering enlightenment into a lot of possible solutions to go around this problem.
tl;dr I automated the deployment of this website with Travis CI, Github, Hugo and Github Pages. The website gets build from each push to master and, if the build is successful, deployed to Github Pages for website hosting. Introduction A few months ago I wrote an article describing how interesting it can be to automate the deploy workflows - Automate Simple Deploy Workflows - Cool!. The easeness of deploying automatically was appealing but it still required some manual work.