I had this idea over 10 years ago but never finished it. I hope this takes off. I do fear it's not very practical for many big pieces of legislation which are often written in secret.
Transparency has a cost. There are several good reasons, but my favorite is intellectual freedom. Policy makers would be much less likely to explore bold reforms or risky bipartisan compromises if their draft quality notes and correspondences were publicly tied to their political reputation. It takes significant work to produce successful legislation, and much of that work can be productively and safely done without direct public oversight. This is the same reason an individual might value a private journal.
If you have a problem with your representative’s behavior, call their office and ask about it. They will certainly have a reason. Tell them if you disagree, and vote when you can.
> Policy makers would be much less likely to explore bold reforms or risky bipartisan compromises if their draft quality notes and correspondences were publicly tied to their political reputation.
Only if those bold reforms weren't in the interests of the people they serve. Risky bipartisan compromises should still be transparent along with what was gained in exchange for them. If the people feel that the compromise wasn't worth it they should be empowered to vote accordingly come election time. It's the job of representatives to assure the people who elected them that they are doing a good job and if they can't do that they deserve to lose their position. Refusing to support bold reforms that the people they represent want, or refusing to compromise when it would be beneficial to voters would become just as costly to their career.
> It takes significant work to produce successful legislation, and much of that work can be productively and safely done without direct public oversight.
Often most of that work is done entirely for them by corporations and lobbying groups and "law makers" just vote how they are paid to vote without even reading the bill put before them. Just because something can be done in secrecy doesn't make that the ideal way to do it. We've have extremely poor results with the system as it stands right now, so a change to introduce more transparency and accountability seems like a very good idea.
> This is the same reason an individual might value a private journal.
A public servant representing the people by making edits to laws and performing the duties they were elected to carry out is nothing at all like someone keeping a private journal. Their work is not their personal affairs, it is the public's affairs. How that work is being done matters to the public. Legislators would still remain free to go home at the end of the day and write in their private diary all they like.
> If you have a problem with your representative’s behavior, call their office and ask about it.
When their behavior is conducted in secrecy behind closed doors the public doesn't have the ability to hold them accountable for it, which is exactly why it takes place in secrecy. Increasing the public's ability to hold elected officials accountable by increasing transparency can only improve outcomes for voters, and it would certainty be inconvenient for elected officials who want to put their own interests above the interests of the people who elected them.
> Only if those bold reforms weren't in the interests of the people they serve.
This is my point exactly: the creative process is impossible to do perfectly. If you want to find potential policies to enact, you need to examine very many policies that don’t work and aren’t in your constituents best interest. Those get left on the table and not advanced to actual congressional actions, sparing the legislator scrutiny for their creativity.
Some creative solution-seeking will happen in a bipartisan way through negotiation. I understand the desire to see the whole process, but removing the veil would change the behavior the participants. If every word were subject to partisan scrutiny from the wings, how could congresspeople possibly get anything productive done? See as evidence congressional committee hearings, in which the members spend significant time grandstanding for C-SPAN sound bites instead of productive questioning.
> When their behavior is conducted in secrecy behind closed doors the public doesn't have the ability to hold them accountable for it
This is obviously not true. Every bill has publicly documented sponsors and goes through a lengthy, public process with several rounds of procedural votes, committee approvals, amendment debates, etc. At some point there must be a minimum granularity of attribution. Track Changes from blank page to finished law would be useless anyway, because it would show some unpaid staffer actually typed most of the changes. Even Git history uses commits, and very mature projects like the Linux kernel revise their patches rather than keeping a detailed history of the patch creation. The champion who landed it and their reviewers are credited with the patch, as also in Congress.
> Often most of that work is done entirely for them by corporations and lobbying groups
The drafting and ideation? Sure! I wouldn’t want it any other way. It’s much better that we have an entire industry of people studying the law, finding solutions, and advocating their preferred options, rather than a group of Philosopher Kings making the law in isolation. You’re also dramatically downplaying the effort of coalition building, balancing constituent pressure, and passing procedural hurdles that is required to take a bill all the way from draft to law.
I think we may agree that provenance of bill text originating from outside of Congress could potentially be more transparent. But then again, the relevant interest groups are usually very well known by the time a bill reaches the floor anyway because that is their whole purpose, and they want to take credit for their victories. And “Monsanto drafted these provisions” is pretty far from the vision of absolute transparency and zero congressional privacy that you seem to be suggesting.
Do you have other specific ideas to increase transparency? If bill sponsor attribution, public debate and amendment, and recorded voting record are insufficient to understand a legislator’s actions, what would you suggest instead?
Likewise, a younger, more idealistic me thought it'd be great to use a GitHub-esque platform for laws. Pull Requests to suggest laws, gated behind reviews/approvals, branches so each house could work on their own versions before finally reconciling and merging into the Code, literally.
How can I try this to see if I should shut things down myself. I run a 6 figure stealth and have a day job for fintech in 9 figures all php so kinda worried
But created my own based on it since it feels sketchy running someone else's exploit poc ya know. Ran it first in a vm before running it against a production site.
Facebook hasn't used PHP for a very long time. It's been using Hack for over 12 years, which was initially based off PHP but it's deviated quite significantly now. It's now nearly entirely statically-typed, and has a bunch of features that PHP doesn't have. IO is fully asynchronous using async/await syntax (like C# or JavaScript), functions can be marked as pure, and a bunch of other things useful in large codebases.
It still uses the same request model as PHP, since that's genuinely useful for web requests. It's easier to avoid memory leaks if each request is entirely self-contained and there's no global state persisted between requests (other than APC and opcode caches)
This link gets me a shitton of extremely intrusiv ads, some of which look like malware (auto-downloading an "OperaSetup.exe"). Is pastebin already compromised?
I lose disputes all the time, no matter the evidence. I'm not happy with Stripe. The only thing keeping me from looking at alternatives is the low volume of fraud committed against my SaaS.
Do better Stripe. Be better Stripe. Or eventually we will find someone better. Think. Don't enshittify. Your support has already become covered in it by doing the needful.
Most likely because your country's banks are heavily lobbying against such initiatives.
It's easy to blame Visa and Mastercard, but the reason why the EU doesn't have this is that the EPP (the largest political group in the European Parliament) answers to European banks, which don't want it.
I think the cryptocurrency-based implementation is stupid and a product of its time, but the EU is investing a lot of money into a system to push Visa and Mastercard out.
Many countries have their own payment systems already, often widely successful. Integration between these systems has been annoying but things have started to centralize on two or three systems across Europe now.
>Private banks are resistant to a digital euro both as a payment method and a store of value. The digital euro is designed to be a free, public payment method, directly challenging fee-based systems operated by banks. This is its key usefulness in terms of sovereignty. But it could also be used as a digital wallet and users may move their money out of private bank accounts to central bank-backed digital euro wallets meaning banks lose out.
So far they have successfully delayed any implementation.
The original release was a proof of concept. That proof of concept is currently being developed into a fully-fledged proposal. Once that proposal is accepted, and legislation is ready, the first actual implementations can begin.
I don't think you can call it a "delay", the project just moves at a glacial pace.
The entire project was never going to finish before 2030. Some banks are upset about it, for sure, but others are in favour.
QR payments are ubiquitous in South East Asia. The eventual goal is ASEAN-wide interoperability, and some are even already interoperable with South Korean, Japanese and Chinese counterparts. And as expected, the US is also complaining about those, merely because Americans can't grasp the concept, like how they lag on pin adoption.
My experience is Claude and others are good at writing methods and smaller because you can dictate what it should do in less tokens and easily read the code. This closes the feadback loop for me.
I occasionally ask AI to write lots of code such as a whole feature (>= medium shirt size) or sometimes even bigger components of said feature and I often just revert what it generated. It's not good for all the reasons mentioned.
Other times I accept its output as a rough draft and then tell it how to refactor its code from mid to senior level.
I'm sure it will get better but this is my trust level with it. It saves me time within these confines.
Edit: it is a valuable code reviewer for me, especially as a solo stealth startup.
As a stealth ceo of a profitable SaaS. This is a nice reminder for my company to wind down its relationship with OpenAI. I have no doubt Anthropic will eventually become evil but at least they have a backbone today.
Goodbye Sam.
Edit: Also, referring to the DOD as the Department of War is cringe.
I clicked the article thinking it was about GitLab. Much of the criticism held true for GitLab anyway, particularly the insanely slow feedback loops these CI/CD systems create.
You can though. GHA and Gitlab CI and all the others have a large feature set for orchestration (build matrices, triggers,etc.) that are hard to test on a local setup. Sometimes they interfere with the build because of flags, or the build fails because it got orchestrated on a different machine, or a package is missing, or the cache key was misconfigured, etc.
There are a bunch of failures of a build that have nothing to do with how your build itself works. Asking teams to rebuild all that orchestration logic into their builds is madness. We shouldn’t ask teams to have to replicate tests for features that are in the CI they use.
Indeed there are. But you iterate on local and care about CI once everything is working in local. It's not every tuesday I get CI errors because a package was missing. It's rare unless you're in those 1000-little-microservice shops.
It is rare for our run of the mill Java apps to however, we notice it with:
Integration of code quality gates, documentation checks, linting, cross architecture builds, etc.
Most of this can be solved by doing the builds in a docker image that we also maintain ourselves. Then what remains is the interaction between the ci config for matrices, the tasks/actions to report back quality metrics, the integration with keyvaults to obtain deploy time secrets, etc.
Then there are the soft failures, missing a cache key causing many packages to be downloaded over and over again, or the same for the docker base images, etc.
We fix this for our 1000+ microservices, across hundreds of teams by maintaining a template that all services are mandated to use. It removes whole classes of errors and introduces whatever shenanigans we introduce. But it works for us.
If GHA, Azure Pipelines, etc., would provide a way of running builds locally that would speed up our development greatly.
Until then we have created linting based on CUE to parse the various yamls, resolving references to keystores, key ids, templates, etc., and making sure they exist. I think this is generic enough to open source even.