[deleted]
Jules, remote coding agent from Google Labs, announces API
71–80 of 81 posts
Re: Jules, remote coding agent from Google Labs, announces API
#72[deleted]
[deleted]
Re: Jules, remote coding agent from Google Labs, announces API
#73I have an old Django site I'm maintaining for a long-time customer of mine. They often want to make small changes - things that are only a few lines of code, but would take an hour to just spin up the system, remind myself how it works, commit, push, update the server and all that. Last week I've moved the whole infrastructure to Railway, and taught the customer to use Jules. They make their own PRs now, and Railway…
Do they still pay you the same amount?
They've always paid me per hour. The fewer hours, the better for me: just like the sibling post, I'm also not in it for the money. I care for both the customer and the project, and I'm happy that we've found a way to get the development going again with really minimal effort from my side.
Re: Jules, remote coding agent from Google Labs, announces API
#74I have an old Django site I'm maintaining for a long-time customer of mine. They often want to make small changes - things that are only a few lines of code, but would take an hour to just spin up the system, remind myself how it works, commit, push, update the server and all that. Last week I've moved the whole infrastructure to Railway, and taught the customer to use Jules. They make their own PRs now, and Railway…
How do you handle the customer database? Do you push this in its entirety to the VM?
No, Jules was able to usually edit the code blind and get things working. If they didn't, the customer saw it on the automatic environment created for the PR, told Jules and Jules fixed it. I think I saw one task or maybe two in which Jules actually ran the HTTP server, set up Postgres, ran all the migrations and created a superuser, only to then write some Playwright code that it used to login and take some screenshots.
In other words, so far it didn't feel like including a database will provide us with much, but I am playing with the idea of creating a tiny mock database and including it in the repo, as the real database is around 15GB and contains passwords and names.
Re: Jules, remote coding agent from Google Labs, announces API
#75I have an old Django site I'm maintaining for a long-time customer of mine. They often want to make small changes - things that are only a few lines of code, but would take an hour to just spin up the system, remind myself how it works, commit, push, update the server and all that. Last week I've moved the whole infrastructure to Railway, and taught the customer to use Jules. They make their own PRs now, and Railway…
That's honestly incredibly cool, could I perhaps encourage you to write a blog about the details with some examples on what the PR requests from your customer looks like.
That's an interesting idea! It's been just a little bit over a week now that we're doing it, but maybe by the end of the month I'll have some more conclusions to share.
Re: Jules, remote coding agent from Google Labs, announces API
#76I am so sick of these anthropomorphized names that have nothing to do with anything that we’re all supposed to remember now. Why are we giving products first names? The worst offender is probably Amazon Rufus. It’s all so dumb and I hate it. At least attempt to be clever and name it something that relates to the product itself. Even Google Wave, despite its shortcomings, made sense as a product name.
I assumed the Jules name was at least partially inspired by Jenkins.
I always thought of the character from Euphoria
Re: Jules, remote coding agent from Google Labs, announces API
#77Headline makes it sound like the AI itself gained sentience and made an announcement.
Re: Jules, remote coding agent from Google Labs, announces API
#78Do people really find Jules useful? I find it needs babysitting much more than Cursor.
Re: Jules, remote coding agent from Google Labs, announces API
#79Earlier quoted context omitted.
Why? In 3 years time this won't be how these tools work. So it feels like you're saying we should invest time in something that doesn't work and will be redundant in 6 months. Worse, your example is one that AI agents are notoriously bad at. Give them an error like that and they're more liable to break the existing functionality to fix it, after littering the code with tons of log statements. When most of the time th…
And in five years time all human engineers will be replaced. Why not just quit now?
You misunderstood, there's no point learning it until it works. Don't bother until it's stable, picking up agentic coding will be trivial, because it has to be trivial to work well.
To get agentic coding working 9 months ago you were massaging context, 6 months ago you'd be hooking up MCP servers, 3 months ago you'd be writing a gazillion .claude files.
But all of that is utterly useless knowledge. That's not a transferrable skill.
Using AI is much more effective if you write the code yourself, using AI as a supercharged Stack Overflow.
A programmer + AI supercharged SO > A programmer + agentic coding
So stop wasting your time learning how to get agentic coding working today, especially as the method keeps changing. There's no point learning the voodoo and rain-dancing of this iteration of today's coding agents. Try them, and until they work, discard them.
Re: Jules, remote coding agent from Google Labs, announces API
#80Would anyone at Google be willing to tell me how many people are working on this project? I’ve been building something functionally similar for my employer, but it’s a nights and weekends project with only one contributor (me).
Why would you build something for your employer in your personal time? You're literally putting your own money in the shareholders pockets.
Social currency, I guess. I work on the AI team, so it’s just part of the job.