Nothing suggests it would have been free — in fact, if I owned a ford (a shallow crossing point) running through my property, you can bet I would charge for it.
44 karma · joined June 4, 2024
Nothing suggests it would have been free — in fact, if I owned a ford (a shallow crossing point) running through my property, you can bet I would charge for it.
It’s very easy to filter out the weeds: read the classics and any book that breaks through the noise with consistently high reviews. We don’t need to waste time on low-quality literature or AI-generated slop.
https://web.archive.org/web/20250625181250/https://www.terms...
it takes a good 5-10 minutes to boot up
We’re talking about less than a 10% performance gain, for a shitload of data, time, and money investment.
This is not to say that traps don’t make your house more livable. Once, I lived in a house connected to a forest in Brazil—no real neighbors, and a shitload of mosquitoes.
I did buy some fancy traps with UV lights and fans, and oh boy, I killed a shitload of them. Not to say I fully solved the mosquito problem, but I significantly reduced the bites. My wife is allergic to them, so she’s a great sensor—if there’s even one mosquito in the room, she knows.
Looking ahead, Search will become a de facto LLM chatbot, if it isn't already.
You’ve never seen the word before, but when reading it for the first time, you’ll probably pronounce it correctly.
English is awful, but French takes the crown on this one—though more because it has the same pronunciation for many different words and written forms.
English, on the other hand, the alphabet doesn’t map well.
Mood and flood both have “oo”, yet each is pronounced differently. You need to know the word beforehand to know exactly how it’s pronounced.
Granted, it is not only summaries that go into the description—how to test, if there is any pre-deploy or post-deploy setup, any concerns, external documentation, etc.
Less is more. A summary serves to clarify, not to endlessly add useless information.
⸻
2. about the usefulness of summaries.
Summaries always provide better information—straight to the point—than commits (which are historical records). This applies to any type of information.
When you’re reporting a problem by going through historical facts, it can lead to multiple narratives, added complexity, and convoluted information.
Summaries that quickly deliver the key points clearly and focus only on what’s important offer a better way to communicate.
If the listener asks for details, they already have a clear idea of what to expect. A good summary is a good introduction to what you are going to see in the commits messages and in the code changes.
______________________
3.About multiple Prs.
Summary helps to clarify what is scope creep (be it a refactor or unrelated code to the ticket);
it make it easier for the reviewer demand a split in multiple PRs.
examples: A non-summary PR/MR might lead to the question—“WHY is this code here?"
"he touched a class here, was he fixing something that the test missed out ? or is just a refactor?"
_______________
As a reviewer you can get those information by yourself, although summary helps you to get it much quicker.
One thing I do that helps clean things up before I send a PR is writing a summary. You might consider encouraging your peers to do the same.
## What Changed?
Functional Changes:
- New service for importing data
- New async job for dealing with z.
Non-functional Changes: - Refactoring of Class X
- Removal of outdated code
It might not seem like much, but writing this summary forces you to read through all the changes and reflect. You often catch outdated comments, dead functions left after extractions, or other things that can be improved—before asking a colleague to review it.It also makes the reviewer’s life easier, because even before they look at the code, they already know what to expect.
There are two groups:
1. The ones who go after the news (a minority).
2. The ones who don’t even bother reading the article (the vast majority).
From group 1, we have those numbers.
Yes, potentially those 53% could read the news in full in another place and avoid falling for the misinformation.
So, out of the people who read, I know for a fact that 12% — plus some chunk of the 53% — might be able to clarify the misinformation.
The numbers still stack up for the people who fall for misinformation in headlines.
A weird, provocative headline creates misinformation.
Of the people who try to access the article, only 12% actually read it (1% who pay, and 11% who bypass the paywall). Another 53% look for the information elsewhere, which may or may not clarify the misinformation.
And those are only the ppl that tries to read the news, the majority of ppl doesn't even bother trying to open the news link.
"OpenAI has claimed that as of December 2025, ChatGPT has 300 million weekly active users generating 1 billion messages per day. "
**should be December of 2024 **, my brain bugged there.
Nonsense. When AI gets stuck in a suboptimal topology, it’s the human who nudges it out.
How will you maintain code if you’re not even able to read it?
Using AI to read introduces noise with every iteration. Did you see that trend of people asking AI to reproduce someone self over 70 times? The noise adds up—and the original meaning shifts.
AI is non deterministic.
Delegation, properly defined, involves transferring not just the task but the judgment and ownership of its outcome. The perfect delegation is when you delegate to someone because you trust them to make decisions the way you would — or at least in a way you respect and understand.
You can’t fully delegate to AI — and frankly, you shouldn’t. AI requires prompting, interpretation, and post-processing. That’s still you doing the thinking. The implementation cost is low, sure, but the decision-making cost still sits with you. That’s not delegation; it’s assisted execution.
Humans, on the other hand, can be delegated to — truly. Because over time, they internalize your goals, adapt to your context, and become accountable in a way AI never can.
Many reasons why AI can't fill your shoes:
1. Shallow context – It lacks awareness of organizational norms, unspoken expectations, or domain-specific nuance that’s not in the prompt or is not explicit in the code base.
2. No skin in the game – AI doesn’t have a career, reputation, or consequences. A junior human, once trained and trusted, becomes not only faster but also independently responsible.
Junior and Interns can also use AI tools.
So what if the BDD is done?
Read >> Write.
As the final step, you should be cleaning up AI slop, bloated code, useless dependencies, unnecessary tests—or the lack thereof—security gaps, etc. Either way, any fine-tuning should happen in the final step.
This review stage will still eat up any time gains.
Is the AI result good enough? fix it, or refeed to AI to fix it.
That said, I disagree with the idea that it’s merely about aesthetics.(Hegel’s dialectic, for example, isn’t just a stylistic choice — its structure actively shapes meaning and allows for a better synthesis.)
I don't think the author wants to engage and have meaningful conversations, his position is clear.
A meaningful conversation - at least how i see it -, involves acknowledging both the pros and cons of any position. Even if you believe the pros outweigh the cons — which is a subjective judgment — you should still be able to clearly enumerate the cons. That’s is an analytical approach.
this is one of the lessons of The first minute, a short book that goes well with this blog post.
When everyone agreed to LinkedIn’s terms, no one agreed at the time to have their personal data used to train AI.
an extra tool(window to our inner bits) without the necessity of making a biopsy is always welcome.
I am assuming, of course, that everyone will break down a path into their own personal steps rather than just downloading an random roadmap.
I can see this being more appealing than a boring to-do list.
If you want to bypass a paywall, the best tool is https://www.removepaywall.com/. It consolidates a few different approaches to breaking paywalls, such as using the Internet Archive or Google Cache and a few others. you can just open straight in https://www.removepaywall.com/search?url=<URL>
However, I am not suggesting that you bypass paywalls, as paid content is somewhat essential to how news outlets make money, I am just sharing the first google result.