I mean, the post was written by a Stanford CS lab, so I'm inclined to believe that they know what they're talking about and are not just bad at creating abstractions.

▲

rryan 2 hours ago | parent | next [-]

I know nothing about the PhD candidate and professor who co-authored this, but I don't think this statement makes sense in general.

Typically CS labs at universities contain people who have not spent a significant amount of time exposed to large industry codebases and the corresponding complexity. I think the post would have more credibility coming from e.g. the platforms team at a tech company with a monorepo.

▲

jrflo 2 hours ago | parent | next [-]

There is something to be argued about industry vs academic experience but this post has nothing to do with large industry codebases

	▲	rryan 5 minutes ago \| parent \| next [-]
		Disagree. The abstractions they are talking about aren't like, the y-combinator. They're talking about boring software engineering abstractions.
	▲	raddan an hour ago \| parent \| prev [-]
		Well, they’re also probably not scaling up in the same way as any of the commercial AI offerings, let alone the frontier labs. Faculty at Stanford probably have some decent hardware to play with, but they do not have data centers. I don’t doubt that they know their way around CUDA/PTX, but it’s not clear how relevant their message is given that their research code is very likely not being deployed in production, or at scale.

▲

JMiao an hour ago | parent | prev [-]

sounds like it might help to know something about the phd candidate and professor

	▲	rryan 2 minutes ago \| parent [-]
		Heh, not really

▲

vatsachak 2 hours ago | parent | prev | next [-]

The machine learning community decided to choose Python as the main language, which costs probably tens of millions of dollars in bugs every year due to it not being type checked (astral sh is fixing this though)

▲

raddan an hour ago | parent [-]

Hasn’t mypy been a thing for years already?

The main problem with Python is that, if you’re not doing your work in highly optimized numeric libraries (which are usually written in C), then you’re paying terrible overheads to use the Python interpreter. Type checking doesn’t help with this because Python is dynamically typed but static types could in principle. Is that what you mean?

	▲	vatsachak an hour ago \| parent [-]
		I mean yes the python interpreter is not great, but I'm talking about bugs created by accidentally passing a negative number where a positive one should go, using a tensor of the wrong size etc. I don't have any ml experience with python only numerical libraries and I always have to be careful what I'm doing otherwise an experiment can go Kaput. Types stop that.

▲

2 hours ago | parent | prev | next [-]

[deleted]

▲

nostrebored 3 hours ago | parent | prev [-]

why?

▲

jrflo 2 hours ago | parent [-]

I think it's generally fair to assume that you don't become a Stanford CS professor by being bad at writing code and creating abstractions, and that the average professor (let alone one at a prestigious university) is more knowledgable than your average HN commentor

	▲	nostrebored an hour ago \| parent [-]
		Professors have no reputation for writing good code. Academic code is fairly notorious for being under abstracted, hard to follow, messy, etc. If a passerby told me this story I’d have the same guess though!