21–30 of 67 posts
Earlier quoted context omitted.
Someone's given it a shot: https://github.com/obsidianmd/obsidian-importer/pull/424
Can't help but think if the author of that PR had been less defeatist and snarky they would have had a chance at decent discussion about it being a viable option (with AI).
At least have it be split into some files and structured in some way.
Everyone is looking down on LLM-assisted dev here, but I think it's a great fit. I also don't believe it can be one-shotted (there's too many deltas between Notion's API and Obsidian). With that said, LLMs are great for enumerating edge-cases, and this feels like the perfect task for Codex/Claude Code. I'd implore the obsidian team/maintainers to take a stab at building this with LLMs. Based on personal experience, t…
A month ago I migrated company's website and blog from Framer to Astro (https://quesma.com/blog/ is you would like to see the end result).
This weekend I created a summary of Grafana dashboard data. LLMs are tireless at checking hypothesis, running grunt code, seeing results, and iterating on that.
What takes more than a single is to check if the result is correct (nothing missed, nothing confabulated, no default fallbacks) and to maintain code quality (I refactor early and often, here is a place in Claude Code that there is no other way than using Opus 4.1). Most of my time spend talking with Claude Code ais in refactoring - and it requires most knowledge of tooling, abstraction, etc.
Earlier quoted context omitted.
Autocorrect is not generative AI in the way that anyone is using that word. Also autocorrect doesn't even need to use any sort of ML model.
Ah yes the duality of anti-AI crowds on HN. “GenAI is just fancy autocorrect”, and “autocorrect isn’t actually GenAI”. The thing is, if you’re talking about making laws (as GP is), your “surely people understand this difference” strategy doesn’t matter squat and the impact will be larger than you think.
Earlier quoted context omitted.
Why? It doesn't say you need to have extensive experience with them. I would assume this is mostly to dissuade applicants that are not aware of the potential challenges ahead.
This "exploring" can take tremendous amounts of time, depending on the complexity of these APIs. My time is worth a lot to myself. I am not going to spend many hours for a chance of winning 5k$. If this takes a week off of my free time its not worth 5k to me.
Earlier quoted context omitted.
Can't help but think if the author of that PR had been less defeatist and snarky they would have had a chance at decent discussion about it being a viable option (with AI).
It's 1100 lines of code in a single file that nobody understands. That's instant spaghetti right there, not a valid PR. At least have it be split into some files and structured in some way.
spaghetti code is code that snakes through the code base in a hard-to-follow way
In addition to what's already in the thread, I assume by now somebody has vibecoded an agent to scan GitHub for bounties and then automatically vibe up a corresponding solution. Will be a fun source of spam for anyone who wants to do the right thing and pay people for good work.
I recently got my first AI generated PR for a project I maintain and it was honestly a little stressful. My first clue was that PR description was absurdly detailed and well structured... yet the actual changes were really scattershot. A human with the experience and attention to detail to produce that detailed description would likely also have broken it down into seperate PRs. And the code seemed alright until I no…
There are also open bounties by comma.ai, is it becoming more common? https://github.com/orgs/commaai/projects/26/views/1
Everyone is looking down on LLM-assisted dev here, but I think it's a great fit. I also don't believe it can be one-shotted (there's too many deltas between Notion's API and Obsidian). With that said, LLMs are great for enumerating edge-cases, and this feels like the perfect task for Codex/Claude Code. I'd implore the obsidian team/maintainers to take a stab at building this with LLMs. Based on personal experience, t…
We all lean on LLMs in one way or another, but HN is becoming infested with wishful prompt engineers. Show, dont tell. Compete on the market instead of yet another PoC.