Help with micromanaging lead developer!
I'm a fairly young programmer (23 to be exact) who has a fairly old programmer (age wise) as a lead programmer. We decided to create a new system (custom) for some of our clients. So we started on this new system, got some foundations laid, for a schema created, all that fun stuff. Then I spent two days working on a foundation (I was told to do it using OOP) so I decided I would start with a nice DI and IoC system using a package manager. And all was going well, until he wanted to review it.
Pretty much he told me to delete it entirely and start over, giving no explanation as to why besides that it overcomplicated stuff. So I said okay, I didn't have a problem doing that. So we spent a few days talking about how to he wants to do things. So that worked fine, I spent the day working on that system. Now I sent him my code and he told me basically I needed to change it.
I used namespaces according to PSR-0. I was told not to.
I put my files in a nice organized directory (/Namespace/Class.php) I was told not to, I was told to change them from that to a single directory and add .class.php to the end
I wanted to use PDO. I was told to use his convoluted mysqli wrapper that as far as I am concerned is terrible.
I wanted to at least clean up his mysqli wrapper. I was told not to touch it as it works.
Now I don't mind following directions. But I'm having a real hard time with a few things.
The deadline is going to be impossible to reach with him micromanaging my file names.
I'm not following a single recommended OOP approach. And when asked why we are not doing simple things like following PSR-0 or what not. I get a blanket "overcomplicates things".
Every single thing I do is in his eyes wrong.
I find it difficult to code in what I would consider an old fashion.
Really I just want a solid reason, "overcomplicating" things as far as I am considered is not a reason. It's simply the fact the lead does not want to learn anything new.
I'm not sure how to deal with this, I've never had such a wall of a lead developer before.
I'm a fairly young programmer (23 to be exact) who has a fairly old programmer (age wise) as a lead programmer. We decided to create a new system (custom) for some of our clients. So we started on this new system, got some foundations laid, for a schema created, all that fun stuff. Then I spent two days working on a foundation (I was told to do it using OOP) so I decided I would start with a nice DI and IoC system using a package manager. And all was going well, until he wanted to review it.
Pretty much he told me to delete it entirely and start over, giving no explanation as to why besides that it overcomplicated stuff. So I said okay, I didn't have a problem doing that. So we spent a few days talking about how to he wants to do things. So that worked fine, I spent the day working on that system. Now I sent him my code and he told me basically I needed to change it.
I used namespaces according to PSR-0. I was told not to.
I put my files in a nice organized directory (/Namespace/Class.php) I was told not to, I was told to change them from that to a single directory and add .class.php to the end
I wanted to use PDO. I was told to use his convoluted mysqli wrapper that as far as I am concerned is terrible.
I wanted to at least clean up his mysqli wrapper. I was told not to touch it as it works.
Now I don't mind following directions. But I'm having a real hard time with a few things.
The deadline is going to be impossible to reach with him micromanaging my file names.
I'm not following a single recommended OOP approach. And when asked why we are not doing simple things like following PSR-0 or what not. I get a blanket "overcomplicates things".
Every single thing I do is in his eyes wrong.
I find it difficult to code in what I would consider an old fashion.
Really I just want a solid reason, "overcomplicating" things as far as I am considered is not a reason. It's simply the fact the lead does not want to learn anything new.
I'm not sure how to deal with this, I've never had such a wall of a lead developer before.
No comments:
Post a Comment