Hacker News new | past | comments | ask | show | jobs | submit
To clarify, it was Github Co-pilot so was in their IDE - not a generic MS Co-pilot.

They limit all developer to $100/month (maybe it was $150) budget too.

Their "coding with AI" was prompts like "implement this function" where they write the function header.

It's actually shocking to see people still working like that.

I always find it fascinating to see this out in the wild. I work from coworking spaces, so I’m constantly around developers from companies of all sizes, and the difference is striking.

Some of us have moved away from IDEs and writing code entirely and work terminal-first, while others still use agents the way I did two years ago.

For example, I recently watched someone in an actual code file adding Python import statements by waiting for Copilot’s inline suggestion to kick in. It was such a bizarre thing to witness. That’s not because of the person (I don’t want to judge anyone’s way of working; if someone enjoys writing code, that’s fine by me). It’s because I remember doing exactly that years ago, and since then I’ve stopped writing code altogether.

I even remembered that I had built an extension back then, because Copilot folks never added a quick opt-out or silent mode to Copilot inline suggestions[1].

It’s strange how fast everything has changed.

[1]: https://marketplace.visualstudio.com/items?itemName=Bubulus....

Yeah it's weird.

I interviewed for a role a month or so back and they were "look we use AI for everything but we want to see you code. You can use AI autocomplete though" and I had to download Cursor and turn on that mode. It was weird remembering how to do it!

And profit lines have stayed pretty much stable in the last few years for most companies.
I can assure you that in the places closest to AI coding this is absolutely not the case.

But people underestimate the overhead in converting code into money, and that overhead hasn't been eaten into as much by AI yet.

loading story #50573710