infamia
Microsoft and Adobe are both already under investigation. Based on the preliminary findings, they've been suspended from participating in the Green Card program along with a host of other companies. [1]
> That's not going to happen. It's easier for them to send the jobs offshore.
It sounds like that's what the administration is demanding (i.e., hire more US workers before they can participate in the H1B program). [2]
[1] https://www.cnbc.com/2026/10/08/microsoft-adobe-green-card-l...
[2] https://www.theguardian.com/technology/2026/oct/08/jd-vance-...
I really like this metaphor, it hits home that just because you sense something is human-like doesn't make it so. We're wired to respond to those sorts of things.
> When I stumble around trying to explain my thinking
I had similar difficulties expressing my thoughts in an organized way. The video below from Richard Sutton (the father of Reinforcement Learning [which LLMs use extensively in training]), helped bring order and firm up some of my thoughts and theories.
https://www.youtube.com/watch?v=21EYKqUsPfg
>I invariably get hit with the response, Sure, but if it's functionally identical to a coin being magically pulled out your ear, what's the difference if it is or if it isn't?
Not to spoil the video, but it isn't at all functionally equivalent. LLMs are an imperfect and somewhat randomized simulation of what the LLM thinks an average person might say in response to a question. Which is another way of saying, most people will on average get worse answers than if they worked on a problem themselves (but they will get that worse answer from the LLM comparatively quickly). Practical people respond to this positioning fairly well, and for others it still lands a bit since no one wants to think they're below average. That said, I'm still working on my positioning a bit as well!
Perhaps, which is why I hedged with the possibility that it is mere hyperbole. However, I think what did it for me was his statement that he provides and expects feedback to anyone not following this recipe, which is at utterly without nuance. Incidentally, you can execute with focus and intention without urgency and arguably be more effective over the long haul.
> Before the 2024 Carbon Pollution Standards, the federal limits were much weaker—and for existing power plants, there was effectively no operative federal CO₂ limit at all.
This is an exaggeration that stretches credulity, since there have been strict limits for decades around secondary outputs that are required by power plant energy production effectively limiting production and emissions (which is the entire point).
If everything is urgent, then nothing is. This guy sounds miserable to work for and with. Assuming this is accurate and not just hyperbole, he is essentially saying he has no prioritization skills because everything is urgent. I think most people who have been around the block have worked with people like this, and unbeknownst to them, their coworkers develop a default snooze button associated with most of their requests and projects.
The ADA was written in an extremely non-specific way that allows unelected bureaucrats to reinterpret it every so often. To be honest, the US would probably have a more accessible society if the law was better written.
People don't know exactly the words that they're going to say necessarily, but tend to start with a general concept of what they're trying to communicate and only then try to put together the words (sometimes out of order). LLMs do not begin with any sort of concept they're trying to express. LLMs are simulations that attempt to reproduce what an average person might say while wired up to a huge knowledgebase.
https://docs.djangoproject.com/en/dev/releases/6.1/#model-fi...
That's the great thing about Django, it's been around so long and the quality bar is so high that eventually all the major rough edges get sanded away usually in a really well considered manner.
A transmitter is a sensor in a power plant that very precisely measures the air flow within the combustion chamber, so the fuel burns as clean/efficiently as possible. Relatively new transmitters can read with more precision, so you can dial down the airflow/fuel and the corresponding power output.
I don't doubt there's a small number of plants that can't do 10-1. That said, transmitters are intended to be replaced and upgraded regularly since they have a finite lifespan (they're cheap anyhow). 10-1 has been around for 35+ years now and you're really lucky to get 20 years out of a transmitter.
Lots of folks don't know that coal and gas fired plants are able to turn down their power generation more than 90% (i.e., "ten to one turn down"). It's definitely true that cold restarts take a while. However, they often rather quickly and dramatically change their power output profile while running.
SSE is perfect for chat/notifications and is a lot simpler than syncing. The server pushes updates to the client doesn't require a sync. SSE is also more performant since it can keep the connection open. The example below is on a $10 vps last I heard.
Your example is about one developer's decision, which is not really what we're talking about. The damage goes way up when you start talking about an arbitrary number of applications. A more apt analogy is, what if you couldn't install any applications except through the Windows Store? We're talking about restrictions laid down by the OS developer and for iding all applications outside of their crappy walled garden, which is very different. Also, you don't actually think Google is going to stop there do you? They will certainly turn it off one day of they think they can get away with it, because it is in their financial self-interests to do so.
Edit: Of course, you do need to have enough demand/scale to make it worth your while, but that will depend on your audience size and how engaged/invested they are in your content AND you personally to an extent. Perhaps be creative and start out with small experiments. Not too hard with LLMs nowadays.
People have been following this strategy of creating their own mini-brands for years and have their own following. YT doesn't even have all of the their content, and YT is just one lead gen channel. Frankly, Ad Revenue from YT is pitiful, and it's an open secret the real money is made as I've described (although it is a long term play).
I don't disagree with you about PeerTube and the like, but it is a two-sided marketplace and you need to prime both sides of that pump (content creators and viewers).
The problem is the reader has to invest time to find out and LLM written text will (on average) lower the quality towards "meh" and spend more words doing so. Even if the author is making an earnest effort to produce high quality content, they need to admit to themselves and others that their results will be more hit or miss. The disclosure allows the reader to make a more informed decision about how to engage with the material (e.g., have an LLM summarize or analyze the content, or just dive in because we know it will very likely be a good read). Editing what someone has written is like reviewing code, you're by default not as invested, so the results will likely reflect that reality.
1. If you want to know when something happened and a particular place is important (like the previously mentioned doctor's appointment), store the local date/time with timezone data. That covers you in case the timezone changes before your recorded event happens. Personally, I would not store reflexively store dates/times in a string. For the cases I encounter, that feels like primitive obsession since you can always use EXTRACT in a query to simplify output.
2. If will you need to lookup the date and time after an event occurred, write a separate field that includes timezone offset field (e.g. -1, +1, -8, etc.) in case you want to look up exactly when an event previously happened. This (mostly) covers you from timezone shifts that occur at that particular location between when you wrote the data vs some later date. This falls apart if the timezone you're converting to also changed their timezone between now and the event. Also, if your timezone shifts between when you wrote the record and the actual event.
I wonder if someone has a temporal record of timezone shifts. You could solve a lot of edge cases with something like that. Then you could write a query that asks for the timezone's offset as of a specific date. That would make life much easier. Then you could skip the timezone offset field I mentioned in #2.