arter45
In other words, they are asked to do overtime. So, as long as they are getting adequately paid for that overtime and they are not forced to do so (but I assume you can always find at least two people out of 20 who could do that), I don't think it's a big deal.
So Google, with hundreds if not thousands of security engineers, basically infinite budget, more than 500 published papers on security and privacy, multiple security teams, including one (Project Zero) that has discovered at least 2,000 vulnerabilities in the last 10 years, and with actual experience in privacy applied to its many apps and solutions... is unable to anonymize data when required to avoid a lock-in?
At every point in time t, f(t) is the price per 1 GB of RAM which is 1GB/1B times the price per byte of RAM.
Because 1GB/1B is non-zero, it follows that f(t)=1GB/1B F(t).
It also follows that ratios are preserved, ie
f(t1)/f(t2)= 1GB/1B F(t1)/F(t2)
As long as f(t2) is non-zero, which in this context is never the case.
Visually, the two graphs are the same except scale is different.
Palantir really doesn’t make sense. It’s like developing a bulletproof vest and naming it Horcrux… sure, in the HP world a Horcrux does protect you from death, but it is very associated to evil, so no one who is really fan of the saga would choose that name, especially for a publicly known product.
Then again maybe they just asked an LLM “I have a surveillance solution. I want to name it after a fantasy concept. Any ideas?”
Source?
I think the argument here is:
- laws are slow
- innovation is faster
- if you let laws regulate AI you're basically playing catch up
- therefore, let technology regulate AI in real time: once a decision is made, it is immediately valid.
From an efficiency standpoint this may make sense, but the important question is: who makes the decisions that are then implemented in software?
AI platforms are generally provided by private operators, so there are two actors here: the State and the AI provider.
Assume the State decide to completely deregulate AI.
Let's take deepfakes. As long as an AI provider makes money out of deepfakes, and they do not fear sanctions (remember, there is no government regulation), why would they ban them? Reputation risks? Well, there are many AI providers, so as long as they can produce deepfakes that cannot be traced to a specific AI platform, why bother?
It's one thing to say that laws are slow, quite another to say that democratic accountability and general concerns other than making money should be thrown out of the window in favor of fast but obscure processes.
>The first thing a rational economist would do is tell the government to fire all economists and stop accrediting economics degrees
Please elaborate.
I don't think this surprise anyone, especially given that Adam Smith, who is known as the father of modern economics, wrote a book describing stuff that was obviously already happening before his ideas were published. Not to mention Italian bankers, tulips bubbles, gold coins and so on.
However, this doesn't mean that things do not (or cannot evolve). Markets are observed by someone, a theory is born, markets evolve, maybe following a theory, an existing theory is generalized, and so on.
If you remove DNS servers from the equation, you need to write down records for other domains, too. This means you have to chase every domain for changes in CDN configuration, hosting provider or ISP migrations, IPv4 to v6 migrations and so on.
You don't have PTR records, which means you can't find out a name from its IP address.
You also miss other features of DNS, like SRV, MX and so on.
More subtly, you lose the ability to control DNS resolution over systems you can't control. If a DNS server says host.example.com is 192.168.0.4, a Windows desktop, a Linux server and your toaster will agree on that (especially if no local cache is enabled, but even then TTLs apply). If for some reason you cannot control a particular machine, you will never get it to consider that new DNS record. This can happen for a lot of reasons.
With —-all
Yes, there are alternatives to GDP, but context is key.
If you just to make more meaningful charts or rankings of top 10 countries, you just switch to another indicator and that's it. This could also impact, to some extent, real economic choices.
Other applications are more difficult.
For example, debt substainability. Governments issue bonds to finance stuff, but they eventually have to repay at least interests. This introduces a link between GDP and debt growth. If you replace GDP with another index things get more vague: a country may have the maximum happiness, but if it issues bonds and it cannot repay its interests, it's going to have some trouble anyway.
Monetary policy is also difficult to decouple from GDP. Alternative indicators often mix many aspects, which means the central bank can either
1) target the whole index, which means it could try to influence not just interest rates, but education, healthcare and so on (it essentially blends with the government), or
2) keep targeting inflation, but through non-GDP estimates, which means the price "signal" is mixed with other "noise".
If anyone, including your surgeon, can take that life insurance policy based on your life, things can go bad pretty quickly (hint: what happens if a profit-maximizing surgeon would earn a lot more money from your policy than from his regular job?).
That's why there is so much emphasis on signing or stamping projects in the "ordinary" engineering world: you're literally telling a potential third party (which may include a court of law at some point) that you reviewed the work and can be held responsible.
This doesn't rule out team work of course (just think about civil engineering, it's not something you can do alone most of the times), and this doesn't mean there are no unethical or even corrupt engineers, but there is in most cases a single person who is responsible from a professional, ethical, and legal point of view.
In my experience this never occurs with programming unless you're dealing with SWE in engineering-adjacent sectors (aerospace, ...), and even then I'm not sure as I have no personal experience in those areas.
It does mention IP concerns, but that's not the greatest existential threat posed by AI.
It’s like SMS vs MMS or modern chat. With pure text, you can at best add a link to a picture (which could get rotten or inaccessible for other reasons), but you cannot directly graphical content.
Not necessarily. I hate frontend tasks not because I don’t care about the user, but because I don’t have decent graphic skills. I can code but I don’t have a good istinct for colors, size, font styles, or other frontend issues that feel more art than science.
I’m honest about it, and luckily my job doesn’t involve frontend tasks, but this doesn’t mean that I don’t care about the users. In fact, you could say that I avoid frontend tasks precisely because I care about users and I don’t want them to be tormented by my awful UI choices :)
> Frontend problems are just easier to see — bad UI, confusing views, ugly design. Everyone notices. Backend problems are hidden — slow API response, bad errors, hard to manage code
That’s one way to see it. Another way is that frontend problems are subjective. The same UI could be confusing for someone and reasonable in someone else’s eyes. What’s ugly? “Beauty is in the eyes of the beholder”, as the saying goes.
Backend problems can be hidden and random but they are objective. If an API returns 500, there is something wrong. It may do so only when a plane passes by or when a cosmic ray happen to flip a bit, but everyone can agree that a 500 is not supposed to happen (unless your API intentionally returns 500 for success…). The root cause may be obscure, but the existence of an issue is objective.
But yes, you don’t always need cool technologies.
It probably doesn’t require consensus among all participants (pairwise consensus at every step should be fine), so there is very likely no voting.
It’s not even permissionless. It’s not like a random company could join this “chain” simply because they can generate a keypair.
It’s a fundamentally different problem, and it makes sense that the architecture is different.