I think that would probably trigger my problematic code consideration. I'm not saying it won't slow you down on some projects, only that clean projects should benefit.
Though, even here, how long did it slow you down for. Do you think the junior won't contribute more overall than the time you invested?
In this case, it wasn't too bad because:
In this case, most of the loss of velocity came from things like the adjustment to React and explaining the downright awful application structure. It was definitely worth bringing in someone else - it'd take me a lot more time and hassle to do a much crappier job of the front end.
However, if it had been a case of bringing in another back-end developer to work on similar tasks to me, I'd have had to spend a lot of time explaining what I could, going through the awful parts of the code base, and avoiding stepping on each other's toes.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.