micw
Joined 6 years ago
Joined 6 years ago
Example: Lifting a 10-metric-ton stone by 36 meters stores just about 1 kilowatt-hour (kWh) of energy. This is roughly equivalent to the capacity of a small power station used for a camping trip.
I doubt that. Currently the cells itself makes only <50% (maybe <30% meanwhile) of a PV module. So the limit to the bottom is by the glass and frame and cable, not by the cells.
But $/watts can significantly go down with more efficiency.
I have created wrappers for Codex (https://github.com/micw/codex-wrapper-advanced) and claude (https://github.com/micw/claude-wrapper-advanced) that uses their SDK (Codex) and the CLI (Claude) internally to align with the subscription ToS and still have a common API ;-) This way I can use both in any harness and can easily switch between both.
If you give a smart one a task, he will look for a way to do it with lowest effort. Probably most would do it but the smart ones will find way more the shortcuts, automations and exploits.
Edit: also smart people will more often ask "why" if a task makes no sense to them.
Just kidding. Of course there's doom for postgres: https://github.com/cedardb/DOOMQL (pure SQL) and https://github.com/DreamNik/pg_doom (extension).
Oh and there's https://github.com/snaplet/postgres-wasm that allows to run everything else in postgres ^^
- explore the features and behaviour of the existing code
- first write lots of E2E tests for literally everything
- human-in-the-loop to review the feature list and test cases to see if some obvious or important stuff is missing
- then let implement it and verify by tests
I used this in (way) smaller scenarios and got really good examples with minimal human interaction.