91–100 of 105 posts
At least 20% of code must be AI generated with the goal of at least 80% by the end of the year. CEO declared that vibe coders create better solutions because they are “goal oriented” as opposed to traditional coders that are “process oriented”.
The same CEO will have a meltdown over the bugs in an unmanageable codebase next year. Fun times ahead :)
Using Gemini Pro. No, I adopted it all on my own, but work pays. I love it, even though I can't use it on everything. Most developers here are using it, with approval on a per-projext basis. Lately it's taken over code reviews, for myself and when I review other people's code. Extremely helpful. It's made software development fun again.
The division I worked in was demanding that developers use AI at least once a week and they were tracking people's usage. The boss nagged about it every day.
I had no problem meeting the requirement but did find it's contributions to be very hit or miss as to usefulness.
Using Gemini Pro. No, I adopted it all on my own, but work pays. I love it, even though I can't use it on everything. Most developers here are using it, with approval on a per-projext basis. Lately it's taken over code reviews, for myself and when I review other people's code. Extremely helpful. It's made software development fun again.
Wait. You don’t review code any longer? Are you sure that’s wise? Or is that not what you mean?
No. My employer released their official AI policy not long ago, and it codifies what has been their unofficial policy for a while now: you can use it if you want to, but you'll have to pay for it out of your own pocket.
Not forced but the tooling has been made available to those who ask. Work have provided Microsoft Copilot through Teams and Github Copilot through my IDE of choice. I found the Microsoft Copilot to be reasonably good when given a complete context with extremely limited scope such as being provided a WSDL for a SOAP service and asked to write functions that make calls and then writing unit tests for the whole thing. T…
I'd never thought about LLM failure modes like this, but it makes sense.
Cross too many possibility streams, instead of prompting / contexting down to one, and it vacillates between them and outputs garbage.
I'm no longer at the company but yesterday was my last day so my information is still current. The division I worked in was demanding that developers use AI at least once a week and they were tracking people's usage. The boss nagged about it every day. I had no problem meeting the requirement but did find it's contributions to be very hit or miss as to usefulness.
It's really interesting to see the extreme contrast between the constant praise of AI coding tools here on HN vs the actual real world performance as seen recently on public Microsoft repos, where it utterly fails at even the most basic tasks.