You want to stop the source, which is that the government and other agencies can purchase surveillance data that would otherwise be disallowed by the 4th amendment. We need to end this 'laundering' of information through third parties, and enforce the constitution by its intent.
> But no need to wait. At a high level, Gas City is the answer to all your problems. Ha! At least, for certain classes of problem, such as, “How can I bring AI into my company and pass an audit trail,”
The important audit at my company is conducted by the FDA.
I have a feeling when they ask what processes we followed to mitigate any user harm that could be caused by software changes that "I told an AI-mayor in the form of a cartoon fox what to do and he spit out a bunch of vibecode software written by AI-driven virtual cartoon characters" is not among the answers they want to hear.
Yes, or pretty close to it. What we don't know how to do (AFAIK) is do it at a cost that would be acceptable for most software. So yes, it mostly gets done for (components of) planes, spacecraft, medical devices, etc.
Totally agreed that most software is a morass of bugs. But giving examples of buggy software doesn't provide any information about whether we know how to make non-buggy software. It only provides information about whether we know how to make buggy software—spoiler alert: we do :)
Anthropic deserves to have this as the top comment on every HN post. It's absurd that they don't clarify this better and so many people are running around online saying the exact opposite from what their, confusing, docs say.
The Chilling Effect of this is real and it gets more and more frustrating that they can't or won't clarify.
They will never see a single cent from that, AA will continue to rotate domains and nothing was accomplished, except for spotify's legal team which earned easy money arguing against empty chair in court.
Shoutout to Arq backup which simply gives you an option in backup plans for what to do with cloud only files:
- report an error
- ignore
- materialize
Regardless, if you make it back up software that doesn’t give this level of control to users, and you make a change about which files you’re going to back up, you should probably be a lot more vocal with your users about the change. Vanishingly few people read release notes.
> You basically just need a metal tube, and well... a pipe from home depot does that much better than trying to 3d print something much less reliable.
Why would you buy a pipe at Home Depot? A gun barrel is not a firearm, and is not required to be registered or serialized. You can drive to Arizona or Nevada and buy an actual barrel, with rifling, manufactured to meet well-known specifications, without showing an ID. Until this year, you could have a barrel shipped to your California residence without an ID. There's no need to build the Shinzo Abe contraption.
> So my assumption is immediately that some relatively large lobbying group feels threatened by 3d printing, and is using this as a driver to try to control access and limit business impact.
Occam's razor. This isn't a shadowy manufacturing cabal, threatened by 3D printing. Gun control lobbyists are trying to prevent the printing of handgun frames and Glock switches, because they're the easiest parts to print.
> Either way, this is bad legislation.
California legislators haven't met a bad gun law that they don't like.
Repeating myself, when we speak of bugs in a verified software system, I think it's fair to consider the entire binary a fair target.
If a buffer overflow causes the system to be exploited and all your bitcoins to be stolen, I don't think the fact that the bug being in the language runtime is going to be much consolation. Especially if the software you were running was advertised as formally verified as free of bugs.
Second, there was a bug in the code. Maybe not a functional correctness bug, but I, along with many and most end users, would consider a crashing program buggy. Maybe we just have different tastes or different standards on what we consider an acceptable level of software quality.
W.r.t people running Lean in production, you'd be surprised...
I might be missing something, but what I need is not "stacked PR" but a proper UI and interface to manage single commit:
- merge some commits independently when partial work is ready.
- mark some commit as reviewed.
- UI to do interactive rebase and and squash and edit individual commits. (I can do that well from the command line, but not when using the GitHub interface, and somehow not everyone from my team is familiar with that)
- ability to attach a comment to a specific commit, or to the commit message.
- better way to visualize what change over time in each forced push/revision (diff of diff)
Git itself already has the concept of commit. Why put this "stacked PR" abstraction on top of it?
I did something similar to a local company here in Spain. Not medical, but a small insurance company. Believe it or not, yes, they vibecoded their CRM.
I sent them an email and they threatened to sue me. I was a bit in shock from such dumb response, but I guess some people only learn the hard way, so I filed a report to the AEPD (Data protection agency in Spain) for starters, known to be brutal.
I've also sent them a burofax demanding the removal of my data on their systems just last friday.
Any company that does the "unlimited*" shenanigans are automatically out from any selection process I had going, wherever they use it. It's a clear signal that the marketing/financial teams have taken over the businesses, and they'll be quick to offload you from the platform given the chance, and you'll have no recourse.
Always prefer businesses who are upfront and honest about what they can offer their users, in a sustainable way.
I used to work at Blackmagic, wrote some of the peripheral code around BRAW and did some work with the Resolve guys up in Singapore.
Used to have lunch regularly with one of the owners too. Need to check in with him again!
At least back in 2019, BMD made a lot of money selling professional licences for DaVinci Resolve. I don't know exact figures but that part of the business was healthily profitable of its own accord. Very, very healthily profitable!
Most parts of the business were profitable standalone, AFAIK. Their model didn't revolve around loss leaders, burning VC money or anything like that; just selling good products at fair prices and making bank.
I think a big part of it was a fairly lean culture (whole company was bootstrapped and grown sustainably), and specifically in the case of DaVinci they bought out an existing business that had already done a lot of the development and marketing work for absolute peanuts.
I’m working as a single solo developer of a tiny video game. I’m writing it in C with raylib. No coding assistants, no agents, not even a language server.
I only work on it for a few hours during the week. And it’s progressing at a reasonable pace that I’m happy with. I got cross-compilation from Linux to Windows going early on in a couple of hours. Wasn’t that hard.
I’ve had to rework parts of the code as I’ve progressed. I’ve had to live with decisions I made early on. It’s code. It’s fine.
I don’t really understand the, “more, better, faster,” cachet to be honest. Writing the code hasn’t been the bottle neck to developing software for a long time. It’s usually the thinking that takes most of the time and if that goes away well… I dunno, that’s weird. I will understand it even less.
Agree with writing less code though. The economics of throwing out 37k lines of code a week is… stupid in the extreme. If we get paid by the line we could’ve optimized for this long before LLM’s were invented. It’s not like more lines of code means more inventory to sell. It’s usually the opposite: the more bugs to fix, the more frustrated customers, the higher churn of exhausted developers.
Hyperbolically, I think it's one of humanity's greatest resources. I can find anything from precision machining, LLM internals, historical footage of WWI, music performances from pretty much any era, and on, and on. There are so many things that I didn't know there was any footage of or that I didn't a single thing about that I find there pretty much daily.
I wish the BBC would publish their whole archive through YT. The few things that they do put up are often so mind expanding whether it's Berty Russel, The Beatles, or some cracking Scottish chap going for a bike ride with a bottle of whisky.
> The primary goal is clear and simple: to require 3D printer manufacturers to use a state-certified algorithm that checks digital design files for firearm components and blocks print jobs that would produce prohibited parts.
"state-certified algorithm" has a really nice tyrannic ring to it. I am sure once this has passed the rich people can finally sleep at night knowing they are safe from roving gangs of armed Mangiones.
The paper opens with "to feed a growing population" without asking is that what we need? want? where we are actually heading to?
Is feeding the world a real problem? I've yet to see compelling evidence that it really is except as a secondary effect of logistics, energy supply, and war.
edit: I understand the environmental impacts. I think we should solve our energy problems first.
I've come to dread any formalization of Agile. Agile development is fine. I've built a 40+ engineering team with it. I can vouch for its effectiveness when applied to small, excellent teams.
For reference, here's all the Agile you need, it's 4 sentences:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
The real problem is that capital-A Agile is not agile at all, but exactly the opposite: A fat process that enforces following a plan (regular, rigid meeting structure), creating comprehensive documentation (user stories, specs, mocks, task board) and contract negotiation (estimation meetings, planning poker). It's a bastardization of the original idea, born by process first people who tried to copy the methods of successful teams without understanding them.
You can build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
Youtube must know better than me what to recommend me out of all the videos... still, I get presented the same shite again and again.
To be fair: not everything is shite and Youtube is my favorite social media (especially for discovering new music), but I noticed a big drop in quality videos from one day to the other a couple of years ago. Just opening up Youtube one day and seeing all kinds of thumbnails with people with their mouth open, very 'colory' thumbnails (more childlike), channels that I would never watch being presented... I should have noted the exact date, but I didn't. I guess it was around two years ago.
Even searching for specific topics is hard. I just know there's enough material on the platform, but in my search results I get so many doubles and channels that I already know. I can keep scrolling, but to no result.
If anybody knows some good DIY or woodworking channels, let me know!
Fundamental misunderstanding of the market dynamics here.
There are at least an order of magnitude more people making a professional salary as photographers (ie.: enough to justify a software purchase) than professional videographers.
Outside of film, videographers are generally paid a day rate about half as high as photographers, with enormously higher equipment costs.
Film - hollywood, streaming, TV etc, combined actually employ a relatively small number of people. Sure there's enormously more budget for any given TV show than say a wedding photoshoot, but think about how many people get married, how many corporate photo sessions there are etc etc.
Basically by conflating videography and cinematography you've obscured the issue. Source - I'm a videographer that also works as a cinematographer / director on smaller budget projects.
Also on anything bigger than a very low budget short, it's editors and post people who are using the editing software not the videographers / camera operators / DOP. Bare in mind DaVinci does not own the film industry. It's very much still Avid's game, with Nuke for colour, and a small percentage of Adobe Suite.
Its going to be funny when there are married 17 year olds driving cars with guns and children but who can't install linux or access facebook without calling their dad.
