In general, I would expect an identity verification firm that I'm hiring to secure and then physically delete any sensitive records my customers are uploading, unless I explicitly opt-in otherwise. My guess is in this case that Discord is attempting to train its own models for first-pass verification, so this is a training corpus; there's no evidence that Persona's doing anything with Palantir, other than proximity of funding.
The broader issue here is that SV VC is starting to feel mildly radioactive when it comes to public opinion; Persona's previous lead fund (up through its Series B) was Index, run by the more conventionally-liberal Neil Rimer, and no one worried about that. The entanglement of Silicon Valley's oligarch class in very extreme politics* at a time of very fraught national political upheaval is making VC money politically-exposed money; if you take FF or Sequioa cash, how certain are you that they won't just get involved in your business, but push you to take specific political or social positions that serve their non-fiscal interests? How certain are your customers that that isn't happening to you?
For decades, SV venture capital has been tech money, and generally smart tech money (I don't like Thiel, but the man is absolutely the smartest of the PayPal Mafia set, and his success bears that out). Now, for various reasons (the end of ZIRP, the failure of major tech bets since 2016 or so to pay off, COVID overvaluations), VCs have moved into rent-seeking, particularly on government and military contracts. It's no longer tech money, it's political money, and, compared to traditional prime vendors, it's not clear that it's smart political money. After all, when the political winds turn, possibly as soon as this November, is it a smart strategy to have worked aggressively and incessantly to alienate the party coming into power? For a lot of startups with regulatory, legal, or political exposure risk, getting entangled with that might be more trouble than it's worth.
* There is no other term that suits the mix of open white supremacy and anti-democratic policies -- repealing the 19th Amendement, for example! -- that we see emerging from the PayPal Mafia.
I believe the argument will be that the rent seeking will be used to position themselves such that it doesn't matter who is in power, the government will listen to them not the other way around. Admittedly, the fact is, the Epstein Files existed across multiple political parties' justice departments and none of those folks have been investigated or prosecuted...
Recent updates say this was a unilateral call by FAA because DOD was refusing to coordinate with them for creating safety corridors for DOD drones and/or HEW usage. Issues came to a head after DOD shot down a highly threatening mylar party balloon, which FAA evidently considered to be a somewhat reckless use of military weaponry in a US city's airspace.
> Recent updates say this was a unilateral call by FAA because DOD was refusing to coordinate with them for creating safety corridors for DOD drones and/or HEW usage.
This is the first explanation I've seen that fits the odd facts perfectly. This is the kind of thing that happens when two regional bureaucracies collide. The FAA has long-standing mechanisms for coordinating military use of airspace with commercial and civilian flight operations.
But instead of the usual DEA border interdiction, the administration is now tasking the military to drive this. Military commanders on a new high-priority mission to intercept drones which can attempt to cross the border anytime and anywhere realized coordinating with the FAA would require committing to active corridors and time windows in advance, limiting their mission success and resisted. The FAA realized that could lead to lots of last minute airspace restrictions, flight cancellations and increased risk of a mistake resulting in downing a civilian flight.
The regional FAA administrators responsible for flight safety around El Paso decided to escalate the dispute by simply shutting down all civilian flights, knowing that would get immediate national attention. It was an extreme action but one that's within their purview if they can't guarantee the safety of the airspace. I'm sure they expected it would put political pressure on the military to limit operations and it worked. In a sense, it also helps the military commanders because being ordered to accept FAA operational limitations gives them cover if it reduces their mission effectiveness below what they'd promised. That's probably why the military wouldn't agree on their own without it being ordered from above. They're the ones responsible for deploying expensive new anti-drone tech in field ops for the first time. Future budgets and careers are on the line.
Update: DoD’s pushing back on the story, saying that Border Patrol and ICE were the agencies using high-energy weaponry to shoot down party balloons, much to the consternation of NORTHCOM.
> The Pentagon allowed U.S. Customs and Border Protection to use an anti-drone laser earlier this week, leading the Federal Aviation Administration to suddenly close the airspace over El Paso, Texas, on Wednesday, according to two people familiar with the situation who spoke on the condition of anonymity to discuss sensitive details.
FAA ought to be drowning Kegseth’s DoD in bureaucracy at every possible opportunity, after the massacre over the Potomac River a year ago. They deserve no leniency whatsoever.
If you see it on the DC metro, the buyer is a Hill staffer or a Pentagon action officer; if you see it at the Super Bowl, the buyer is you (assuming you're an American taxpayer), to help maintain a certain amount of public political capital when Congress starts looking at whether they want to fully fund TR-3 and Block 4. Cutting a military program popularly seen as successful is a whole lot harder than cutting one popularly seen as a wasteful failure, and doesn't garner the politician behind it nearly as much positive PR.
Design thinking, at least in its formal STS approach, is essentially applied sociology; it's about using various toolkits to build a sufficient understanding of a domain from the "inside out" (using desk and field research) so that you can design valuable experiences that build upon the expertise of those actually inside the domain. In this, it's a bridge between UX/product and users/stakeholders (technical stakeholders are admittedly too often an afterthought, but that's a process problem). If anyone comes in and attempts to blindly shove workshops at you without first conducting in-depth research, interviews, and field studies in your domain, then they are (without resorting to the One True Scotsman) not doing design thinking, they're doing cargo-cult brainstorming. (It's also a process orthogonal to agile development, since by definition it's a linear process that needs to be conducted prior to developing the actual product features and requirements.)
The books and papers the OP cites are solid (Rittel and Webber, Buchanan, etc., though TRIZ, I think, is rather oversold), but in my experience the problem with most design thinking practitioners is that they aren't qualified sociologists and ethnographers, so a lot of design thinking is basically a reinvention of the last century of sociological middle-range theory and ethnographic principles, without being strongly informed by either, likely due to the field's foundation in early software requirements studies.
These are good points. Although I discussed the TRIZ in couple of my articles. I need to revisit my thoughts as it is over-egineered Russian tool that eliminate all the benefits of subjective constructivism design mindset. It is simply say, everything can be solved using one fo those 40 ways.
That's a great answer that offers concrete insight into what design thinkers are trying to achieve. And it seems like they have a chance to succeed if they also employ iterative experimental methods to learn whether their mental model of user experience is incorrect or incomplete. Do they?
Traditionally you use a lot of paper and experiential prototypes to iterate on, which doesn't cover everything but helps refine assumptions (I sometimes like starting with mocking downstream output like reports and report data, which is a quick way to test specific assumptions about the client's operations and strategic goals, which then can affect the detailed project). When I can, I also try to iterate using scenario-based wargaming, especially for complex processes with a lot of handoffs and edge cases; it lets us "chaos monkey" situations and stress-test our assumptions.
More than once early iterations have led me to call off a project and tell the client that they'd be wasting their money with us; these were problems that either could be solved more effectively internally (with process, education, or cultural changes), weren't going to be effectively addressed by the proposed project, or, quite often, because what they wanted was not what they actually needed.
Increasingly, AI technical/functional prototyping's making it into the early design process where traditionally we'd be doing clickable prototypes, letting us get cheap working prototypes in place for users to test drive and provide feedback on. I like to iterate aggressively on the data schema up front, so this fits in well with my bias towards getting the database and query models largely created during the design effort based on domain research and collaboration.
It's not settled law as it pertains to LLMs, but, yes, creating a "statistical summary" of a book (consider, e.g., a concordance of Joyce's "Ulysses") is generally protected as fair use. However, illegally accessing pirated books to create that concordance is still illegal.
Man, back when I was doing Big Consulting (including gov't/defense) I had to affirmatively declare every year to Legal that I wasn't directing any investment purchases or doing anything that could be construed as improper use of nonpublic knowledge. And now Palantir reps just out here pushing insider trading tips like it's nothing, smdh.
Should go without saying, but since the media is doing a terrible job of reporting this, it's not at all clear what authority OSD/SecNav has to do this, given that even if there were something objectionable under the UCMJ about his statements he made those statements after retiring, and they aren't recalling him to active status (probably because a court martial would go very badly for the Navy and OSD).
It's exceedingly unlikely that this survives any administrative or legal scrutiny (and if it does, there's a whole lot of former active-status Trump allies, including GOFOs, who are more than vulnerable under these same standards); the main result, I think, is to elevate Kelly's political profile while turning most of the Pentagon even more against Hegseth and Phelan (the former being an over-promoted PAO, and the latter not even having that experience, having spent his career managing Michael Dell's money).
The cargo-cult shibboleth of "never put business logic in your database" certainly didn't help, since a lot of developers just turned that into "never use stored procedures or views, your database is a dumb store with indexes."
There's value in not having to hunt in several places for business logic, having it all in one language, etc. I was ambivalent on the topic until I encountered an 12 page query that contained a naive implementation of the knapsack problem. As with most things dogma comes with a whole host of issues, but in this case I think it's largely benign and likely did more good than harm.
But that is the result of having multiple applications needing to enforce valid states in the database.
"Business logic" is a loose term. The database is the effective store for state so it must enforce states, eg by views, triggers, and procedures.
Other "business logic" can happen outside of the db in different languages. When individual apps need to enforce valid states, then complexity, code, etc grows exponentially.
Other than a few ill-advised attempts to implement microservices infrastructure by well-intentioned co-workers I've not encountered situations where multiple applications needed to access a single data store. While I'm sure there are valid use cases there I suspect they're rare and should be treated like the outliers they are.
It was absolutely under version control and there was a full test suite. The guy that wrote it is easily in the top 3 smartest human beings I've ever met and an incredibly talented developer. Unfortunately a lot of his stuff required being at the same level on the IQ bell curve, which meant it was functionally unmaintainable by anyone else. If you're familiar with the Story of Mel, it was kinda like that.
A lot of people probably think it's better to keep database "easy to swap". Which is silly, its MUCH easier to change your application layer, than database.
genuinely curious, can you steel man stored procedures? views make intuitive sense to me, but stored procedures, much like meta-programming, needs to be sparingly used IMO.
At my new company, the use of stored procedures unchecked has really hurt part of the companies ability to build new features so I'm surprised to see what seems like sound advice, "don't use stored procedures", called out as a cargo cult.
My hunch is that the problems with stored procedures actually come down to version control, change management and automated tests.
If you don't have a good way to keep stored procedures in version control, test them and have them applied consistently across different environments (dev, staging, production) you quickly find yourself in a situation where only the high priests of the database know how anything works, and making changes is painful.
Once you have that stuff in git, with the ability to run automated tests and robust scripting to apply changes to all of your environments (I still think Django's migration system is the gold standard for this, though I've not seen that specifically used with stored procedures myself) their drawbacks are a lot less notable.
You give no reasons why you think it's a sound advice.
My experience is following
1) Tx are faster when they are executed a sql function since you cut down on network roundtrip between statements. Also prevents users from doing fancy shenanigans with network after calling startTransaction.
2) It keeps your business logic separated from your other code that does caching/authorization/etc.
3) Some people say it's hard to test sql functions, but since pglite it's a non issue IMO.
4) Logging is a little worse, but `raise notice` is your friend.
> At my new company, the use of stored procedures unchecked has really hurt part of the companies ability to build new features
Isn't it just because most engineers aren't as well versed in SQL as they are in other programming languages.
Stored procedures are great for bulk data processing. SQL natively operates on sets, so pretty silly to pass a dataset over the wire for processing it iteratively in a less efficient language, and then transfer the resultset back to the database.
Like any tool, you just have to understand when to use it and when not to.
It’s about what you want to tie to which system. Let’s say you keep some data in memory in your backend, would you forbid engineers from putting code there too, and force it a layer out to the front end - or make up a new layer in between the front end and this backend just because some blogs tell you to?
If not, why would you then avoid putting code alongside your data at the database layer?
There are definitely valid reasons to not do it for some cases, but as a blanket statement it feels odd.
Stored procedures can do things like smooth over transitions by having a query not actually know or care about an underlying structure. They can cut down on duplication or round trips to the database. They can also be a nightmare like most cases where logic lives in the wrong place.
You have the same problem that you have with legal LLMs; an LLM is incapable of providing legal or regulatory-involved advice, and anyone using an LLM for such purposes (even leaving aside hallucinations) forfeits any justifiable reliance defense. There's a role for LLMs, but no one with legal responsibility over reporting could or would possibly rely on an LLM for complex regulatory and rules analysis, not when there's the risk of your wardrobe being replaced with orange jumpsuits.
That’s not because of the FDA, that’s because of CEPS. If the USG negotiated drug prices the way France does, there’d be far less disparity in average pricing. (Given the continual litany of safety, efficacy, and dosage control issues with imported drugs, FDA isn’t regulating them enough, largely because the inspection budget just isn’t there.)
The broader issue here is that SV VC is starting to feel mildly radioactive when it comes to public opinion; Persona's previous lead fund (up through its Series B) was Index, run by the more conventionally-liberal Neil Rimer, and no one worried about that. The entanglement of Silicon Valley's oligarch class in very extreme politics* at a time of very fraught national political upheaval is making VC money politically-exposed money; if you take FF or Sequioa cash, how certain are you that they won't just get involved in your business, but push you to take specific political or social positions that serve their non-fiscal interests? How certain are your customers that that isn't happening to you?
For decades, SV venture capital has been tech money, and generally smart tech money (I don't like Thiel, but the man is absolutely the smartest of the PayPal Mafia set, and his success bears that out). Now, for various reasons (the end of ZIRP, the failure of major tech bets since 2016 or so to pay off, COVID overvaluations), VCs have moved into rent-seeking, particularly on government and military contracts. It's no longer tech money, it's political money, and, compared to traditional prime vendors, it's not clear that it's smart political money. After all, when the political winds turn, possibly as soon as this November, is it a smart strategy to have worked aggressively and incessantly to alienate the party coming into power? For a lot of startups with regulatory, legal, or political exposure risk, getting entangled with that might be more trouble than it's worth.
* There is no other term that suits the mix of open white supremacy and anti-democratic policies -- repealing the 19th Amendement, for example! -- that we see emerging from the PayPal Mafia.
reply