rileymichael

the tests are validating the plugin by executing actual builds in an isolated/temporary gradle project. debugging doesn't work out of the box because it's another process

https://docs.gradle.org/current/userguide/test_kit.html#sub:...

there's currently ~6k open issues and ~20k closed ones on their issue tracker (https://github.com/anthropics/claude-code/issues). certainly a mix of duplicates / feature requests, but 'buggy mess' seems appropriate

successful how? the only metric i see is # of pull requests which means nothing. hell, $dayJob has hundreds of PRs generated weekly from renovate, i18n integrations, etc. with no LLM in the mix!

LLMs are trained on source code, so that's what they can (barely) write. Decompiling is a -lossy- action which means that training directly on the output would have much less information and would be a nightmare if one (human or llm) needs to debug.

yeah the recent “LLMs will just make the binary directly” comment should be a massive signal that the guys clueless

considering their series F was only ~5 months ago this doesn't seem too far-fetched!

this is likely an ecosystem sort of thing. if your language gives you the tools to do so at no cost (memory/performance) then folks will naturally utilize those features and it will eventually become idiomatic code. kotlin value classes are exactly this and they are everywhere: https://kotlinlang.org/docs/inline-classes.html

the incident has now expanded to include webhooks, git operations, actions, general page load + API requests, issues, and pull requests. they're effectively down hard.

hopefully its down all day. we need more incidents like this to happen for people to get a glimpse of the future.

A bunch of people with poor programming experience could get together and start claiming their new tool is the future.

Doesn’t mean the tool is actually useful, no matter how many people join the community.

> Generally, I believe R1 has the potential to change the world.

oh man this is fantastic

> In rule form: - Code must not be written by humans - Code must not be reviewed by humans

as a previous strongDM customer, i will never recommend their offering again. for a core security product, this is not the flex they think it is

also mimicking other products behavior and staying in sync is a fools task. you certainly won't be able to do it just off the API documentation. you may get close, but never perfect and you're going to experience constant breakage

it all matters. if more people took pride in their craft and understood the behavior of their tools, modern software wouldn’t be so horrid

> I don’t care what type of weird tricks the compiler did for optimizations.

you might not, but plenty of others do. on the jvm for example, anyone building a performance sensitive application has to care about what the compiler emits + how the jit behaves. simple things like accidental boxing, megamorphic call preventing inlining, etc. have massive effects.

i've spent many hours benchmarking, inspecting in jitwatch, etc.

> I don’t read code anymore

> Senior Technical Product Manager

yeah i'd wager they didn't read (let alone write) much code to begin with..

> is copying the game outright legal

no it is not. a lot of runescape servers have recently been receiving UDRP disputes (to get domain + contact info) and subsequent legal communications from jagex

i don't care about the 'analytical signal'. the purpose is people can't tell if im writing a (discord, slack, etc.) message from my phone or laptop or desktop, and it works for that

simple toggle to disable it permanently

my reasoning is that i don’t want identifiable markers for what device im writing from. so all auto-* (capitalization, correct, etc.) features are disabled so that i have raw input

> LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building

as the former, i've never felt _more ahead_ than now due to all of the latter succumbing to the llm hype

by default it'll be exposed as a `java.lang.Object` and they've thought about using compiler plugins to generate methods returning `Optional<>` or `Result<>` instead

https://www.youtube.com/watch?v=IUrA3mDSWZQ&t=2626s

microslop copilot strikes again

> MkDocs: Works great with JS disabled, however the table of contents needs to be maintained via mkdocs.yml, which can be quite tedious.

note that the mkdocs-material folks are now working on https://zensical.org/ which is in rust and _much_ faster. it solves this specific requirement by autogenerating the navigation based on file structure.

it's still early / under active development, but i recently rebuilt our techdocs on top of it. a simple github workflow to aggregate from our two monorepos + some bash-fu to merge them together and voila! no config file headaches

fyi the project appears to be private :)

sorry to hear. perhaps you could goodhart's law it and setup some background cron that simulates usage

no, this is coming from the fact OP states they are miserable. that is unsustainable. at the end of the day the more productive setup is the one that keeps you happy and in your chair long term, as you'll produce nothing if you are burnt out.

yep.. learning vim or all of the keybinds/tools at ones disposal in $jetbrains_editor would _actually_ make some peers 2x faster but alas..

> I also can’t stop myself from using Claude Code and the like.

just.. uninstall it? i've removed all ai tooling from both personal+work devices and highly recommend it. there's no temptation to 'quickly pull up $app just to see' if it doesn't exist

> Everybody in the industry is vibecoding right now

no ‘everybody’ is not. a lot of us are using zero LLMs and continuing to build (quality) software just fine

i mentioned a few months ago that it was a shame where graphite was headed re: AI (https://news.ycombinator.com/item?id=44955187). this appears to be the final nail in the original products coffin

for anyone else looking for a replacement, git spice and jujutsu are both fantastic

hoping for some disruption here. gha is an absolutely horrid platform for anyone trying to build optimized workflows. so many bugs / rough edges that haven't been addressed for years, the hosted runners feel like decade old compute. missing all of the modern features (like dynamic pipelines) other providers offer.

to top it all off, they round up to the nearest whole minute instead of billing for actual usage which i assume they'll use for this new charge.

this has been all but confirmed for a while. they’re really spinning their wheels on products lately only to kill them, this air.dev slop will undoubtedly meet the same fate. all the while their core products continue to rot