469 karma · joined November 28, 2020
I usually follow Divio’s documentation to reference explanations and references, but it is not suitable for a blog post
I genuinely think that multi-agent is a probable future to enable coding at the scale of a big corporation.
I agree and I did not see it work yet, but the trial were most likely on small scale where it is simply over engineering.
(Btw : I do not sell tokens. I I think distributed the work through agents in a plateform is a way to control costs by optimizing specialised agents)
Just a toy, and very incomplete, but hopefully useful.
I wanted to try to implement this for months. You did a really good job.
I welcome the Hacker News community to share their insights and experiences with this model. Do you find it useful in your work? What aspects resonate most with you, and what improvements or alternatives would you suggest?
I hope that it will be useful.
In the data mesh, we mark the difference between an operational data (a representation of a state) and an analytical data which have (at least) one temporal dimension.
I did not insist on this in the article because that was not the point.
What you mention is right, it is very difficult to find incentive to get operational data. It is not the same in the analytical world. At its core, data mesh is a paradigm that applies to the analytical world.
I've written an article narrating my recent endeavor with goMarkableStream, a tool I crafted to bridge gesture inputs from a reMarkable tablet to a web browser for seamless interactive presentations. This exploration led me down a path where the Unix philosophy and the Go language became pivotal elements.
Key highlights of the article:
A deep dive into using WebSockets versus HTTP for conveying gestures from a device to a browser, highlighting the trade-offs and practical considerations. An illustration of Unix's enduring principle, "everything is a file," in action - capturing touch events in a Linux-based environment and the strategic choice of Go for its simplicity and robustness. The issues and thought to design a bespoke messaging system over HTTP, moving away from the intricate layers of third-party libraries, in favor of a more transparent, hands-on approach. I try to place some reflections on the journey of tackling complexity with simplicity, echoing Rob Pike’s wisdom: “a little copying is better than a little dependency.”
hope you will enjoy the post