Category: Technology

I work in technology sector. And I do round a clock, not only from 9 to 5. It is my bread and butter, it is my hobby, it is the fascination of my life. And with the current rate of change particular in information technology (IT), there is always something new to learn, to try, to talk about. I often post news, thoughts, and reviews. And when I do, this is the category I use.

Slimming down Docker images

It’s been a while since I posted anything about Docker.  That’s mostly because I still don’t really use it for anything – playing around locally, testing and learning doesn’t count yet.

But just to keep the ball rolling, here are a couple of handy links for the ideas on how to improve your Docker images, so that Docker uses much less space, benefits more from caching, and brings up the containers faster:

Both articles are around the same theme – choose your  base image carefully, try to minimize the layers, use only what you need, and don’t forget to clean up the disk space with “docker system prune“.

This is why you shouldn’t interrupt a programmer

Yup.  This is exactly why you shouldn’t interrupt a programmer.  It takes him at least a few minutes to get back to where he was, irrelevant how brief and unimportant the interruption was.  And that’s why we invented managers (interrupt them all you want!), asynchronous communication (emails, ticketing systems, etc), and other tools and processes.

Happy 20th birthday, LWN!

Linux Weekly News (aka LWN) is celebrating its 20th birthday.  Wow, that’s quite impressive! Not many web sites can say that.  But even fewer can do so while covering technology news related to Linux and other Open Source Software.

I’ve been a reader of LWN since their early days.  I’ve been subscribed to it also at different times during the years (see 2002, and then 2004).  And I’m glad that they are still around.  I still catch up with the RSS feed on a weekly basis.

Happy birthday, LWN!  And thanks for all the hard work and excellent content.

The most dangerous word in software development

I think this article – The Most Dangerous Word In Software Development – hits the nail on the head.

“Just” implies that all of the thinking behind a feature or system has been done. Even worse, it implies that all of the decisions that will have to be made in the course of development have already been discovered—and that’s never the case.

Every time somebody asks for “just” this little thing or that little thing, I ask them to “just describe it”, or “just answer a few questions”, or “just pay for it”.  Somehow, it never turns up as easy and simple in the opposite direction.