

I think comment ratio could be a fairly misleading metric. There are programs out there that requires a lot of context upfront that distills down to just a few lines of code, and especially those that are more academically interesting.


I think comment ratio could be a fairly misleading metric. There are programs out there that requires a lot of context upfront that distills down to just a few lines of code, and especially those that are more academically interesting.


Yo, you just reaffirmed my idea that I thought was too wild! I have to replace this old phone of mine soon cause the battery’s dying, but I guess this thing will have to stay up for a bit, or much, longer.


Please don’t remind me. Had a colleague with a senior title who just vibecoded on our CI pipeline and it ended up blocking deployments for half a day.


AFAIK, the author isn’t anti-proprietary. His goal with the newsletter is to share news that relates to self-hosting, which isn’t limited to FOSS, which is something he mentioned in one of his recent newsletters (it’s a common criticism he gets apparently). And there’s the reality where the vast majority of the source for selfhosted software are hosted on Github.


Back in university, it was an iPad mini 5, using Notability. Notability has enshittified badly though.
These days (I’m no longer in university so I do write a lot less), I write on a Kobo.


It does. I vastly prefer writing notes by hand than typing em. But my handwriting sucks when I have to write quickly, and I also don’t like lugging around giant stacks of paper. And so I settled on a digital writing pad, and just do the work to type my notes later. Acts as revision too.
One thing that sort of helps me know when I should quit a job is by looking at my employment as a business relationship between me and the employer. I have my aspirations and goals, and if the employment doesn’t work in my favour anymore, then it might be time for me to go. Things that can be “not in my favour” can be things like:
Thanks and praises are good, but those are free and are expected of a cordial relationship anyways. You don’t charge your friends for saying thank you after all.
Essentially, just like all relationships, if it doesn’t work out for us, then we should consider leaving that relationship, lest it eats at us. You can always argue with yourself on whether you should stay: maybe it’s just worse out there, maybe they haven’t crossed your bottom line, etc. We can’t use every logic in other relationships, but there’s a certain pattern to them.


That’s not always bad though, but you definitely need a strong leverage. And a strong leverage is not something the US really has these days. In fact, they’re working really hard to get rid of their leverages. That’s some smart politics there. /s
So this rando just came here and just said something like “I’m gonna make it harder for people in your neighbourhood to do business with mine if you don’t stop the fighting.” Like, sure bro. Like that’s gonna work.
Sure, Thailand exports 19% of its products to the US, might hurt em a lil, but I don’t think that’d stop them from fighting Cambodia if they’re serious about it, and they were. Cambodia does export 42% of its stuff to the US, so it’d hurt em, but if Thailand isn’t gonna be bothered, it’s not like they have a choice.
So much for the self-proclaimed master negotiator.


There’s no good reason today and in the future, period.
There are “experts” who still claim these, but they are based on a very dated recommendation from at least 15 - 20 years ago at this point. To some, such non-sensical requirements (by the fact that we should be storing passwords as hashes today) have become doctrine, rather than any fact based in reality.
And some users have been conditioned into thinking that these are good security practices as well, because governments and banks still make use of them, and these are the very organizations that should be the best-in-class when it comes to security. Some of these users become CEOs or product designers with more say than their IT and security experts in the company. The rest is history from there.


Just to add to the list or clarify further


You’re gonna need more conditions than that cause you could just slap any a = b = c ∈ ℝ, drop a 0, and call it a day.
I don’t claim it to be common practice, just saying that it exists. That said, it may be “niche” in the grand scheme of things, but by no means do I think it’s small and insignificant. If anything, such codebases are typically foundational libraries in the giant stack of cards most other software engineers build.
See also antirez’s article about code comments https://www.antirez.com/news/124 You’ll notice how some of the snippets would’ve easily failed your criteria.