Eduardo Zepeda's latests posts

Beginning Python: From Novice To Professional was one of the first Python books I read. I chose this book because with it you could learn Python from scratch. The book starts from the installation of the language, going through the different types of data structures that Python includes and even two chapters on abstraction.

When you get to the end of the introduction, the following chapters of this book touch on a different topic about Python each, some of the topics covered are as follows:

The other day a person asked me why I use Wordpress for my blog if I could develop a website by myself. In the post where I explain how I learned to program I even talked briefly about my lousy experience with PHP. So why did I choose Wordpress instead of developing my own blog from scratch? The answer to that is simply that, for this blog, I want to write text, not code. I don’t want this blog to become a project to develop along with creating posts. I want something that works with a couple of clicks and forget about it completely. Let’s not lose sight of the fact that the purpose of a personal blog is to write on it constantly, not to program it constantly. It’s sad to see so many developer blogs using the newest technologies and super up-to-date, but with very few entries.

Previously I briefly discussed unittest, coverage, mock, nose, nose, pytest and other testing tools in Python . You are probably wondering then why do we need more libraries? In this post we are going to talk a bit about tox, a testing tool for testing code in different versions of Python.

What is Tox for?

Imagine you are writing a small application for the general public. All your code tests pass, the application works perfectly.

Long ago, when I started programming I thought that testing code was a waste of time. Why did I need to write more code? python unittest? mock? I could just read the code, see the places where the code might fail and handle the problem with a try and an except (or the equivalent in another language). I also thought that, aside from syntax errors, no errors would be generated in the flow of the code if one wrote carefully enough. The first programming book I read had a section devoted entirely to testing and I didn’t understand what all the fuss was about. why should I incorporate tests into my Python code? It wasn’t long before I realized how wrong I was. unittest python

The other day, one of the youtubers I follow recommended a page to receive algorithms by email How would you like to receive one algorithm problem a day in your email? That’s 7 problems per week and 365 problems per year. Imagine how much it would improve your problem solving and analytical skills. Still not enough? What if I told you that these code puzzles are frequently asked questions in job interviews at top world-class technology companies?

The previous entry was the third part of the series on the most common GNU/Linux commands. To end the entry I wrote about the chmod command, which manages permissions . This chmod command is one of the most complex commands in GNU/Linux, not because of its variety of options, but because of the previous knowledge required to be able to use it correctly, and its weird syntax (RWX) or even worse (777, 755, and so on)

This is the continuation of the following parts:

• GNU Linux Basic Commands, part one
• GNU Linux basic commands, part two .

printenv

Printenv is in charge of printing the environment variables of our system.

What is an environment variable?

Environment variables are a series of equalities known as environment variables, and their corresponding values. Environment variables describe the environment in which a program runs and influence how our operating system behaves. These variables are available to be read by any application on our system, so we can use them to store information such as user names, configuration values, paths to files, etc.