A Review of My 2019 Readings

The end of the year is a good time for assessments. A good one is, “what have I learned this year?” IT is a field that keeps moving, and we need to stay up to date if we don’t want to drown. In our culture, most of our knowledge is stored and shared through writing, so a part of my question becomes, “what have I read that was enlightening this year?”

What I Read in 2019 #

Books #

Books are the first thing that comes to mind when we make this kind of review, and I indeed read some IT-related ones this year, though the majority was not that technical.

I’ll provide you with a link to each book if you’re interested, but this article is not sponsored.

97 Things Every Software Architect Should Know #

Cover of the book “97 Things Every Software Architect Should Know”

2018 was hard on me, professionally speaking. I worked on a project with high stakes, a lot of pressure and it was the first time I was really getting into my “technical architect” shoes. I’m ok with all the technical parts—I mean, that’s what I’ve always loved—but I wasn’t so sure I did all that was expected from me on the management side.

In the end, everything appeared to be fine, but when I discovered this book, I was curious to broaden my perspective about my role. This book was indeed written as a collection of short articles—up to 5 pages, I guess—written by actual software architects. Each article gives a specific bit of advice and explains it.

I’d recommend this book for anyone in the “architect” role or thinking of following this path. It’s not purely technical, far from it. Actually, several entries remind us that an architect can’t take a purely technical approach, lest their solution is unfit or too expensive to realize within budget/time limits. Others highlight that we should be able to keep a bird’s-eye view, give you advice about how to behave with your team—an architect is a leader and a manager in my world… Much of it is common sense, but like most common sense, seeing it explained helps us realize it is a good thing and why it is.

Click here for more information and buying options1.

Sobriété numérique : les clés pour agir #

Cover of the book “Sobriété numérique : les clés pour agir”

I didn’t find an English version of this book. It was published last September in France. Its title could translate to Digital Sobriety: the Keys to Action.

People seem interested in saving the planet more than ever. Yet, many of us, especially the younger generations, can’t live a day without a smartphone. We can’t realize that those 120 g are built from 70 kg of raw material, which required a polluting extraction and transformation. Same thing goes for all the displays, screens, televisions that go ever bigger.

This book is addressed to anybody, not only people working in the IT field. It’s divided into two parts:

  • The first part is a lexicon of terms related to the field of ecological design and thoughts. Each word or phrase is clearly explained and often illustrated with an example. It may seem repetitive on some aspects, or a bit lengthy, but it’s still interesting.
  • The second part of the book is much shorter and more to the point. It gives ways to act, reduce our digital footprint. It includes giving advice and highlighting false good ideas2. It’s a real call to action for those who wish to help the planet.

Click here for more information and buying options.

Écoconception web : les 115 bonnes pratiques #

Cover of the book “Écoconception web : les 115 bonnes pratiques”

I didn’t find an English version of this book either. This is the 3rd edition and was published last May. Its title could translate to The 115 best practices for web ecological design.

The stakes should be a bit clearer with the presentation of Sobriété numérique just above. Both books are indeed from the same author and the topics are related. We know digital has an environmental impact, which indirectly means IT and software have a footprint too—I’ll write more about this subject very soon.

This book focuses on the web development and suggests best practices to reduce the footprint of the website you’ll develop. Those are presented as flashcards, with the practice, an explanation and example, and evaluations of the difficulty and impact of adopting this practice (on the CPU, memory, network load and so on).

Click here for more information and buying options. If you just wish to have a look at the best practices without the explanations, they are publicly available here (in English too, this time).

Please note that, due to the “flashcard” format of this book, it’s not really comfortable to read as an epub. I’d rather recommend the PDF or paper editions.

White papers, Articles & Studies #

Still, books are not everything. Knowledge filters through all cracks, and some studies and white papers are waiting freely to give you more insight on many unsuspected topics. I’ve read some interesting ones, but I’ll keep only the one available in English on this page. If you also wish to see the French ones, please refer to the French version of this page.

Environmental Footprint of the Digital World #

This study gives a great summary of the impacts of the digital world, in all its forms: computers, smartphones, displays, IoT and data centers. It includes an analysis of the footprint of the fabrication, use and end of life of all these products, and gives a wide overview. It also includes an analysis of the evolution over the last decade and a prevision of what the next one may look like.

For instance, it estimates that we are 4.1 billion people using 34 billion devices, meaning each user has in average 8 digital devices. It also tells us that, though they did not exist ten years ago, connected devices may amount to 19 billion now.

Of course, studies on that scale cannot be taken as gospel truth: the magnitude of data to find and crunch makes it hard to be exact, and numbers differ from what you may find on other sources. Still, I think it should be taken into account.

You can read the full study here.

Blogs #

I can’t find my source again but a recent survey highlighted that the first support for sharing and gaining knowledge for developers is still blogs like this one really—which is why having blogspot blocked by your company policy is always frustrating. Starting my blog from scratch, I also refreshed my blog list a bit. This is still a work in progress and I’ll share it later.

Things I Hope to Read in 2020 #

Never settle for what you already know, there’s always more to discover. Below are some things I hope to find the time to read next year—this goes between my videogames-to-finish and non-technical-to-read lists.

  • The Robert C. Martin Series. Well, maybe not the whole series at once, but I’m especially interested in Clean Code, Clean Architecture and The Software Craftsman to begin with. Reading at least two of those in 2020 would be a great start.

  • High Performance Java Persistence by Vlad Mihalcea should be a goldmine if it’s what his blog promises it to be. I’ve had a few years without using JPA because my clients preferred explicit SQL, but now Spring Data JPA is everywhere and developers don’t always know how to use it properly or efficiently. I wish to reinforce my knowledge of its subtleties so that I use its features the correct way and can help my teammates doing so.

  • Numérique et impact social (Digital and Social Impact) is a white paper that is published in separate modules, once a month. The title is self-explanatory, and the chapters already available include Employer-Employee Relationship, Quality of Life at Work, Health and Security at Work

These are just some ideas and I hope to read a bit more than that next year.

To Conclude (This Post and Year) #

2019 is coming to an end. I’ve rebooted this blog, and though it’s rather calm now, I love sharing. I hope some of these thoughts and advice will help someone.

In any case, I wish you a very happy new year!


  1. If you work in IT, you should check with your company. I know several of them have free access to at least some O’Reilly books. ↩︎

  2. Most of the false good ideas highlighted here are not bad ideas, but they’re solutions that don’t yield as much result as you’d hope. ↩︎