Geek Logbook

Tech sea log book

The elements of programming style: Control Structure

Chapter 3: Control Structure A computer program is shaped by its data representation and the statements that determine its flow of control. These define the structure of a program. There is no sharp distinction between expression and organization.  The control structures of a language provide the framework of a program. These include decision-making with IF

The elements of programming style: Expressions

Chapter 2: Expressions Writing a computer program eventually boils down to wanting a sequence of statements in the language at hand. How each of those statements is expressed determines in large measure the intelligibility of the whole; no amount of commenting, formatting, or supplementary documentation can entirely replace well expressed statements. After all, they determine

The elements of programming style: Don’t Be Too clever

Preface to the Second Edition The practice of computer programming has changed since The Elements of Programming Style first appeared. Programming style has become a legitimate topic of discussion. After years of producing “write-only code,” students, teachers, and computing professionals now recognize the importance of readable programs. There has also been a widespread acceptance of

Refactor or rewrite?

While I was reading The elements of programming style found the following quote: Don’t patch bad code – rewrite it The element of programming style – Chapter 4 – Page 1 Its make me think about an informal comments that different professionals have been made during these years: “Don’t touch code that it’s working”. But,

Dijkstra: The Humble programmer

Dijistra wrote some interesting things about the activity of programmer. In this opportunity I’m going to make some quotations and notes about the article: The humble programmer Rules “discovered” for the creation of software A number of rules have been discovered, violation of which will either seriously impair or totally destroy the intellectual manageability of

Coders at Work

Coders at work is a series of interviews made by Peter Seibel in 2009 where different programmers talk about their views about the technology, development, how they work as a programmer and the environment where people in tech works. The general overview of this book is really good because if you read it, you’ll learn

Django Jinja Isn’t a thing

I was reading about Jinja and an article on Wikipedia caught my attention: Jinja (template engine) At the beginning I read: Jinja is similar to the Django So, Django Jinja and Jinja projects are different? I don’t think so because, in the same article, the sources point to the Jinja2 documentation. And this also happens in the Django article

50projectsIn50days – Day 2: Progress Steps

The projects related to the progress step it is generated by an another script in JavaScript that change the class in the DOM. There are two event listeners in the script and there is a function that update the CSS. So, the new style is following: The project has a an average difficulty and it’s

While you learn while you build it?

The quotation and the necessity of understand what you have done is really important when you try to understand some concepts. For that reason when I found this video: I remember the importance of being someone that trying to understand the concept of the “project based courses”. Because If you don’t know what you have