๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Boris Dayma ๐Ÿ–๏ธ
@borisdayma
๐Ÿ–๏ธ Founder of Craiyon ๐Ÿฅ‘ Author of dalle-mini
๊ฐ€์ž… February 2012
357 ํŒ”๋กœ์ž‰ ์ค‘    14.2K ํŒฌ
Claude/Codex have helped me update codebases very fast, but for new repos/scripts/logic, not completely sure of the positives. 1/ it can often one-shot a working solution, but itโ€™s often over-designed, lots of abstractions, tests, security paranoia where not needed, etc 2/ I used to develop everything through Jupyter notebooks, explore, test, etc. It was actually quite fast, great for exploring deeply my workflow, edge cases, etc 3/ now, maybe because of laziness, maybe thinking it will be faster/better/more efficient, I resort to Claude/Codex. Itโ€™s likely ok for quick or non-important features (personal admin dashboard/monitoring), but Iโ€™m not convinced of the long term value 4/ "but what about karpathy auto-research loop workflow"? I think it has its use cases, but you cannot prompt forever "make it better, here is the target" on every type of problem. Also on any specialized project, I donโ€™t think LLM can reach the insight/creativity of humans, and those are better triggered through step-by-step development / visualization of the full pipeline vs just a top level overview
๋” ๋ณด๊ธฐ