Some sort of LLM audit trail is needed (containing prompts used, model identifier and marking all code written by LLM). It could be even signed by LLM providers (but that wouldn't work with local models). Append only standard format that is required to be included in PR. It wouldn't be perfect (e.g. deleting the log completely), but it might help with code reviews.
This would probably be more useful to help you see what (and how) was written by LLMs. Not really to catch bad actors trying to hide LLM use.
This would be a useful feature to bake into the commits generated by agents. Heck you don’t even need to wait — just change your prompt to tell it to include more context in its commit messages and to sign them as Claude rather than yourself…
1. Without noise you become more aware of your tinnitus.
2. WFH -> Less movement -> Decreased blood flow can contribute to the onset of tinnitus.
Long exposure to high volumes causes hearing damage. Many people set volume on headsets too high to hear better.
3. Many people are diagnosed with tinnitus every day, and some are bound to have it discovered after a vaccine shot. In the same way, some people will have tinnitus discovered after COVID. That doesn’t yet prove causation.
I'm not sure what you mean - I think the mobile 300 series can do quad channel already for its APU at least. I'd assume it can do more but do you not need more slots beyond that?
There are a single-digit number of products using the AMD Strix Halo mobile parts that have a 256-bit memory bus. All other mobile x86 processors (including AMD's mainstream Mobile silicon used for these desktop processors) have the usual 128-bit bus.
> The best UX in every single instance I've encountered is consistency.
While I agree that consistency is hugely important, I have also seen a lot of cases where it made the UX worse. The reason is that, unfortunately, UX isn't so simple. There isn't a single UX rule that is always true. UX design rules (best practices, guidelines, or principles) are a good starting point, but in a lot of situations multiple rules are conflicting each other. UI/UX design is dealing with tradeoffs most of the time. Good designer will know when breaking a specific rule will actually improve the UX.
Consistency is very important, but sometimes a custom UI element will be the best tool for the job. For example, imagine UI for seat selection in a movie theater ticket booking app. A consistent design would mean using standard controls users are already familiar with, but no standard control will provide high quality UX in this situation (not without heavy modifications).
But I still I agree with you that a lot of bad UX is due to inconsistency. There needs to be a good reason each time consistency broken and often it is broken for the wrong reasons.
A success story by what definition? I cannot judge Haskell as I don't know it well enough.
I should have added "usually". On average when something is designed by a committee the effect is like this, but not always. You don't have to take my word for it [1]. That kind of outcome is not always guaranteed and the result can be good in some cases. In same way, an AI generated content can also sometimes have character.
> A success story by what definition? I cannot judge Haskell as I don't know it well enough.
In the sense that it looks coherent and incorporates a lot of lessons learned over the decades of functional programming.
Design by committee usually fails either by being boring or by becoming a Frankenstein monster made of various contradictory opinions of committee members. Neither is the case with Haskell.
And the only bad design decision that I know of, namely to not make Monad derived from Applicative, was corrected in a future release.
Brains are great at pattern recognition (lots of studies). This includes ratios. Your shade of color is not a good example, because it's just a single value, not relative to anything on its own. But if you have multiple colors, there will be various relationships/ratios between physical properties of the colors (wavelength, intensity etc.). Similar in music, 1:2 frequency ratio is recognized as an octave. Strongest ratios (i.e. strong pattern) are usually the simple ratios like 1:2, 1:3 & 2:3, etc. However, science hasn't been able to find out, if we can recognize Golden ratio because of the Fibonacci sequence pattern that is often found in nature or if it's to us just a ratio that is close to a simpler ratio like 5:3.
It will probably get there one day since all BCL is annotated. Perhaps this is not done because you can have parts of the library be completely safe to use in AOT while another part not be.
Oh, I despise this tactic so much. It means the company has known from the start that they can't offer it for free in the long term, but decided to subsidize it in order to gain a dominant position and get rid of competition. This breaks the conditions needed for a free market dynamics to work. In other words, they win market share for reasons other than efficiency, quality, or innovation. That's why some forms of government subsidies are prohibited under certain agreements, for example. Some multinational corporations have annual revenues larger than the GDP of many countries and can easily subsidize negative pricing for years to undercut competitors, consolidate market share, and ultimately gain monopoly power.
Also, the company has hinted false promises to the customer, as it signals that they have developed a business model where they can offer something for free. For example a two-sided marketplace where one side gets something for free to attract users and the other side pays (as it profits form these users). Users can't know something isn't sustainable unless the company explicitly states it in some way (e.g. this is a limited time offer).
So from the user's perspective, this is a bait-and-switch tactic, where the company has used a free offer in order to manipulate the market.
reply