_pastel · HackerTrans

_pastel

no profile record

投稿

A Philosophy of Code Review

benpastel.com

4 ポイント投稿者 _pastel昨年1 コメント

Tinfoil Hat Tips

llam15.github.io

2 ポイント投稿者 _pastel6 年前0 コメント

コメント

3 か月前議論

The tradeoff is highly contextual; it's not a tradeoff an agent can always make by inspecting the project themselves.

Even within the same project, for a given PR, there are some parts of the codebase I want to modify freely and some that I want fixed to reduce the diff and testing scope.

I try to explain up-front to the agent how aggressively they can modify the existing code and which parts, but I've had mixed success; usually they bias towards a minimal diff even if that means duplication or abusing some abstractions. If anyone has had better success, I'd love to hear your approach.

昨年議論

Bike is the one that gets me - when the full Ode to Joy hits I tear up every time.

2 年前議論

You could fine-tune the embedding model to reduce cosine distance on a more specific function.

2 年前議論

I work with an extremely effective machine learning engineer, and the biggest thing I've learned is how far you can get with vibes, even in a more traditional ML situation.

He invests most of his time visualizing the inputs and outputs of his systems very carefully, instead of focusing super heavily on metrics; this is a lot more effective than I thought it would be, particularly in the early stages of a project.

2 年前議論

Why is max_seq_len set to 2048 [1] when the model card says the context size is 8k [2]?

[1] https://github.com/meta-llama/llama3/blob/14aab0428d3ec3a959...

[2] https://github.com/meta-llama/llama3/blob/14aab0428d3ec3a959...

2 年前議論

Tooling around embeddings has improved. Creating and fine-tuning custom embeddings for your tabular data should be easier and more powerful these days.

2 年前議論

100% agree.

One thing that helps is hooking metabase up to its own database and building queries on your queries, e.g.:

    select *
    from report_card 
    where dataset_query ilike '%' || {{query}} || '%'

(You can also join in metadata like the author, when it was last ran, etc.)

We also try really hard to keep the Collection directory structure clean and consistent. But it's still really hard.

3 年前議論

Not only is it not constant time, it's not even polynomial - it's psuedo-polynomial. Also it'll fail on negative numbers, right? You'll need something like `10000 * log(time + min(time) + 1)` to be linear in the bits used to represent the inputs.

> In computational complexity theory, a numeric algorithm runs in pseudo-polynomial time if its running time is a polynomial in the numeric value of the input (the largest integer present in the input)—but not necessarily in the length of the input (the number of bits required to represent it), which is the case for polynomial time algorithms.

https://en.m.wikipedia.org/wiki/Pseudo-polynomial_time

3 年前議論

Some ways to make recipients feel more comfortable:

- You can suggest some other contribution. "Would you mind bringing snacks? / Would you mind handling music on the drive? / Would you mind giving X a ride?"

- You can allow them to reciprocate in less expensive situations, like taking the check when you are at a cheaper place.

3 年前議論

True in this situation, but note that intermediate activations and gradients do take memory and in other contexts that's the limiting factor. For example purely convolutional image networks generally take fixed-size image inputs, and require cropping or downsampling or sliding windows to reach those sizes - despite the convolution memory usage being constant for whatever input image size.

3 年前議論

Ah, the celery semantics.

3 年前議論

Interesting how Gitlab repeatedly emphasizes it's based on "cost of market", not "cost of living".

3 年前議論

So in the sparse grams explanation, what are the bigram weights?

Is it inverse frequency, so common bigrams get split last? And the goal is to be able to search on a larger gram that covers the more common trigrams as often as possible?

3 年前議論

From https://acoup.blog/2019/07/26/collections-war-elephants-part.... I highly recommend the whole series.

> At Bagradas (255 B.C. – a rare Carthaginian victory on land in the First Punic War) [...] the elephants disorder the Roman line. In the spaces between the elephants, the Romans slipped through, but encountered a Carthaginian phalanx still in good order advancing a safe distance behind the elephants and were cut down by the infantry, while those caught in front of the elephants were encircled and routed by the Carthaginian cavalry. What the elephants accomplished was throwing out the Roman fighting formation, leaving the Roman infantry confused and vulnerable to the other arms of the Carthaginian army.

[...]

> Elephants could also be used as area denial weapons. One reading of the (admittedly somewhat poor) evidence suggests that this is how Pyrrhus of Epirus used his elephants – to great effect – against the Romans. It is sometimes argued that Pyrrhus essentially created an ‘articulated phalanx’ using lighter infantry and elephants to cover gaps – effectively joints – in his main heavy pike phalanx line. This allowed his phalanx – normally a relatively inflexible formation – to pivot.

[...]

> Thus the war elephant wasn’t a ‘battle winner’ so much as a dangerous complication thrown in the way of the enemy’s plan of attack. And at that, they were awesome.

4 年前議論

Did you target cloud infrastructure from the beginning, or fall into it by chance? Do you think that's an easier entry point than general programming?

4 年前議論

I had a graduate algorithms class that was graded like this, but the teacher didn't explain and I was clueless. I spent the whole semester super stressed and convinced I was failing, then was shocked and befuddled by an A. "Emotionally trying" is an accurate description of how it felt.

Props to this professor; struggling in confusion is a lot more fun if you know that's the game you're supposed to be playing.

4 年前議論

I see this when giving and receiving form advice in a few physical disciplines. "Just relax your shoulders here and move naturally."

Physical mastery often looks relaxed, natural, and simple, because all extraneous effort has been removed. When you're training hard to reach that state, the "just" can really sting. It feels like: "not only are you bad at this, but it's simple to not be bad at this".

4 年前議論

Thanks for all your work!

If you don't mind some off-topic feedback on the Dominion website - have you considered making the Tables screen default to "New" only? At busy times, that screen consistently lags for several seconds while displaying hundreds (thousands?) of running and finished games. It's always a pain to wait for it before de-selecting "Running" and "Post-Game".

4 年前議論

Word of warning - if you write your own task queue at a startup, you will spend the rest of your tenure justifying this decision to every new data engineer who joins.

Also, am I crazy or do the celery docs not even clarify their delivery semantics? Isn't that table stakes for a queueing system? As best as I could tell you can get close to "at least once" with

  acks_late=True, task_reject_on_worker_lost=True

but not in cases like a worker hanging indefinitely without being explicitly killed.

4 年前議論

If you're interested in browsing creative prompts, I highly recommend the reddit community at r/dalle2.

Some are impressive:

  - www.reddit.com/r/dalle2/comments/uzosy1/the_rest_of_mona_lisa
  - www.reddit.com/r/dalle2/comments/vstuns/super_mario_getting_his_citizenship_at_ellis

And others are hilarious:

  - www.reddit.com/r/dalle2/comments/v0pjfr/a_photograph_of_a_street_sign_that_warns_drivers
  - www.reddit.com/r/dalle2/comments/wbbkbb/healthy_food_at_mcdonalds
  - www.reddit.com/r/dalle2/comments/wlfpax/the_elements_of_fire_water_earth_and_air_digital