Recent submissions

Comment · 20 days ago
If I am not wrong, orgs build vs buy for the most part is NOT impacted by AI cycle.

For the most part business care about, is this our core capability OR not?? If core, yes build is what preferred. If not, buy is preferred. Where few occasions they deviate from this due to, to be frank non-technical reasons.

In Software world, building is not the costly, maintaining it is - and this cycle of AI developed software is NOT proven yet. So, so far my understanding is nothing changed in that area.

Comment · 20 days ago
Curious - if you measured any quality side of this? not just PRs and velocity. Some of the tradeoffs like Github are not really related to AI capabilities, isn't it?
Comment · 24 days ago
Interesting idea. Did you run any comparison analysis between dockerized vs brewlet??

Curious about what motivated you to pursue this approach.

Comment · 25 days ago
This slop is one of the very frustrating experiences with AI. To address this, I had to set a global rule - Results summarized max 5 sentences, expand only if asked.
Comment · 25 days ago
depproof | Part-time B2B Sales Lead | REMOTE (US) | Part-time | Equity + commission | https://depproof.com

Most of the code a team ships is third-party, and scanners flag hundreds of vulnerabilities in it. depproof tells you which few attackers are actually exploiting, so you fix those first. It runs inside your own environment, and your code never leaves.

We're a small, founder-led company looking for a part-time sales lead who has sold to security or engineering teams: running first conversations, shaping the pitch, and closing our first customers.

You may reach out to me at: prasadv at depproof.com

Comment · 26 days ago
This is great writeup, can we do a cross comparison with "human" experts?? whether models perform better OR worse??
Comment · 27 days ago
The tools were sold on speed and quality, and they deliver both.

I think "quality" side depends on LOT of tuning you would need to keep in place. Quality might be good if you are dealing with single project, when you hare more than one repo to deal with, things need real attention and observed that quality goes down significantly.

Comment · 1 month ago
The ongoing theme of all these responses was shifting the blame to the consumer.

As expected. I think consumers also need to push back on these practices, but the problem is, majority of consumers are tech savy but not privacy savy.

Comment · 1 month ago
Reducing the number of clicks doesn’t necessarily improve interaction.

I think this is half true and depends on you are dealing with vetrans or new users. Once you are used, people just click as many as needed, but when user is new to the UI, every click becomes a question and resistance.

Comment · 1 month ago
If you are upcoming developer, nothing wrong in vibe coding in my opinion as long as you take time to understand what is being done by the model. One suggestion I have is, make sure ask/explore alternative approach of solving the same. This helps you to understand and eventually judge what fits in given scenario. Good luck!
Comment · 1 month ago
Make sense, most of the consumers/users of this tech not much into privacy, like any other gadgets at home.
Comment · 1 month ago
Correct, that is what confused me, how SBOM came into the picture, now got it, thanks!
Comment · 1 month ago
This is unfortunately becoming latest theme. Get the credentials one or otherway from maintainer and use it to distribute the malware.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton