[dfsegoat]

You mean during the intro / "more hands on period"?

I've not heard any negative feedback, but I think it requires a 'fine touch' - or you risk drowning people in information / tedium. If they get things the first time, I won't be prone to checking up on them as much.

[brailsafe]

Ya, that's what I meant. If I started at a company and my manager micromanaged me—especially with no clear reason why—I'd feel like this company isn't for me. No negative feedback isn't terribly surprising given that I don't know anyone besides myself inclined to actually say anything about an issue. Out of curiosity though, have you ever received negative feedback about anything, or given it yourself explicity before being more "hands-on"?

[dfsegoat]

I totally get where you are coming from. I should clarify that historically, all of my new hires were pretty much fresh out of school, or transitioning to software dev from other roles.

If I hired a dev with significant experience, I don't think I would use the same process, aside from knowledge gaps.

I definitely have received negative feedback on processes that are in place, and I welcome that, because if something can be done better, or more efficiently - then we should change it. Flexibility is key.