Reminds me this great story from a different era:
A software engineer that loves Disroot and the team behind it.
Reminds me this great story from a different era:
On a serious note, I really enjoy yerba mate-based (or should I write flavoured) elixirs. Or even yerba mate itself. Just saying! 🤷
That’s like… Your opinion, sis…
Do you eat them too? Asking for a friend!
Could someone explain how they’re going to drive 407 km/h in traffic jam? Or in a city, in general?
I definitely agree that too many comments is often a bad sign, esp. when large part of them is obviously generated.
As mentioned in my other comment, names will rarely explain the reasons why a given solution was chosen. These reasons are important from maintenance perspective and should be recorded next to the relevant code.
You’re definitely not the only one.
In my opinion the important information we should record in comments is WHY, because the code can only explain HOW, maybe WHEN, but never WHY. If we don’t know WHY, any refactoring done in the future could break the logic by ignoring assumptions made by the authors.
What’s the font used in the heading? Is it some flavour of Helvetica?
I keep telling myself that in the ideal world, phones would be programmed in Forth.
That comment… Oh my, I want to joke and talk someone like you! Now!
I tried searching for research on it, but only found results claiming this didn’t work… Not actual scientific research, but better than “we think this should work, so now we’ll try selling it”
What is he holding? An ancient dildo or a shit stick?
And “Y” stands for “Your Mom”. But it was a one night stand…
I suspect it’s related to USA current affairs and have no clue what it’s referring to. Any hints for us outsiders?
I’m beginning to feel we’re no longer talking about Clean Code being bad, but about people following ideas they don’t understand, which is not related or caused to any particular book.
I hope your book won’t have a table of context and those stupid indexes. If they read it, they should know where you mention topics, right? Tables of contents considered harmful! /s
I’d love to learn what that damage was. I often see complaints (sometimes also involving tech choices) but usually they’re not specific, so I’m always left wondering.
First you confirm they have to spend a lot of time to set everything up, then you claim it’s just pressing a button? 🤨
Taking a picture with your phone maybe looks like that, when you don’t care, but knowing one’s gear and using it properly is already many levels above just pressing a button. Then only a few questions and one presses the button. Questions like: what will be blurred? what will stand out? how the picture will be composed? will colours play? or textures? are there relations between objects in the picture?
What in trying to say is: I don’t agree with you, that it’s just pressing a button. Programming is also just pressing buttons, right? 😉
If you enjoyed it, I’ve collected a couple of others:
https://untalkative.one/reading:2019:good-stories