Oh yeah, of course. You can’t just trust it 100%. One time Claude gave me a piece of code that was a nasty bug that could have caused some serious issues. It was a one liner that deleted an employee from database by mere searching said employee with their name. Thankfully I caught it in the dev environment before it got into prod (assuming AQ missed it, too) and started deleting people. lol.
- 0 Posts
- 82 Comments
Damn, sounds like it could do some wonders.
Nah, I’m good the way I do things. I have a good pace that has been working out very well for me :)
I don’t mess with any of those in-IDE assistants. I find them very intrusive and they make me less efficient. So many suggestions pop up and I don’t like that, and like you said, I get confused. The only time I thought one of them (codium) was somewhat useful is when I asked it to make tests for the file I was on. It did get all the positive tests correct, but all the negative ones wrong. Lol. So, I naturally default to the AI in the browser.
I don’t even know what aider is. Lol. There are so many assistants out there. My company created a wrapper for chatgpt and gave us unlimited number of tokens and told us to go ham.
Lmao. I don’t give a shit. I’ve been saving a ton of time ever since I started using it. It gobbles up CSS, HTML and JS like hotcakes, and I’m very much ok with that.
I’m telling you. It’s fantastic for the boring and repetitive garbage. Databases? Oh hell yeah, it does really well on that, too. You have no idea how much I hate working with SQL. The ONLY thing it still struggles with so far is negative tests. For some reason, every single AI I’ve ever tried did good on positive tests, but just plain bad in the negative ones.
If you know what you’re doing, AI is actually a massive help. You can make it do all the repetitive shit for you. You can also have it write the code and you either clean it or take the pieces that works for you. It saves soooooo much time and I freaking love it.
penquin@lemm.eeto Open Source@lemmy.ml•Open source maintainers are feeling the squeeze21·5 months agoIt’s socialism and it is very much ok when it’s for a corporation/bank/billionaire bailout/handout, and “OH THE COMMUNISM AND SKY IS FALLING AND WE ARE DOOMED AND LIFE IS ABOUT TO End” when it’s something that helps people.
penquin@lemm.eeto Open Source@lemmy.ml•Open source maintainers are feeling the squeeze82·5 months agoAre you looking for a literal apocalypse? Are you like insane or something? 😂
penquin@lemm.eeto Open Source@lemmy.ml•Open source maintainers are feeling the squeeze36·5 months agoGod damn. I came here to say something, but I don’t think it would’ve been even close to this, let alone better. Thank you.
Just found that out the hard way on the job the other day. Asked my sr dev if there is documentation of an API we were supposed to work on, he just laughed. I got the hint. Lmao
penquin@lemm.eeto Technology@beehaw.org•Amazon pumps additional $4Bn in AI Start-up Anthropic4·8 months agoHopefully that will change that ridiculous message limit for the better. I really like Claude, but I hate the limit.
It feels the same when chatGPT starts giving you some random shit that has nothing to do with the code you have
I’m pretty it has been forked to the moon and back before he went insane.
penquin@lemm.eeto Open Source@lemmy.ml•Open Source Everything: A curated list of the best open source software13·10 months agoThanks for this
100%. I try to keep working through them and only participate when my name is called.
Yup, and getting older makes it harder to catch up to that damn train of thoughts after that useless ass meeting interrupted them.
Yes, software, and specifically C# unit tests in my case. Positive unit tests check if the code works as expected when given valid inputs. They confirm that the function or module behaves correctly under normal conditions. Negative unit tests check how the code handles invalid or unexpected inputs. They ensure that errors are properly caught, exceptions are handled, and the system doesn’t break when things go wrong.
As for examples, it’s just the LLMs I have tried never wrote negative tests that actually worked. If you use Visual Studio, you’re probably familiar with those check marks that it has on unit tests. Those become green check marks when the test is valid, red X when it is invalid (isn’t correct). The negative tests from LLMs always have red X’s. Hope this makes sense.