••••••••••••••••••••
You are asserting that these changes are somehow tied to time, by the very construction of your experiment in that you ask the same questions sequentially day-by-day. However, that leaves you unable to be sure whether the changes are actually tied to the time because it is not being controlled for, as near as I can tell. As near as I can tell from your "Method and Limitations" from the previous day's run, you are only asking a given AI a given question once. You need to ask the same AI the same question a number of times, preferably as close to simultaneously as possible, to see if there's as much variance within a single day as there is in a week. As your experiment is constructed, it is not possible for you to collect the data adequate to prove the claim you are trying to make. As I think it is likely that the variance you are seeing is the randomness in the answer process itself and not tied to time at all; two people can probably ask the same question at the same time and get two different answers. If nothing else, have an AI go back over your experiment, perhaps feed it this comment as well, and ask it what else may be flawed in your experiment. That doesn't mean you have to adopt every suggestion; every experiment can always gather more data and always have an expanded scope and always cost more money. However this is a more-or-less fatal problem with your experiment and there may be others, this is just all I'm considering. An AI can bang on the problem in a more dedicated fashion than I'm doing here.
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
> These are 90-95% cheaper than Anthropic. I'd prefer open source, too, but this has nothing to do with Windows Phone OS (which failed because of network effects). FWIW it is worth noting that the GP's suggestion is more in line with Microsoft's own stated belief in the future of "unmetered AI". At the moment, Microsoft is arguably meeting that claim with their support for and encouragement of Nvidia Nemotron Bolt, which is an actually pretty good, quite interesting, unusually-trained-and-sized-to-fit MoE model that was designed to go with the launch of the Nvidia/Microsoft RTX Spark machines. (Good Sam Witteveen video about it: https://www.youtube.com/watch?v=WJpeW9lCSUM ) But it would be good to see Microsoft themselves distilling an open weights model. Like any vendor with a profit motive they do have to decide the obvious, though: how do you make money from it, when right now it could cost several hundred million dollars to train (even if you adjust the training of a larger proprietary model so you can distill the smaller one from it)? There is, essentially, no way to keep an open weights model from being copied/distilled/extracted, and IMO what that tends to suggest is that open weights models will essentially gravitate to sort of uncontroversial, "standard library" tasks. So I think it also means that Microsoft's approach on open weights will ultimately be the same as Apple's: they will focus their efforts on LLMs that meaningfully add function to their OS and can be decapitated to make similarly useful decision models. Put another way: given the geopolitical angle of the last few weeks, I think it is possible that the open weights coding models we have now may be among the best we will ever get, until the nearly inevitable GPU/tensor hardware glut arrives. In the meantime, something else is clearly happening: much broader competition in the "good enough" models category, which is what we need to drive down the cost of inference hardware such that open source and open weights are feasible over the longer term.
•••••••••••••••••••••••••••••••
Im quite sceptical of articles making claims, as opposed to data that explains the productivity over a large enough scope. OUTSIDE OF TECH: From what I am personally seeing, there are more incremental improvements in productivity than step changes in firms . For the degree of hype, we would expect more step changes. For the actual capability of these tools, it should be more incremental changes. The greatest determinant of a step change in productivity is the presence of 3 things, typically in one person. 1) Domain expertise 2) project expertise/knowledge 3) familiarty with AI tooling All of which are useful because this allows the operator to identify when a session is going of the rails quickly, discard the output, and switch to a better prompt. Otherwise, the productivity gains are incremental, and arise out of capability expansion in doing early career work. i.e., AI removes the communication friction of reaching out to another firm or team. There are going to be MANY counter examples and anecdotes on how this is not true. Good counter examples are people using LLMs to assist with legal issues or handle translation. This is usually within the boundaries of early stage work, which the operator has enough experience and common sense to understand. Another boundary is review - people are getting spammed from inside now, because the cost/ease of generation has gone down, while verification capacity has not kept pace. The ratio of availble V/G vs required V/G for a process depends on how mission critical that process is. Most firms are stuck in a hype driven cycle to just produce more, and review is not a valued part of the process. I expect that this is going to change as soon as people start asking who is responsible and accountable for things going wrong. Velocity is great as long as you don't break someone else's things. I am going to regret writing this.
•••••••••••••••••••••••••••••••••••••••••••••••••••
Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln. Today we are going to take a look at how to avoid this vuln by not having Nginx and not using HTTP/2 (for most use cases). We will assume that you are using Nginx for any of the following: Serving files or serving dynamic website content through some integration with a programming language. We will be using python, but you can use any programming language that has a native integration with sockets through it's C interface (literally every language: Step 1: import socket # import the socket library from glibc or glibc. Step 2: socket.socket() # socket.socket() Step 3: socket.bind((PUBLIC_ADDR,80)) # bind before listening obviously. Use a local address if you are below the IPoverty4 line. Step 4: conn,addr = socket.accept() # this creates a connection, wrap it in a While True and a try catch for production. Sprinkle in some import threading to support multiple concurrent requests. Step 4: req = conn.recv(4096) # split on b"\r\n\r\n" to separate headers from body, read HTTP RFCs for the rest. Feel free to reject HTTP/2 requests, they'll probably just resend as HTTP/1.1 Step 5: #Fill in the details, most likely if you are using nginx, you will end up connecting two sockets with pipe, or just storing and forwarding to another tcp endpoint. Again take a look at the HTTP RFCs and the glibc socket and stdio manuals. Thank you for reading my tutorial, and best of lucks.
••••••••••••••••••
Man, is it aggravating to read fantasies like this, as someone who's trying to juggle a full-time job and hosted public services for other people at the same time. There are two internets. One of them is open, less-commercial, and largely built and maintained by people whose first job is not the work they do to maintain this internet. That group includes a ton of open source software, millions of small servers scattered around the world (virtually private or otherwise), and is generally best-effort. The other internet is fully commercialized, often ad-driven, fully integral to the data broker economy, and centralized behind a few companies that pay as few people as possible to satisfy the occasional PR statement that, "we take security seriously and...". The next stable equilibrium here is not "we get a secure and open internet". The next stable equilibrium here is, "we have no open internet, and the internet is now managed by just a few companies." We're already halfway there. Google and Microsoft combined already account for somewhere around 30% to 40% of email traffic. 30% of all websites are now behind Cloudflare. A few companies dominate social media traffic. Amazon and Shopify combined are half of US e-commerce. Every single short-response-window exploit like this just pushes a few more percentage points of traffic into a handful of companies. Cheer for that, I guess. When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.
••••••••••••••••••••
Average age of a CEO is still 61, lots of olds to go "running the day to day". https://www.kornferry.com/insights/this-week-in-leadership/the-graying-corner-office - Despite millennials now surpassing baby boomers as the largest cohort in the workplace, CEOs are only getting older. Since the turn of the new century, the average age of CEOs in the United States has increased by ten years, to 61. Executives are starting in the top job later in life as well. And while some firms appear to be turning to younger leaders, the average age at which CEOs are appointed continues to rise, to 55, up from just 48 in 2000, according to a new working paper from the National Bureau of Economic Research. - Experts believe that the age jump reflects companies’ belief that complexities such as AI and constant geopolitical issues require a veteran hand. Boards want someone with a proven track record. They’re desperate for leaders who can get their organizations to perform at a top level—ideally, while also transforming and innovating, says Jane Edison Stevenson, global vice chair of Korn Ferry’s Board and CEO Services practice. “It’s the smallest candidate pool that I can remember,” she notes. - The paper looked at 50,000 CEOs at firms of all sizes from 2000 to 2023. The average CEO age has accelerated far faster, over the same period of time, than the age of the average US worker—which has gone up by only two years, from 40 to 42. The aging CEO trend is most pronounced among smaller private firms, according to the paper. Larger companies are offering internal candidates a wider range of assignments. Smaller companies value experience, the paper states, and it’s why many of them are willing to wait to hire older top executives.
••••••••••••••••••••••••••••••••••••••••••••••
 Top