I just had to transfer one of my guys out after frequent arguments to do that. I don’t understand - I point out a function that does exactly why he wants, yet he still wants to reinvent it.
I’m dreading when I come back after break. I got 50% a new junior guy who keeps saying he’s a great programmer. No sign of it so far but my management insists I take him on. All he needs to do is expose a new endpoint, wire up functionality that’s already there, and I walked him through it. Should be easy, right? No reinventing the wheel, right?
I do know the feel. I was young once (seems a long long time ago). Reinventing the wheel was fun and challenging. I loved creating libraries. I didn’t actually know at the time that there were already existing libraries I could just use, this was the 90s. But it is hard to keep track of what library code exists in a project if you didn’t write it. Maybe assign them to review the library code and document it or something. Then they will know what it is at least.
I just had to transfer one of my guys out after frequent arguments to do that. I don’t understand - I point out a function that does exactly why he wants, yet he still wants to reinvent it.
I’m dreading when I come back after break. I got 50% a new junior guy who keeps saying he’s a great programmer. No sign of it so far but my management insists I take him on. All he needs to do is expose a new endpoint, wire up functionality that’s already there, and I walked him through it. Should be easy, right? No reinventing the wheel, right?
I do know the feel. I was young once (seems a long long time ago). Reinventing the wheel was fun and challenging. I loved creating libraries. I didn’t actually know at the time that there were already existing libraries I could just use, this was the 90s. But it is hard to keep track of what library code exists in a project if you didn’t write it. Maybe assign them to review the library code and document it or something. Then they will know what it is at least.