munch-o-man
Joined 8 months ago
Joined 8 months ago
What is our rush to give up our own thinking?
Also, fuck them, just because they are on the books for an amount of money equal to the GDP of New Zealand doesn't mean I want to pay it off for them with my taxes.
They spend more time trying to figure out how to put more agents into their "process" and solve any problems it creates with more agents than just doing a general claude run and tweaking it themselves with the skills they built over their career ostensibly.
Cracks me up watching engineers completely degrade themselves by saying that a "team" of "agents" should just be let loose on a task and create 10,000+ line PRs that no human will ever read, then deploy it to production and run code no human has seen or understands....like, stop degrading yourself to prop up these companies bleeding money....it is a tool, it is powerful, it isn't an engineer though and you are, it isn't smart and you are, don't intentionally argue for your own replacement by a fucking corporate chatbot.
If I had to work at a company that thought they could do software that way I would refuse to join the on-call rotation....if that fucking shit is so much better than me that we need to rush un-reviewed shit to production then I'm sure it is also so much better than me and it can manage oncall for nights and weekends at least...unassisted. Watch how many of these zealots change their tune when you tell them they should hand over on-call 24/7 in production to bots and not even put people in a pager rotation or page them. Suddenly real people are needed to fix the software we were too stupid to write but the bot - that did write it - is too fucking stupid to manage?
make it make sense.
You can get massive productivity increases with these tools while still using manual-mode only, reading the code as it is generated via the diffs, yell at it when it does boneheaded shit (which it 100% will), and doing narrow-scoped tickets/PRs that are reviewable by a human being just like in the before times. What is the need to go faster than that and essentially just tie the entire product of your company to what some other company's bot chooses to shit out to you that day?
For example...in the key of aminor when you make the five chord major to create a resolution back to i (aminor) you raise the 7th scale degree. That means the G becomes G#...Ab is the same pitch but writing it that way is wrong. An EMajor chord is spelled E G# B, not E Ab B. Now if you spell that as 9 0 4 you have stripped all context out of the music. Musicians aren't just player pianos, they analyze the harmonic structure of the music the inform phrasing, shape, tone, volume, and pacing (acelarando, decelerando, ritardando, etc).
Whenever I see something like this trying to reinvent standard notation I feel like it is usually from somebody who can kind of play an instrument but can't read music or can't read it well because they haven't put the years of work it takes to be a proficient sight reader and they haven't studied harmony/music-theory.
One of the most important things about musical standard notation is that it is - standard - you can hand it to any musician on any instrument and they can make sense of it quickly. It is a skill that takes a lot of practice but it is what allows musicians who have never met each other to be hired for a gig and show up and play together without ever rehearsing.
This approach won't teach you to "see" music either. It forces pure mechanical number memory....you won't see harmony and be able to quickly notice that - for example - a line is just moving the chord up in inversions and since you know harmony and your chords you can sight read that part without ever even reading every individual note.
But still a cool idea from a hobby perspective.
Nobody here is going to run this blackbox-with-a-sales-pitch that - hilariously - STILL doesn't say what this thing supposedly does in any meaningful way that implies it's creator had any understanding what they were creating. Your demo video is a hilarious context-free explosion of chinese and then seemingly just scrolling the README in the github repo with no code in it that you linked.
To top off the audacity of your blackbox that requires access to every aspect of the computer to do [stuff]....you actually are trying to charge money for it. You are an anonymous blackbox wanting access to every part of my computer and I still have to bring my own agent that I pay for to do all the work on top of paying for your ransomware. What exactly are you offering other than moving my mouse and trying to steal my identity?
If you want an evaluation then post the code.
Great for homelabbers who want to take all the always-free tier s3/blob allotments and combine them together and lock them to the free tier quota to make sure you never incur costs. The compression also helps get as much as possible for free.
Great for zero-downtime cloud migrations.
Great to ensure data exists in multiple clouds when written with no complex scheduled tooling shit.
Pair a cloud backend with your local minio/seaweedfs/whatever and set replication factor to 2. Every object will instantly live in the cloud and on your local minio....if you local minio goes down applications will keep working because s3-orchestrator will fail over the reads to the cloud backend...when minio comes back it will make sure all data matches replication factor.
Would love more people to try using it and see what doesn't work or isn't ideal so I can continue improving it....my own use cases aren't going to expose to me everything somebody else might use it for. Also gh issues and PRs are very very welcome...just want to keep improving it.
Just point your applications/clients at s3-orchestrator instead of directly at a real s3 backend...clients don't have to know anything about s3-orchestrator or how it is actually managing the data.
Also, I setup a slightly better auth system for it recently and built a terraform/opentofu provider for handling users/virtual-buckets/permissions published to both public registries.
It also includes a little cloudflare worker that can be utilized to further eliminate costs for backends that are part of the cloudflare data alliance and egress on them routed through cloudflare is free.
shitty project webiste: https://s3-orchestrator.munchbox.cc
Thats just me though...it is more about visual appearance and helping me quickly see the logical breakdown/structure of a file so I can get to the code I want quicker.
I'll try to read through it later, but props to anybody building a project in C...I need to come up with a new pet project in C because I'm so rusty I don't think I've written C in like 7+ years.
I must be using claude wrong....I never run out of quota.
I'm genuinely curious what you are doing that would eat your quota that fast because that sounds legitimately insane.