{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigxxd4qcf7oynmmpaszoewzxalzqu7jp2pngz2rk2acydukbiqk2q",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mnwsgwznnjr2"
  },
  "path": "/t/vibecoding-is-it-changing-how-we-build-software/1383278#post_1",
  "publishedAt": "2026-06-10T12:21:29.000Z",
  "site": "https://community.openai.com",
  "textContent": "Hey everyone\n\nThis is my first post here, so I wanted to start with something I’ve been thinking about a lot lately , _vibecoding_.\n\nIt feels like we’re entering a phase where coding is less about writing everything line by line, and more about describing intent, experimenting fast, and letting AI help shape the implementation.\n\nBut I’m still trying to understand where this is really heading.\n\n  * Is vibecoding actually making developers more productive?\n  * Or are we just shifting complexity from code → prompt design?\n  * And what happens to core engineering skills in the long run?\n\n\n\nFrom what I’ve seen, it’s exciting but also a bit confusing. Sometimes it feels like you can build 10x faster… but then debugging and understanding what’s happening under the hood becomes its own challenge.\n\nCurious how others here see it:\nAre you using vibecoding in your workflow already? And do you think it’s the future of building software or just a phase we’re in?\n\nWould love to hear your thoughts",
  "title": "Vibecoding Is it changing how we build software?"
}