Jorge1o1
Joined 8 years ago
Joined 8 years ago
And in the Transformer architecture you’re working with embeddings, which are exactly what this article is about, the vector representation of words.
I suppose you have gumroad / serialized novels or webcomics but I’m not sure if there’s any albums where the musician is putting out one song at a time
- Avoid breaking changes
- Keep APIs stable
- Test and document everything, etc.
I personally think there's nothing wrong with that. We wouldn't say that a musician is *obligated* to put out a second album or a remaster. We wouldn't say that an author *must* make a sequel to their popular book. But when it comes to code sometimes we feel like the original author has an obligation to keep working on it just because it would convenience us.
(edited for formatting)
“Smart People Should Build Things”
>One executive in the entertainment industry said younger people were less inclined to go out raving until 6am as they were more health conscious and less frivolous with money than previous generations
This is the same generation that has 12 step skincare routines, eats only organic food, chooses to vape or zyn rather than smoke because of secondhand smoke, everyone has an Apple watch on their wrist tracking calories, etc.
If anything I’m surprised that binge drinking and going out late as survived as long as it has.
And as far as the money comment, this generation is not less frivolous there’s just less money to go around haha.
Let’s say that you get a positive diagnosis for the disease, and you ask someone the question:
What is the probability you actually have the disease?
Most people will say 95% or 99%, but your actual probability of having the disease in this example is <2%
maybe some combination of the <noscript> tag and then if so wrapping the buttons in <form> and making the buttons submit those forms?
For example, when working with arrays of data it certainly is easier to think and write “avg a+b” to add two arrays together and then take the average.
In a non-array programming language you would probably first need to do some bounds checking, then a big for loop, a temporary variable to hold the sum and the count as you loop over the two arrays, etc.
Probably the difference between like 6ish lines of code in some language like C versus the 6 characters above in Q.
But every language has features that help you reason about certain types of problems better. Functional languages with algebraic data types and pattern matching (think OCaml or F#) are nicer than switch statements or big if-else-if statements. Languages with built-in syntactic sugar like async/await are better at dealing with concurrency, etc.
Capitalism is not perfect, but at least to me this is more of a moral issue than an economic one.
I think your CO2 point is a great example, why would a Communist or Socialist economic system be inherently more eco-friendly than a Capitalist system? You now have a system where there is a government willing to "plan" or "intervene" in certain aspects of the economy, but unless the government actually cares about pollution nothing will happen. You could even theoretically have a centrally-planned economy that WANTS to increase emissions.
The largest polluter in the world is a Communist country, and in the last 30 years their CO2 emissions have sextupled, while the US's emissions per year have remained flat.
Morality != Economics
Not even a human would work that way... you wouldn't open 300 different python files and then try to memorize the contents of every single file before writing your first code-change.
Additionally, you're going to have worse performance on longer context sizes anyways, so you should be doing it for reasons other than cost [1].
Things that have helped me manage context sizes (working in both Python and kdb+/q):
- Keep your AGENTS.md small but useful, in it you can give rules like "every time you work on a file in the `combobulator` module, you MUST read the `combobulator/README.md`. And in those README's you point to the other files that are relevant etc. And of course you have Claude write the READMEs for you...
- Don't let logs and other output fill up your context. Tell the agent to redirect logs and then grep over them, or run your scripts with a different loglevel.
- Use tools rather than letting it go wild with `python3 -c`. These little scripts eat context like there's no tomorrow. I've seen the bots write little python scripts that send hundreds of lines of JSON into the context.
- This last tip is more subjective but I think there's value in reviewing and cleaning up the LLM-generated code once it starts looking sloppy (for example seeing lots of repetitive if-then-elses, etc.). In my opinion when you let it start building patches & duct-tape on top of sloppy original code it's like a combinatorial explosion of tokens. I guess this isn't really "vibe" coding per se.
[1] https://arxiv.org/html/2602.06319v1