111–120 of 165 posts
It wasn’t until I loaded the content into a hex editor that I learned about U+00A0, the non-breaking space. Looks like a space, but isn’t.
dd/mm/yyyy date formats are cursed.... Perhaps it is mm/dd/yyyy (really?!?) that is cursed....
It's the reason our codebase is filled with momentAmerican, parseDateAmerican and parseDatetimeAmerican.
Earlier quoted context omitted.
I agree, I usually put this sort of information in the commit message itself. That way it's right there if anybody ever comes across the line and wonders "why did he write this terrible code, can't you just ___".
As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.
No difference between a git index and any other binary data (like video).
One of their line items complains about being unable to bind 65k PostgreSQL placeholders (the linked post calls them "parameters") in a single query. This is a cursed idea to begin with, so I can't fully blame PostgreSQL. From the linked GitHub issue comments, it looks like they adopted the sensible approach of refactoring their ORM so that it splits the big query into several smaller queries. Anecdotally, I've found…
Earlier quoted context omitted.
As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.
You are sadly completely missing the point of ever-self-improving automation. Just also use the commit history. Better yet: don't be a bot slave that is controlled and limited by their tools.
I don't think you understand the issue you're commenting on.
It's irrelevant whether you can inject commit history in a prompt.
The whole point is that today's support for coding assistants does not support this source of data, whereas comments in source files and even README.md and markdown files in ./docs are supported out of the box.
If you rely on commit history to provide context to your team members, once they start using LLMs this context is completely ignored and omitted from any output. This means you've been providing context that's useles and doesn't have any impact on future changes.
If you actually want to help the project, you need to pay attention on whether your contributions are impactful. Dumping comments into what amounts to /dev/null has no impact whatsoever. Requiring your team to go way out of their way to include in each prompt extra context from a weird source that may or may not be relevant is a sure way to ensure no one uses it.
Earlier quoted context omitted.
> Disappointing to hear about the Cloudflare fetch issue. You mean the one where explicitly configuring Cloudflare to forward requests to origin servers as HTTP will actually send requests as HTTP? That is not what I would describe as disappointing.
The behavior seems likely to mislead a lot of people even if it doesn't confuse you.
You need to go way out of your way to toggle a switch to enable this feature.
The toggle says very prominently "Cloudflare allows HTTPS connections between your visitor and Cloudflare, but all connections between Cloudflare and your origin are made through HTTP."
You proceed to enable this feature.
Does it confuse you that Cloudflare's requests to your origin servers are HTTP?
Earlier quoted context omitted.
As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.
There's no reason that an LLM couldn't (or isn't) being trained on commit messages. No difference between a git index and any other binary data (like video).
You are arguing that it could. Hypotheticals.
But getting back to reality, today no coding assistant supports building system prompts from commit history. This means it doesn't. This is a statement of fact, not an hypothetical.
If you post context in commit messages, it is not used. If you dump a markdown file in the repo, it is used automaticaly.
What part are you having a hard time understanding?
This is awesome! Does anyone else wanna share some of the cursed knowledge they've picked up? For me, MacOS file names are cursed: 1. Filenames in MacOS are case-INsensitive, meaning file.txt and FILE.txt are equivalent 2. Filenames in MacOS, when saved in NFC, may be converted to NFD
Yep. Create a case-sensitive APFS or HFS+ volume for system or data, and it guarantees problems.
Earlier quoted context omitted.
There's no reason that an LLM couldn't (or isn't) being trained on commit messages. No difference between a git index and any other binary data (like video).
> There's no reason that an LLM couldn't (or isn't) being trained on commit messages. You are arguing that it could. Hypotheticals. But getting back to reality, today no coding assistant supports building system prompts from commit history. This means it doesn't. This is a statement of fact, not an hypothetical. If you post context in commit messages, it is not used. If you dump a markdown file in the repo, it is use…
For example:
>The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.
One can really sense the pain just reading the headings Also a crypto library that limits passwords to 72 bytes? That’s wild
It's written with constant memory allocation in mind. Silly of them to use such a small buffer though, make it a configuration option.