codeinabox

joined 5 months ago
MODERATOR OF
 

AI-assisted development is already a reality, and the open source community is coming together to figure out how to manage it.

Many major projects and organizations now agree on a few key ideas: people must stay accountable, being open builds trust, and existing contribution rules like the Developer Certificate of Origin (DCO) still matter. The Linux kernel community, Red Hat’s legal team, and the OpenJS Foundation have all come to similar conclusions. AI can help with development, but people are still responsible for what they submit.

[–] codeinabox@programming.dev 2 points 4 weeks ago

Check against Can I Use, all of the APIs, except for the following are supported by major browsers:

[–] codeinabox@programming.dev 5 points 1 month ago (1 children)

The fact that people even bring javascript as the backend is a bit crazy to me.

To clarify do you mean replacing JavaScript just on the backend? This article is about using JavaScript on the front end.

[–] codeinabox@programming.dev 2 points 1 month ago (3 children)

I'm intrigued, what would you replace it with?

[–] codeinabox@programming.dev 1 points 1 month ago (1 children)

What are your thoughts on this 2023 comparison?

[–] codeinabox@programming.dev 0 points 1 month ago

So to confirm, you don't trust blogs where the company is selling a product or service, even if they don't mention it in the article? If so, that would cover a lot of articles shared on this instance.

[–] codeinabox@programming.dev -1 points 1 month ago (3 children)

For what? I don't see any products or services being promoted in this article.

[–] codeinabox@programming.dev 0 points 1 month ago (1 children)

People who care about performance are using loops

Well that depends, generators are faster than loops when you're using Bun or Node.

[–] codeinabox@programming.dev 1 points 1 month ago

The conclusion aligns with my own belief, which is that it's better to create a minimal context by hand than get agents to create it:

We find that all context files consistently increase the number of steps required to complete tasks. LLM-generated context files have a marginal negative effect on task success rates, while developer-written ones provide a marginal performance gain.

When I have got Claude to create a context, it's been overly verbose, and that also costs tokens.

[–] codeinabox@programming.dev 1 points 1 month ago

However in this case the opposite is true, as Chromium currently doesn't support this feature.

[–] codeinabox@programming.dev 2 points 1 month ago (2 children)

Do you mean features only currently available in Chrome?

[–] codeinabox@programming.dev 1 points 1 month ago (4 children)

Well spotted, the article states:

The :heading pseudo-class is currently available in nightly builds only. You can test it now in:

  • Firefox Nightly (behind a flag)
  • Safari Technology Preview
[–] codeinabox@programming.dev 4 points 1 month ago

There are some really good tips on delivery and best practice, in summary:

Speed comes from making the safe thing easy, not from being brave about doing dangerous things.

Fast teams have:

  • Feature flags so they can turn things off instantly
  • Monitoring that actually tells them when something’s wrong
  • Rollback procedures they’ve practiced
  • Small changes that are easy to understand when they break

Slow teams are stuck because every deploy feels risky. And it is risky, because they don’t have the safety nets.

view more: ‹ prev next ›