Jeremy Chone

6.5K posts

Jeremy Chone banner
Jeremy Chone

Jeremy Chone

@jeremychone

#ProductionCoding - Rust - Cloud App - AI Production Coding - https://t.co/ZXus8BasLM - https://t.co/mPdBE0971q - https://t.co/AdrnFT2AXA

San Francisco Katılım Mart 2007
297 Takip Edilen2.2K Takipçiler
Jeremy Chone
Jeremy Chone@jeremychone·
@plainionist Vibe coding == Figma++ AI Production Coding: - spec driven - spec is the source of truth - code is the proof of truth Human and AI collaborate on spec, AI can generate 95% of code The key is to collaborate throughout. Not to delegate obsessively.
English
0
0
3
258
Seb
Seb@plainionist·
Serious question: If vibe-coded projects produce code humans can't read but AI can, do we end up depending on AI just to maintain our own systems? 🤔
English
287
9
178
36K
Riya
Riya@_riyatwt·
claude code is fucking insane i know literally NOTHING about coding ZERO and i just built a fully functioning web app in minutes. http://localhost:3000/ check it out
English
93
18
503
36K
Jeremy Chone
Jeremy Chone@jeremychone·
@icanvardar Yes, I moved to Zed a few months ago as an experiment, expecting to go back to VS Code. I did not, and since then, 100% #Zed The project switching and overall experience feel so instant, it's hard to go back to anything else. My config: github.com/jeremychone/jc… @zeddotdev
English
0
0
0
169
Zed
Zed@zeddotdev·
🚀 We just shipped v.0.231! Git graph is finally here: Open it from the git panel or the command palette (git graph: open).
Zed tweet media
English
76
88
1.7K
79.7K
Roman
Roman@romxdev·
vibe coding is officially dead I had to say it. we thought AI would let us relax and code "on chill", but instead it turned us into architectural bureaucrats. we write strict laws, define rules, limits, and principles. if you don't obsessively review the code agent writes, your project will mutate into a massive landfill of tech debt within a month.
English
320
190
2.3K
288.3K
Jeremy Chone
Jeremy Chone@jeremychone·
AI is amazing for speeding up code generation. But that applies to good code and bad code. The trick ➜ keep flattening the system design complexity curve, ✅ so it stays focused on good code generation ❌ not bad code proliferation #ProductionCoding #AICoding
English
0
0
2
108
Matt Pocock
Matt Pocock@mattpocockuk·
Every time an LLM says anything to me, I automatically assume it's BS unless it's read a source confirming it NONE of the non-devs I talk to have this instinct
English
193
50
1.2K
60.1K
Jeremy Chone
Jeremy Chone@jeremychone·
@anuraggoel I would even say, we do not need to ship anymore. AI can just use AI without AI. It does not mean much, but it does not matter anymore, AI will figure this one out. So, let’s aim where the puck will be.
English
0
0
1
103
Anurag Goel
Anurag Goel@anuraggoel·
AI is quietly deprecating GitHub. Agents do not need branches, PRs, or CI/CD rituals. They want to ship code straight to the cloud. The rsync renaissance is here. High availability. Zero bloat. Faster loops.
English
341
17
376
483K
Herbert "TheBracket" Wolverson
Herbert "TheBracket" Wolverson@herberticus·
@rustaceans_rs Usually not - but I greatly prefer to make something concrete first and add traits if I actually need a second type to implement something. For me, it's enums and command patterns.
English
2
1
4
594
Rust Bytes 🦀
Rust Bytes 🦀@rustaceans_rs·
Do you believe Trait bounds are where your architecture quietly reveals itself?
English
2
0
10
1.5K