KaseKun
Joined 6 years ago
Joined 6 years ago
Not really a requirement, if you did fine without the tools before you would do fine again. The difference is you would know which ones are worth manually maintaining
Code bases that you "work in" (maintain, etc) solve real world problems, and solving those problems should trump cleanliness every time
Codebases that are clean are typically showcase examples that sit on a shelf to be admired and appreciated.
You do indeed need to do quite a bit of thinking and problem solving, to build things with an llm.
If you disagree, repeat this project, so you can share with us how little thinking it required.
On either side it says "I just ask the model why it did that"
realistically, though, i quite like writing. The other article i've posted ( https://www.dardar.co/articles/your-data-agent-is-wrong ) is 100% me, but as a consequence it feels kinda preachy and verbose in places haha
The creator certainly got pretty crook from ingesting baking soda
I guess this goes to show that even a subtle touch of an LLM can undermine authenticity.
edit: i've removed that line. I don't like to edit articles after publish (call me old fashioned, but i try to be honest and transparent), in this case though the line adds nothing and your call-out has taught me a good lesson: shit human writing is better than "good" AI writing.
> It looks like someone just pointed a LLM at the codebase and asked it to write an article.
Not entirely true. I pointed an LLM at the codebase to get me to the right files for understanding skills, and to map out the dependencies and lifecycles - Then I spent quite a bit of time reading the code myself and writing about it.
An AI review at the end of the writing (to "sharpen" the language) unfortunately brought in a couple of AI fingerprints (note the "mic drop" comment above)
edit: write -> right (its 8am)