HackerTrans
トップ新着トレンドコメント過去質問紹介求人

7d7n

no profile record

投稿

Advice for new principal tech ICs (i.e., notes to myself)

eugeneyan.com
137 ポイント·投稿者 7d7n·9 か月前·151 コメント

How to Train an LLM-RecSys Hybrid for Steerable Recs with Semantic IDs

eugeneyan.com
1 ポイント·投稿者 7d7n·10 か月前·0 コメント

How to Train an LLM-RecSys Hybrid for Steerable Recs

eugeneyan.com
2 ポイント·投稿者 7d7n·10 か月前·0 コメント

Evaluating Long-Context Question and Answer Systems

eugeneyan.com
2 ポイント·投稿者 7d7n·昨年·0 コメント

Building an agentic workflow for my daily news with MCPs, Q, and tmux

eugeneyan.com
2 ポイント·投稿者 7d7n·昨年·0 コメント

An LLM‑as‑Judge Won't Save the Product–Fixing Your Process Will

eugeneyan.com
2 ポイント·投稿者 7d7n·昨年·0 コメント

An LLM‑as‑Judge Won't Save Your Product–Fixing Your Process Will

eugeneyan.com
1 ポイント·投稿者 7d7n·昨年·0 コメント

FAQ on Writing: How I got started, why I write, who I write for

eugeneyan.com
2 ポイント·投稿者 7d7n·昨年·0 コメント

Frequently Asked Questions about My Writing Process

eugeneyan.com
2 ポイント·投稿者 7d7n·昨年·0 コメント

Improving recommendation systems and search in the age of LLMs

eugeneyan.com
408 ポイント·投稿者 7d7n·昨年·93 コメント

A Spark of the Anti-AI Butlerian Jihad (On Bluesky)

eugeneyan.com
6 ポイント·投稿者 7d7n·2 年前·1 コメント

Patterns for Building LLM-Based Systems and Products

eugeneyan.com
2 ポイント·投稿者 7d7n·2 年前·0 コメント

Evaluating the Effectiveness of LLM-Evaluators (a.k.a. LLM-as-Judge)

eugeneyan.com
2 ポイント·投稿者 7d7n·2 年前·0 コメント

Some Paradoxical Rules of Writing

eugeneyan.com
2 ポイント·投稿者 7d7n·2 年前·0 コメント

How to Interview and Hire ML/AI Engineers

eugeneyan.com
1 ポイント·投稿者 7d7n·2 年前·0 コメント

Bluesky Social Dataset (235M posts from 4M users)

zenodo.org
91 ポイント·投稿者 7d7n·2 年前·40 コメント

How to Run a Weekly Paper Club (and Build a Learning Community)

eugeneyan.com
1 ポイント·投稿者 7d7n·2 年前·0 コメント

Lessons on Building ML Systems, Scaling, Execution, and More

eugeneyan.com
2 ポイント·投稿者 7d7n·2 年前·0 コメント

My Minimal MacBook Pro Setup Guide

eugeneyan.com
3 ポイント·投稿者 7d7n·2 年前·1 コメント

AlignEval: Making Evals Easy, Fun, and Semi-Automated

eugeneyan.com
2 ポイント·投稿者 7d7n·2 年前·0 コメント

コメント

7d7n
·昨年·議論
Not at all! I appreciate the kind words. Thank you!
7d7n
·昨年·議論
haha that wasn't me ;)
7d7n
·昨年·議論
Thank you for the feedback! I'm sorry you found it jargony/less accessible than you'd like.

The intended audience was my team and fellow practitioners; assuming some understanding of the jargon allowed me to skip the basics and write more concisely.
7d7n
·2 年前·議論
Pollution of online social spaces caused by rampaging d/misinformation is a growing societal concern. However, recent decisions to reduce access to social media APIs are causing a shortage of publicly available, recent, social media data, thus hindering the advancement of computational social science as a whole. To address this pressing issue, we present a large, high-coverage dataset of social interactions and user-generated content from Bluesky Social.

The dataset contains the complete post history of over 4M users (81% of all registered accounts), totaling 235M posts. We also make available social data covering follow, comment, repost, and quote interactions.

Since Bluesky allows users to create and bookmark feed generators (i.e., content recommendation algorithms), we also release the full output of several popular algorithms available on the platform, along with their timestamped “like” interactions and time of bookmarking.

This dataset allows unprecedented analysis of online behavior and human-machine engagement patterns. Notably, it provides ground-truth data for studying the effects of content exposure and self-selection, and performing content virality and diffusion analysis.
7d7n
·2 年前·議論
haha I'm glad you noticed!

it's originally "Ready to ~~delve~~ dive in?" but something got lost in translation
7d7n
·2 年前·議論
100% agree with Ted's take. One of the authors wrote about splitting up prompts here too: https://eugeneyan.com/writing/prompting/#split-catch-all-pro...
7d7n
·2 年前·議論
The goal is to solve complex problems with as simple a solution as possible.
7d7n
·3 年前·議論
For some use cases, legal reasons such as proprietary/private data, copyright, terms of service, prevent the use of a 3rd-party API.

On the other hand, directly using an off-the-shelf model, even the best ones, may not meet your performance requirements.

That’s where fine-tuning an open LLM is necessary.