rewording: what job position typically owns or manages those types of tools/processes?

@Gilean Developers themselves are typically responsible for both. A team lead can help facilitate code reviews, but generally it's up to the devs to organize themselves.

@AnnaLear what about first introducing it, maintaining the tools etc? is there typically a position for it?

@Gilean I've never seen anybody hired just to introduce that sort of stuff in a company. Although if the company were transitioning into agile development and brought it an agile coach, he or she would probably drive both unit testing and code reviews. Other than that, all that's needed is a developer (or two or several) deciding to start doing unit testing/code reviews. For testing, it's not uncommon that someone would be appointed to do the initial research and then present it to the group.

@Gilean There may be someone on the team already familiar with the concepts who can help push for it. Code reviews really just require everyone to agree to do them and some agreement on the team on how they're going to be done. Similarly to unit testing, this can (and often is) evangelized by interested developers.

@Gilean It's not really a position-dependent thing. Anybody with the interest and the ability to win the necessary arguments can push testing and reviews through.

Hi Everyone

Hi, I'm trying to remember a quote about programming languages... It suggested that there are two (?) things every programming language needs to provide. One of them was "abstraction", i.e. a method for abstracting computations and reusing them. I don't remember what the other one was. This was either in an intro chapter on some famous book, or possibly in a famous paper. Anyone know what I mean?