Geek Logbook

Tech sea log book

Recent Posts

Categories

#50projectsIn50days #DjangoDevToDeployment Airflow Amazon S3 Amazon Web Services AWS bash bastion host Batch code Coders At Work Computer Science Data Databases Databricks Data Intensive Applications data lakes Dijkstra Edsger W. Dijkstra faker Google Colab Hellerstein Jinja Knowledge Transfer Leadership Models of Computer Programming Networking Networks Protocols Python Redash Seweetviz Social Skills SODA Software Developer Spark: The Definitive Guide SQL SSH Testing The humble programmer Traversy Media Ubuntu Understanding Distributed Systems Virtual Box Web Development whale-alert

Archives

Category: Notes

Notes taking about the different books I’ve read since the blog started. Usually related to specific technology but, sometimes I read about tech history.

4.6 Data Warehouses

DataWarehouses—large historical databases for decision-support that are loaded with new data on a periodic basis — have evolved to require specialized query processing support, and in the next section we survey some of the key features that they tend to require. This topic is relevant for two main reasons: 1. Data warehouses are a very
Read More

Management Skills for developers

Leadership and direction Vision The business vision (“vision speaks of the future”) should be: To communicate the vision: Decision-making Understand what is at stake. And prioritize it. Delegate the rest to the rest of your team. There are three elements when making a decision in dealing with customer-related crises in systems: While you are making
Read More

Learn to speak in public

First steps to public speaking When giving a presentation or starting to speak, it is sometimes common to inform the audience about things they are unaware of, which may cause stress. For example, saying, “Oops, I arrived late. I’m very sorry” or “I missed a few slides, but let’s proceed anyway.” This is your personal
Read More

A short introduction to the art of programming 

Edsger W. Dijkstra – A short introduction to the art of programming  Link: E.W.Dijkstra Archive: A Short Introduction to the Art of Programming (EWD 316) 1. Preface  For those readers who identify the programmer’s competence with a thorough knowledge of the idiosyncrasies of one or more of the baroque tools into which modern programming languages
Read More

The element of programming style

When the book saw the lights, programming wasn’t as important as today. But, some of the ideas around the style of writing are a worth to notice and to know it. For that reason reading the book written by Brian Kernighan and P. J. Plauger are a constant invitation to revisit the way we code,
Read More

The elements of programming style: Epilogue

Epilogue There are many good books on languages, algorithms and numerical methods available to those who want to learn programming in greater depth. Our goal was not to teach languages or algorithms, but to teach you to program well.  Programmers have a strong tendency to underrate the importance of good style. Eternally optimistic, we all
Read More

The elements of programming style: Documentation

Chapter 8: Documentation The best documentation for a computer program is a clean structure. It also helps if the code is well formatted, with good mnemonic identifiers and labels (if any are needed), and a smattering of enlightening comments. Flowcharts and program descriptions are of secondary importance; the only reliable documentation of a computer program
Read More

The elements of programming style: Efficiency and instrumentation

Chapter 7: Efficiency and instrumentation Machines have become increasingly cheap compared to people; any discussion of computer efficiency that fails to take this into account is shortsighted. “Efficiency” involves the reduction of overall cost – not just machine time over the life of the program, but also time spent by the programmer and by the
Read More

The elements of programming style: Common Blunders

Chapter 6: Common Blunders A major concern of programming is making sure that a program can defend against bad data. But even with correct data, there is no guarantee that a program will work. In this chapter we will discuss other aspects of making software reliable. Let us summarize the main lessons of this chapter.
Read More

The elements of programming style: Input and output

Chapter 5: Input and output Input/output is the interface between a program and its environment. Two rules govern all I/O programming: NEVER TRUST ANY DATA, and REMEMBER THE USER. This requires that a program be as foolproof as is reasonably possible, so that it behaves intelligently even when used incorrectly, and that it be easy
Read More