Ben
@benrules2.bsky.social
A search engine can only be as good as the user’s clarity of intent! Without this the forces of reco vs relevance will forever clash.
March 18, 2025 at 12:35 PM
A search engine can only be as good as the user’s clarity of intent! Without this the forces of reco vs relevance will forever clash.
Reposted by Ben
Reposted by Ben
Reposted by Ben
Things like abstracting the logging classes come up as well. Strong abstractions make your application more portable, but are not at all valuable for services. But your repo picks a strategy within the first few commits often.
November 21, 2024 at 12:22 PM
Things like abstracting the logging classes come up as well. Strong abstractions make your application more portable, but are not at all valuable for services. But your repo picks a strategy within the first few commits often.
Have been pondering the same. The release patterns are so different, even simple dev best practices can really diverge.
For example multi commit PRs, debating squash and merge vs just rebase. Cherry picking a single commit is easier for managing distinct releases, but removes info from git log.
For example multi commit PRs, debating squash and merge vs just rebase. Cherry picking a single commit is easier for managing distinct releases, but removes info from git log.
November 21, 2024 at 12:21 PM
Have been pondering the same. The release patterns are so different, even simple dev best practices can really diverge.
For example multi commit PRs, debating squash and merge vs just rebase. Cherry picking a single commit is easier for managing distinct releases, but removes info from git log.
For example multi commit PRs, debating squash and merge vs just rebase. Cherry picking a single commit is easier for managing distinct releases, but removes info from git log.