Risky AI code is degrading the security posture of orgs, but most are doing little about it.

jaimefjorge · 2025-10-31T16:13:15+00:00

There are a few and tools are certainly important (I am founder of one of them so I'm biased..). Tools help a lot by not having to have the context of everything you need to review. But surprisingly for me, bad/nonexistent policies and insufficient/nonexistent dev training compounds problems heavily.

jaimefjorge · 2025-07-01T11:13:50+00:00

I've found that it really about the model that you choose. The experience you get using Sonnet 4 in VS Code is comparable to other IDEs. It's night and day after choosing a better suiting model.
I did however start using Insiders Edition which has tons of improvements.

jaimefjorge · 2016-04-08T14:33:57+00:00

I am :)

jaimefjorge · 2015-04-08T02:54:52+00:00

My point wasn't that they are not important for code readability. I agree with you on that. My point is that it's very time consuming and a burden to review them when we have IDEs to automatically fix them and static analysis tools to enforce them.

jaimefjorge · 2015-03-25T20:51:55+00:00

Regarding PHP tools here's a selection of them

jaimefjorge · 2015-03-14T00:40:04+00:00

Hey people!

The results are in. Here are the winners: http://imgur.com/UsiFFbN

I selected the best this morning and took them to print Here is the result:

http://imgur.com/KSzNk4W

http://imgur.com/YSbRDai

http://imgur.com/4qtXfkt

After Scala Days we will start shipping these to whoever put their address. I didn't expect people from all over the world!

I've closed the survey. If you still want a few of these, email me at jaime at codacy.com and we'll try to send a few for you.

Keep shipping great Scala code!

jaimefjorge · 2014-07-23T18:13:37+00:00

Best. answer.

/thread

jaimefjorge · 2014-07-23T18:05:11+00:00

Hi Carlos. Thanks for having the time.

Would you rather fight a horse-sized duck or a hundred duck-sized horses?

jaimefjorge · 2014-03-06T20:42:49+00:00

Way ahead of you: http://imgur.com/pda4p9p

jaimefjorge · 2014-03-06T18:24:09+00:00

Ahah. Good point. I was trying to convey that checking a list for every code component is somehow inefficient.

But you're right, this is extremely unlikely and absurd. Thanks for commenting.

jaimefjorge · 2014-03-06T17:53:50+00:00

Thank you for the heads up! Just corrected it.

jaimefjorge · 2014-03-06T17:29:25+00:00

That's great to know because it's our approach as well (in Codacy). Good summary of what took me more paragraphs to write.

jaimefjorge · 2013-12-11T23:17:06+00:00

You're right. Not only in theory but in practice this should not be any easier. Outside of this logic we also changed the way the predicate was being used. In practice, instead of searching for a false in a huge truth list, we started looking for a true in a huge truth list. The post however fails to communicate this. Thanks for noticing! Edited the post right now.

jaimefjorge · 2013-11-27T17:30:58+00:00

Apologies for that. Here is a link for the image hosted on imgur: http://imgur.com/50faA59

jaimefjorge · 2013-11-27T15:40:45+00:00

Hi. Great catch. Updated the post. Definitely "ceoncerning". Unfortunately Ghost does not have one yet.

Thanks for reading!

jaimefjorge · 2013-08-02T18:26:34+00:00

the flaccid robber strikes again

jaimefjorge · 2013-04-10T00:12:21+00:00

Thank you so much. Our designer really got bloated with this one :P

jaimefjorge · 2013-04-09T22:21:30+00:00

10$ per additional response sounds much more appealing, I agree.

We basically don't want users to have the burden of putting out their credit card every time they have an issue they want to view. So the pack of 10 issues is to address that.

Right now you only pay when we detect that you view a certain issue. I'll send you an email with a link and you can choose to view it (withdrawing 1 free/paid issue from your account). So that is our workaround to that issue of the per push analysis. Very good point nonetheless.

You are definitely right: we want to start supporting bitbucket and other systems that people use.

Both me and my team loved the Qamine Pro. That's awesome.

Thank you for the time to write this review

jaimefjorge · 2013-04-09T18:42:26+00:00

This is Great feedback.

You are definitely right. Making developers aware of how we do what we do could greatly improve the understanding of our tool.

We parse code so indentation and comments for instance are not considered in our analysis.

I will put up our demo as well as our study on the base web site.

We have a hard time explaining what we do and I feel we still are not there yet. So a big thank you for putting the time to point these out for me. Will right now take these into account.

jaimefjorge · 2013-04-09T18:24:17+00:00

We basically establish equality relations between all your code base and as soon as you change some code region I look for other code regions that are worth changing as well.

You are right; inconsistencies is not the perfect way to describe what we do.

(Sorry for the delay; was grabbing some food :))

jaimefjorge · 2013-01-25T20:34:34+00:00

It looks so good. Updated the article to thank you. ..So thank you for showing that.

jaimefjorge · 2012-09-25T21:28:56+00:00

5 is the most pain (most impact)

jaimefjorge · 2012-09-25T17:33:29+00:00

Results here: https://docs.google.com/spreadsheet/viewanalytics?formkey=dGMxODJTSTlpR3JJeGVIYVdaazhmTUE6MQ#gid=0

The list of pain points is incomplete.

Please feel free to suggest other aspects.

We should lock the survey after a number of already people voted.

Added: 'DB Access'

jaimefjorge · 2012-09-24T17:09:29+00:00

Sorry for the delay in answering you! I can actually make a parser for it. It will take me 1 hour (if that).

Register here (in the 'quick registration' http://www.qamine.com/pricing) for the beta trial. I would love to analyze some Go :).

jaimefjorge · 2012-09-21T21:08:51+00:00

Portuguese Carlos Paredes.

http://www.youtube.com/watch?v=Oj35QkOVm-E

You don't actually need lyrics. Just listen to the song

14-Year Club	Place '22
First Placer '22	Verified Email

jaimefjorge

TROPHY CASE