This reminds me of the time I worked with some folks that had swallowed some enterprise Python book whole, and proceeded to implement a service bus with dependency injection and message queues backed by Postgres… on an embedded device with 1 gig of NAND and 512 meg of RAM.
In general, I think you should be wary of taking any single book (or “thought leader”) too seriously. My favorite books don’t take themselves too seriously; I recommend that everyone read at least the footnotes and appendices of Programming Perl, even if you have no intention of ever programming in Perl.
The bracelet stuff seems real weird to me, but I guess if it helps you to focus on something? I just don’t know if I view programming as actually having any hard-and-fast “principles” to adhere to, aside from, ya know, acting ethically in general. I don’t think I would go so far as to ascribe moral implications to any particular implementation, even if I thought an implementation was really bad. Everything is contextual, depending on the constraints of your environment and the tools, skills, and amount of time you have. If I punished myself every time I had an off day or produced something I wasn’t 100% in love with, I wouldn’t have time for anything but punishment. It doesn’t sound like a happy way to live.
I’d like a rebuttal to this post that does not focus on style or the unfortunate reference in the title. I’ve never read Clean Code, but the cited section about function arguments was painfully wrong for exactly the reason the author notes.
I mean, since a lot of people here were complaining about this article, but without much meat. This just seems to agree with the criticism in the article.
This post is a rambling mess and I recommend you just stay away from it.
I didn’t listen to you and I’m sorry I didn’t.
A good reminder: the enemy of your enemy is not your friend.
This reminds me of the time I worked with some folks that had swallowed some enterprise Python book whole, and proceeded to implement a service bus with dependency injection and message queues backed by Postgres… on an embedded device with 1 gig of NAND and 512 meg of RAM.
In general, I think you should be wary of taking any single book (or “thought leader”) too seriously. My favorite books don’t take themselves too seriously; I recommend that everyone read at least the footnotes and appendices of Programming Perl, even if you have no intention of ever programming in Perl.
The bracelet stuff seems real weird to me, but I guess if it helps you to focus on something? I just don’t know if I view programming as actually having any hard-and-fast “principles” to adhere to, aside from, ya know, acting ethically in general. I don’t think I would go so far as to ascribe moral implications to any particular implementation, even if I thought an implementation was really bad. Everything is contextual, depending on the constraints of your environment and the tools, skills, and amount of time you have. If I punished myself every time I had an off day or produced something I wasn’t 100% in love with, I wouldn’t have time for anything but punishment. It doesn’t sound like a happy way to live.
Casually using KKK as an acronym is problematic.
As well as others’ comments, this is a really distasteful use of equating people to the KKK 😬
I’d like a rebuttal to this post that does not focus on style or the unfortunate reference in the title. I’ve never read Clean Code, but the cited section about function arguments was painfully wrong for exactly the reason the author notes.
Maybe this is what you are looking for?
https://lobste.rs/s/twdhuk/it_s_probably_time_stop_recommending
I mean, since a lot of people here were complaining about this article, but without much meat. This just seems to agree with the criticism in the article.