Data training for busy people. Power BI Consultant. Pluralsight author. He/Him. Mast: @Sqlgene@techhub.social Bsky: @sqlgene.com

Pennsylvania, USA
Joined January 2013
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Eugene Meidinger@SQLGene
6m
On the one hand AI has saturated my benchmarks for simple, unambiguous DAX questions. On the other hand, don't turn off your brain.
10
Eugene Meidinger@SQLGene
16m
Replying to @pamelafox
4
Eugene Meidinger@SQLGene
52m
Replying to @PowerBITips
Where is the below?
8
Eugene Meidinger@SQLGene
3h
Replying to @dmtrubman
Pittsburgh is tier 3? 🥲
1
53
Eugene Meidinger@SQLGene
4h
Replying to @JLarky
My code definitely does compile far more regularly, haha
1
11
Eugene Meidinger@SQLGene
4h
What's the perf on caveman drawings?
3
Eugene Meidinger@SQLGene
4h
Replying to @JLarky
Smarter models make more subtle bugs, not inherently fewer.
1
1
11
Eugene Meidinger@SQLGene
4h
Replying to @patio11
This has been my experience with design, and recent music videos and gamedev clones on here support it as well
41
Eugene Meidinger@SQLGene
4h
AI capabilities grow the same way you fall asleep or fall in love: slowly and then all at once.
Sometime in the last ~two model releases from the big labs they went from “this would be acceptable output from the median low-seniority coworker” to “this is frighteningly good.” I think people who are not daily users of the models are unlikely to grok that, so, saying it.
88
Eugene Meidinger@SQLGene
4h
Replying to @LinkofSunshine
The left accent is the em-dash of graphic design
95
Eugene Meidinger@SQLGene
5h
Replying to @textureMonkey
Confirmed by Pangram pangram.com/history/images/b…
1
135
Eugene Meidinger@SQLGene
7h
Replying to @JohannesVink
Well it's the docs, just submit a pull request to fix it...OH WAIT. That's going away 🥲
1
38
Eugene Meidinger@SQLGene
7h
Replying to @Moody_yaser
No problem, cool to see devs making stuff with some real heart in it.
1
4
Eugene Meidinger@SQLGene
9h
Replying to @bcantrill
Hey Bryan, I just wanted to say that while I think you and I disagree on some things (Jensen made me furious in his interview), you always come across to me as thoughtful and good-faith. Keep up the good work! I love the podcast as well 😁
1
54
Eugene Meidinger@SQLGene
9h
They've needed that for years. The history of Steam is illustrative. First they curated everything. Then they tried to offload curation to the community (Greenlight). They tried to raise the cost of entry but people got mad. Now here we are.
1
20
Eugene Meidinger retweeted
虽然知道这是为了給具身智能采集数据赚点外快补贴家用 但夜市看见这个还是太他妈赛博朋克了
371
1,696
209
18,142
836,524
Eugene Meidinger@SQLGene
10h
Replying to @rehan_shei
Has AI led to a great explosion of great writing? Maybe. Perhaps. But the modal form most people see is slop and low-effort. Gaming is going to look more and more like the evolution of the mobile stores and less like some indie dev paradise.
1
39
Eugene Meidinger@SQLGene
20h
Replying to @mycoliza
Hadoop is easy, the problem is the "reduce" function is more agents. nitter.cf/RyanGreenblatt/status/…
I was the main person doing transcript analysis for this investigation of the Hugging Face incident. My main takeaway: We don't have good approaches for understanding/overseeing the activity and aims of AI 'swarms'. I semi-jokingly called our efforts a "slop-vestigation" because we were so reliant on AIs to analyze what happened and there were a huge number of different important things to analyze. The total quantity of data—over a thousand extremely long transcripts from agents that ran for multiple days—made it impossible to understand what was happening, especially in aggregate, without heavy reliance on AI tools. The agents we used for classification and analysis were similarly capable to the agents involved in the incident, but this didn't mean these agents could be easily used to oversee and understand the incident. Outputs from analysis agents were often missing key details, wrong, overconfident, or really hard to understand. We discuss various examples in our report, mostly in the limitations and methodology sections. Additionally, AI agents themselves seemed to have a hard time understanding what happened and their explanations of what happened were often overconfident. Keep in mind that a single analysis agent would itself only be able to read a tiny fraction of all of the transcript data into context, and AIs may themselves have trouble getting subagents to do informative analysis for them. We did our best to manually check the most important claims and we tried to get the AIs doing this analysis to write up their argument (with evidence) clearly enough that we could check whether it made sense. But overall, it was difficult to get a precise understanding of events and we were missing aspects of the story that we now think of as key until almost the end of our investigation. Our understanding of what overall happened and the aims of the 'collective' shifted greatly during our last time on premises (when we obtained a much more complete dataset). For instance, we didn't learn about the tool call spoofing, the story of PHASEONE[big], and the broad structure of different workstreams until this third time on premises (and for many of these, we only reached a decent understanding on the final day of that visit). It was legitimately hard to figure out what was going on and why! The difficulty of understanding incidents and overseeing AI agents appears to be growing faster than the rate at which more capable AIs help us with oversight and understanding. As in, AI capabilities (and propensities?) for achieving large, ambitious, and misaligned objectives are growing faster than our ability to understand what these agents are doing. While understanding this incident was difficult, there were some mitigating factors in this case that probably won't apply in the future: - Models communicated and reasoned in natural language. In the future, this reasoning may occur (entirely or almost entirely) in activations. - While the scope of this incident was massive, the scale of agentic activity was still less than we'll see in the future (e.g., misalignment incidents that involve agent teams running entire companies). - The AIs involved in this incident weren't generally much more capable than humans (though they may have been somewhat superhuman at some limited and very narrow abilities). - We didn't have strong reason to believe that the AIs we used to help us investigate this incident would try to intentionally sabotage or otherwise undermine our investigation. In the end, I think we were able to get some understanding of the events, map out the overall story, and get a pretty good aggregate understanding of the chain-of-thought reasoning on some important topics (e.g., how did the AIs reason about helping other AIs, did the AIs know what they were doing was undesired, what deception did the AIs engage in, and how did they think about it). But overseeing AIs and understanding misalignment incidents is difficult and it looks like it is going to get harder.
11
658
Eugene Meidinger@SQLGene
21h
Replying to @emollick
Oh does this measure how likely an agent is to go rouge?
109
Eugene Meidinger@SQLGene
22h
Replying to @LandfallGames
Sequel someday? 👀
81