You have an application. You add threads to improve throughput. But how many threads do you add? Do you go for a fixed number, or you compute this dynamically?
We try to articulate an answer in this post.
thoughts on Computing and Truthing
You have an application. You add threads to improve throughput. But how many threads do you add? Do you go for a fixed number, or you compute this dynamically?
We try to articulate an answer in this post.
A new article of mine appeared in Overload: OOP Is not Essential.
Starting from a tweet from Grady Booch, the article claims that OOP is not essential in building (complex) software systems. It covers multiple meanings of the word “essential”, and it also covers the features of OOP and shows that there is nothing essential in there. The true weapon of fighting complexity is decomposition, but OOP isn’t the only alternative there.
Long time, no post. Partially I was busy with other projects, but for a brief time, I was busy writing an article for ACCU. And, as you might have guessed, the article was called “Do Repeat Yourself”.
My previous posts on tasks and concurrency (Threads are not the answer, Look ma, no locks and Modern dining philosophers) ) all talk about tasks. But after all these posts, I’ve got the same question back what is the difference between a task and a thread?, in various forms.
This blog post is aiming at making some light on this difference.
I’ve recently re-read Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin et al. And, once again, I have mixed feelings about the book.
This post is discussing some weak points of the book.