System is experiencing heavy traffic. Sitting for a few hours, will it fix up?
Jules: An asynchronous coding agent
241–245 of 245 posts
Re: Jules: An asynchronous coding agent
#242Does anyone remember sweep.dev? It had exactly the same core features as Jules when it first launched — asynchronous coding, github integration, etc. — but now it's become a JetBrains Copilot plugin."
Re: Jules: An asynchronous coding agent
#243Earlier quoted context omitted.
Is the code available?
I had not thought about sharing it. I rolled my own framework, even though there are several good choices. I'd have to tidy it up, but would consider it if a few people ask. Shoot me an email, info in my profile. The more difficult part which I won't share was aggregating data from various systems with ETL scripts into a new db that I generate various views with, to look at the data by channel, timescale, price regim…
The framework is now available on Github:
https://github.com/jacobsparts/agentlib
I'm planning to write a blog post about the larger system when I get the chance.
Re: Jules: An asynchronous coding agent
#244Earlier quoted context omitted.
Shhhh... don't tell the plebes what it really means to "2x their productivity". Seriously though, this kind of tech-assisted work output improvement has happened many times in the past, and by now we should all have been working 4-hour weeks, but we all know how it has actually worked out.
Hell, when the industorial revolution happened, working hours increased , not decrease. And especially with electricity, Factory owners forced workers to work deep into the night. A constant 16-hour shift was the norm, so much that it requires legal intervention [1] > In 1833, the Factory Act banned children under 9 from working in the textile industry, and the working hours of 10-13 year olds was limited to 48 hours…
not sure if you will still see this 7 days later, but the claim "we work more hours than medieval peasants did" jumped out at me so i looked into a bit and am curious if you have more thoughts on it!
i found this lively criticism of the video on reddit: https://old.reddit.com/r/badhistory/comments/16y233q/histori....
my brief takeaway was that the claim might be true if "work" means "working for an employer for wages", but not if "work" includes "necessary labor for shelter, food, clothing, survival".
but it's an interesting thought though so i'm curious if you have other related resources to dig into.
Re: Jules: An asynchronous coding agent
#245Earlier quoted context omitted.
The same was true with the aristocrats of centuries past: the capitalists who run our modern economy were once nothing more than their managers, delegates who handled the estates, their investments, their finances, growing power until they could dictate policy to their 'sovereign' and eventually dispose of them entirely.
The nobility used to be the dedicated warrior class, the knights. This secured their position in the society and allowed them to rule, by coercion when needed. Once they ceased to exercise their military might, some time around 17th-18th century, and chose to live off the rent on their estates, their power became more and more nominal. It either slipped (or was yanked) from their hands, or they turned capitalists the…
The problem is your timeline: in actuality, the nobility of Western Europe lost their independent armies by the 15th century, solidly by the 16th, and thereafter held on to a military role only through participation (as officers) in the state-run standing armies that developed thereafter. Yet for centuries they held on to power: in France, until the revolution, and in Britain, until well into the 19th century. Great read on the topic: https://projects.panickssery.com/docs/allen-2009-a_theory_of...
"Living off of the rent of their estates" was enough to remain in control of the state for centuries. Only the birth of capitalism and thereafter the industrial revolution allowed for other actors -- the bourgeoisie -- to overtake the aristocrats economically.