Talk to the manager Karen! Do it!
A software engineer that loves Disroot and the team behind it.
Talk to the manager Karen! Do it!
One person downvoted? Are they stupid or something? Asking for a friend.
Obviously, that’s what the “arms race” refers to. Birds used to have very strong arms which they used while racing in their super-fast arm bikes.
If you enjoyed it, I’ve collected a couple of others:
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…
That’s what she said!