Pluto is great. I use it all the time. If you like the reactivity/reproducibility but are wedded to Python, you might want to check out Marimo, which is also great. [https://marimo.io/] It too puts the output of a cell above the code so if you're unable to adapt to things that are different it's also probably not for you. FWIW, Observable's Notebooks (Javascript) work the same way: output above the code... - Source: Hacker News / 2 months ago

Marimo notebooks give you the best of both worlds (https://marimo.io). - Source: Hacker News / 4 months ago

Agree with the author, will add: duckdb is an extremely compelling choice if you’re a developer and want to embed analytics in your app (which can also run in a web browser with wasm!) Think this opens up a lot of interesting possibilities like more powerful analytics notebooks like marimo (https://marimo.io/) … and that’s just one example of many. - Source: Hacker News / 7 months ago

The training pipeline uses Marimo notebooks (think Jupyter, but reactive). Models are quantized to uint8 and served via CDN. Total bundle for a predictor: up-to 2MB. - Source: dev.to / 8 months ago

Marimo is a Jupyter notebook with each cell being somewhat logically connected to each other. That's way if you update the value of a variable in a cell and re-run it, related values in other cells will be auto-updated and auto-run. This is called reactive execution. Thus the notebook can act as a single python script or app and has an extension of .py instead of .ipynb. - Source: dev.to / 9 months ago

Line length, spacing, and indentation matter. My preference for code is roughly 80 to 110 characters. Longer lines become tiring to scan, while very short lines can create excessive wrapping. For formatting, tools like Prettier reduce debate and keep code visually consistent across contributors. - Source: dev.to / about 1 month ago

137Foundry provides legacy modernization services that include dependency mapping as a foundational assessment phase. Prettier and ESLint are useful companion tools for enforcing code style consistency as the refactoring proceeds. Node.js and Python.org official documentation are authoritative references for understanding the import and module systems of those runtimes. - Source: dev.to / 3 months ago

Prettier and ESLint are useful tools for establishing consistent code style as a baseline before starting structural refactoring - style differences in a diff make behavioral changes harder to spot. OWASP provides useful checklists for security-critical code review that apply directly to the critical path review step. - Source: dev.to / 3 months ago

The matcher field takes a regex pattern. Edit|Write means this hook only fires when the Edit or Write tool is used. Claude running Bash, Read, or any other tool won't trigger it. The command itself uses jq to extract the file path from the tool input JSON, then pipes it to Prettier. Every file Claude touches gets formatted automatically. - Source: dev.to / 5 months ago

The better approach: let the agent write code however it wants, then run Prettier, Black, Ruff, or ESLint. Zero ambiguity. The agent doesn't need to think about formatting at all, which means fewer tokens spent and fewer decisions that could go wrong. - Source: dev.to / 5 months ago