6 ms·
So hard to tell if this is parody or not.
by cschep 1y ago
So hard to tell if this is parody or not.
- Sinidir 1y agoIts not really hard to tell.
- cschep 1y ago1,000 more tests!? That reads coherent to you?
- cpursley 1y agoHere's one Claude-vibed project that makes me money that I run in addition to my saas, which is Elixir. I'm not strong in TypeScript and this is an Astro static site, so Claude has been really helpful. Backend is Supabase (postgres) and a few background jobs via https://pgflow.dev https://pgflow.dev (pgmq) that fetch and populate job openings and uses some AI steps to filter then classify into the correct categories (among other things, there's also an job application flow and automated email newsletter): https://jobsinappraisal.com https://jobsinappraisal.com I also "vibed" up this: https://livefilter.fly.dev/todos https://livefilter.fly.dev/todos (https://github.com/cpursley/livefilter https://github.com/cpursley/livefilter) and this: https://star-support-demo.vercel.app/en/getting-started https://star-support-demo.vercel.app/en/getting-started (https://github.com/agoodway/star-support-demo https://github.com/agoodway/star-support-demo) I hand wrote very little of this code, but can read most of it - the SQL and Elixir at least ;)
- cess11 1y agoIs there a reason why you're using 'when is_struct/2' instead of pattern matching here? https://github.com/cpursley/livefilter/blob/main/lib/live_filter/date_utils.ex https://github.com/cpursley/livefilter/blob/main/lib/live_fi...
- napsterbr 1y agoThis is clearly low quality, non-idiomatic AI-generated Elixir code. So the likely answer is that "you" did not use this at all; AI did. I review this kind of AI-generated Elixir code on a daily basis. And it makes me want to go back to ~2022, when code in pull requests actually made sense. Apologies for the rant, this is just a burnt out developer tired of reviewing this kind of code. PS: companies should definitely highlight "No low-quality AI code" in job listings as a valid perk.
- cpursley 1y agoFwiw, the date range part of this is the lowest quality, I even have an issue open: https://github.com/cpursley/livefilter/issues/2 https://github.com/cpursley/livefilter/issues/2 In production code I'd do a couple passes and tell it to lean into more function head and guard matching, etc. But it does compiles, and works: https://livefilter.fly.dev/todos?filters%5Bassigned_to%5D%5Boperator%5D=in&filters%5Bassigned_to%5D%5Btype%5D=enum&filters%5Bassigned_to%5D%5Bvalues%5D%5B0%5D=jane_smith&filters%5Bassigned_to%5D%5Bvalues%5D%5B1%5D=john_doe&filters%5Bdue_date%5D%5Bend%5D=2025-08-15&filters%5Bdue_date%5D%5Boperator%5D=between&filters%5Bdue_date%5D%5Bstart%5D=2025-07-17&filters%5Bdue_date%5D%5Btype%5D=date&filters%5Bstatus%5D%5Boperator%5D=in&filters%5Bstatus%5D%5Btype%5D=enum&filters%5Bstatus%5D%5Bvalues%5D%5B0%5D=in_progress https://livefilter.fly.dev/todos?filters%5Bassigned_to%5D%5B...