p4ul

This is an excellent book! We give a copy to everyone that joins our team.

Be careful, you're in danger of anthropomorphizing the lawnmower. [1]

[1] https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2308s

My understanding is that this an essential component of their "Chronicles" database system. I'd be curious to hear more recent perspectives.

Thanks for your comments, @chaboud! I definitely agree that LLMs _can_ be an amazing tool for learning, but as you note, one must be intentional about using them that way. I feel like the messages being pushed down from leadership are NOT of the form "Use AI to learn topics deeply and discover new things." The leadership's perspective is more like "Use all the AI you can to ship as fast as you can."

Your comment about programming historically being 1% judgement and 99% effort is interesting. I'm not sure I agree with those exact percentages, but nonetheless, I think the more consequential part of your comment is that the 99% is being reduced by a couple of orders of magnitude. I think that's what ought to trouble us as software engineers. Expending effort is often how we learn and grow. This is true in the context of physical activity (e.g., going to the gym to strengthen muscles) as well as in the context of intellectual activity (e.g., struggling through a problem set). If I go to the gym with my forklift, I can lift things, but I'm not likely to get stronger. Similarly, if I have Claude write all my code, I'm probably not learning much.

> The work that’s left is more interesting and more valuable than the work that’s leaving.

I'm not sure I agree with that. Many (or most) of the software engineers I know find the heavy reliance on AI coding agents/assistants pretty soul-sucking and uninteresting. I feel the same, and I'm looking for some kind of middle ground. For example, I will only use agents when doing so would not deprive me of learning and discovery.

Oh, thank you, @clmcleod! We've been following all your work closely in my team!

I'm very bullish on the long-term prospects of Rust in computational biology—as well as research computing more generally.

This is interesting; thanks for sharing! I have been curious about the adoption of Rust in computational biology. I know that the folks at Saint Jude's [1] are also using Rust for their 'omics research.

[1] https://github.com/stjude-rust-labs

I'm very curious to hear folks' thoughts on this. My intuition is that there are at least two key factors that make tasks difficult for AI tools.

(1.) The overall level of complexity. For example, I think (today) you would need to do an extreme amount of hand-holding to get an AI to write a browser, an OS, or anything with similarly very high level of complexity.

(2.) The representation in the AI's training set. Anything that is common in the training set (e.g., to-do app in JavaScript) will be trivial for an AI to one-shot. Anything that is rare, or absent in the training set is going to be much, much harder for the AI. If I try to ask an AI tool to develop a automated, ultra-low-latency high-frequency trading system, it's probably going to struggle because those kinds of applications aren't in the open-source domain. The same is true for completely novel algorithms. So maybe things that are essentially new science/engineering.

I'm very curious to hear others' thoughts on this, as I've been wondering about this, too.

This might not be exactly what you mean by a CLI app called "whatisthis", but I have been using cheat.sh and the pattern below for a few years. It works really well!

curl cheat.sh/grep # fetches brief grep cheat sheet

I'm sorry if you've had a bad experience working with cloud technologies, but this comparison strikes me as pretty unfair.

Public clouds have enabled thousands of companies to put their products into the world without having to build and maintain hardware. They've completely changed the landscape of computing.

If you haven't written off Python completely, I would suggest giving it a second chance using uv [1] for managing environments and Python versions. In my opinion, uv is the best thing to happen to Python in 10 years.

[1] https://docs.astral.sh/uv/

I agree with this, and I'd go even a bit further and describe them as predatory. They seem to have absolute contempt for their customers, and look for every possible opportunity to bleed them dry.

But then again, I'm probably guilty of anthropomorphizing the lawnmower. [1]

[1] https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2308s

I had the same reaction. Haven't they been selling DGX boxes for almost 10 years now? And they've been selling the rack-scale NVL72 beast for probably a few years.[1]

What is changing?

[1] https://www.nvidia.com/en-us/data-center/gb200-nvl72/

It's interesting that you mention disaster; there is at least one annual conference dedicated to "spreadsheet risk management".[1]

[1] https://eusprig.org/

Yep, and don't forget about Mojo, which has the potential to make such a transition less painful.

I wish this was better understood more broadly. Grants aren't no-strings-attached gifts—far from it; they are contracts.

When a researcher at a university gets a grant, that's the federal government hiring that researcher and their team to complete a specific research project. The research team has a particular research question that the federal government has deemed important enough that U.S. tax payers would benefit from getting an answer.

Yeah, I am very curious to see the responses from other institutions. The University of Texas (Austin) said they were "honored" to have received the compact.[1] That is obviously very concerning.

[1] https://www.chronicle.com/article/the-white-house-sent-its-c...

I feel like "other than the ecosystem" is doing quite a bit of work here.

This has been exactly my experience! I've found SQLx to be a joy to work with in Rust!

Your understanding is correct, dbeaver is a stand-alone application.

If the conclusion is "be transparent", I'm strongly supportive.

And moreover, I would be even more supportive if we found a way to change the incentives for tenure and promotion such that reproducibility was an important factor in how we make decisions about grants, tenure, and promotion.

I agree, but with one amendment: most tenure-track roles in the US will have 50 to 200 applicants for a single position. Over the last few decades, tenure lines have decreased while PhD admissions have not. Adjuncts do so much of the teaching at all kinds of institutions these days.

I strongly agree with this sentiment. And I realize that we might not be the representative of the typical user, but nonetheless, I think these things definitely matter for some subset of users.

I agree; this is incredibly short-sighted. And it has the potential to be catastrophic for scientific progress in the United States.

Scientific innovation happens because countries invest in basic and applied research. This research largely happens at research universities, hospitals, and national labs. If research universities can't afford to conduct research, the scientific innovation—along with the training of the next generation of scientists—all grinds to a halt.

"Do not fall into the trap of anthropomorphizing Larry Ellison." [1].

[1.] https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2308s

This is one kind of macro in Rust: declarative macros [1]. The other kind of macros in Rust are procedural macros [2]. Both are widely used in idiomatic Rust. And even within the procedural type of macros, there are different categories of macros (i.e., function-, or attribute-like macros).

[1] https://doc.rust-lang.org/book/ch19-06-macros.html

[2] https://doc.rust-lang.org/book/ch19-06-macros.html#procedura...

With all the overdose deaths and the lives ruined by opioids, I guess I'm a little bit surprised this didn't result in criminal charges for someone at McKinsey. Surely there must be some emails or texts that are inculpating.