capplexham

5 ms·

1. 1.▲
   by capplexham 1mo ago

   The paradigm shift from ETL to ELT is what went wrong with Data Lakes. An enormous amount of business logic and effort was historically accumulated in the Extract-Transform stage (usually in COBOL or SQL), and then Loaded into a Data Mart f
2. 2.▲
   by capplexham 3mo ago

   Have a look at the prompts in the GitHub [0]. It defines a System Prompt and specifies the documentation structure. This would allow you to switch coding agents, instead of relying on how your coding agent interprets the command "write
3. 3.▲
   The Latent Capability Ceiling: When a Bigger Model Won't Fix Your Problem(tianpan.co)

   3 points by capplexham 3mo ago|0 comments
4. 4.▲
   by capplexham 3mo ago

   Click "Show Options", then: - Check "Show chords on piano?" - Check "Play chord sounds" - Uncheck "Play feedback sounds" For the "Chords", start with just Red and Blue. Then add Yellow. I do
5. 5.▲
   by capplexham 6mo ago

   > The LLM makes this easier but the improvement drops to about 2-3x b/c there is a lot of back and forth + me reading the code to confirm etc This makes sense when you stop viewing the LLM as a "vending machine" for apps a
6. 6.▲
   by capplexham 6mo ago

   This isn’t surprising when you consider how LLMs are actually trained to write code. Expecting a one-shot 1.0 release is unrealistic because the sheer volume of context and decision-making required for a finished product is enormous. Instea