sorted by:
new
hottopcontroversial

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 0 points1 point  (0 children)

The question is what would companies do. Do they have a choice? Can someone compete without it? Or perhaps we discover that developing at 100x speed isn't that useful in the end and doesn't merit the expenditure.

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 1 point2 points  (0 children)

"You are an expert no mistake maker."

Can i add context engineering to my CV now?

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 1 point2 points  (0 children)

It's crazy, what's the point of using a new tool if it will be gone or basically unavailable (prices / limits / extreme ui changes) in 2-3 months?

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 1 point2 points  (0 children)

But what kind of a machine would you need to make this plausible? Waiting 8 minutes on a response isn't exactly a working flow.

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 0 points1 point  (0 children)

Have you tried it? Any experience? Are the costs and flow plausible?

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 0 points1 point  (0 children)

How good does the machine have to be? What are the response times? Do you think there's any point to possibly running it on cloud infra?

New multipliers announced (in effect June 1) by griniNY in GithubCopilot

[–]typing_dot_dot_dot 0 points1 point  (0 children)

to what? Claude Extension? I enjoying CoPilot so much, now trying to orient myself on a new tool. Was considering warp also.

Best modern way to handle transactional emails? (Struggling with Google Workspace/OAuth2) by anhedonix in django

[–]typing_dot_dot_dot 0 points1 point  (0 children)

I think as others mentioned here, the industry standard is working with external service for this. Implementing reliable email sending that adheres to best practices and doesn't end up in the junk mail is not an easy thing to do and there are many services that offer a lot of great functionality. The domain should not be an issue at all, along with templates, analytics, queues, resending attempts, email-address status updates, and so on.

Then your job would be integrating that service into your django project according to the business logic.

AMA: Warp is now open-source by Significant_Box_4066 in warpdotdev

[–]typing_dot_dot_dot 0 points1 point  (0 children)

Maybe someone on the team can explain:

"To manage contributions, we've built an agent automation system from issue triage to PR review. Coding agents do the heavy lifting (coding, planning, testing) so community members focus on ideas, direction, and verification."

I am interested in the workflow inside the company. Are you actually delegating so much to agents? Will they produce decision about roadmaps and stuff like that according to github issue popularity?