Receiving conflicting messages from people in leadership roles
So I am less than a month in to a wonderful new job and I will get right to the point. From day one the CTO has told me to please poke holes and look for inconsistencies and what needs improvement.
On my first and second week, it was too early to find any, but on my third week I have found something.
Well, now I am meeting with the Senior Developer more so than the CTO and so I brought these inconsistencies up with him.
The response I get is, well, the client is not worried about that and we are moving away from that technology anyways.
The piece that I need to also disclose is that its a piece of technology I have spent countless hours mastering and also implementing in other companies and for other customers and so the philosophy that we are replacing it with something better and new falls short of the fact that its not going to completely go away so it behooves us to all learn it, especially for devs that come after me.
Anyway, my question is, what is the best way to address this in a way that I safeguard myself as the new guy and I am not throwing the Senior Dev under the bus?
I could have made the argument and may possibly still have the chance to make the argument to the Senior Dev, that it affects my productivity when I look at a codebase that is unnecessarily disorganized and snippets of code here and there implemented in the past that for someone of my experience, I know are not providing any improved quality to the product.
How do I communicate the inconsistencies and mediocrity without coming off like, "oh you are okay with mediocre code?" I wasn't thinking this as I respect my colleagues, but one can come off this way if one is not careful.
communication productivity
asked 19 mins ago
DanielDaniel
344110
add a comment |
So I am less than a month in to a wonderful new job and I will get right to the point. From day one the CTO has told me to please poke holes and look for inconsistencies and what needs improvement.
On my first and second week, it was too early to find any, but on my third week I have found something.
Well, now I am meeting with the Senior Developer more so than the CTO and so I brought these inconsistencies up with him.
The response I get is, well, the client is not worried about that and we are moving away from that technology anyways.
The piece that I need to also disclose is that its a piece of technology I have spent countless hours mastering and also implementing in other companies and for other customers and so the philosophy that we are replacing it with something better and new falls short of the fact that its not going to completely go away so it behooves us to all learn it, especially for devs that come after me.
Anyway, my question is, what is the best way to address this in a way that I safeguard myself as the new guy and I am not throwing the Senior Dev under the bus?
I could have made the argument and may possibly still have the chance to make the argument to the Senior Dev, that it affects my productivity when I look at a codebase that is unnecessarily disorganized and snippets of code here and there implemented in the past that for someone of my experience, I know are not providing any improved quality to the product.
How do I communicate the inconsistencies and mediocrity without coming off like, "oh you are okay with mediocre code?" I wasn't thinking this as I respect my colleagues, but one can come off this way if one is not careful.
communication productivity
asked 19 mins ago
DanielDaniel
344110
add a comment |
So I am less than a month in to a wonderful new job and I will get right to the point. From day one the CTO has told me to please poke holes and look for inconsistencies and what needs improvement.
On my first and second week, it was too early to find any, but on my third week I have found something.
Well, now I am meeting with the Senior Developer more so than the CTO and so I brought these inconsistencies up with him.
The response I get is, well, the client is not worried about that and we are moving away from that technology anyways.
The piece that I need to also disclose is that its a piece of technology I have spent countless hours mastering and also implementing in other companies and for other customers and so the philosophy that we are replacing it with something better and new falls short of the fact that its not going to completely go away so it behooves us to all learn it, especially for devs that come after me.
Anyway, my question is, what is the best way to address this in a way that I safeguard myself as the new guy and I am not throwing the Senior Dev under the bus?
I could have made the argument and may possibly still have the chance to make the argument to the Senior Dev, that it affects my productivity when I look at a codebase that is unnecessarily disorganized and snippets of code here and there implemented in the past that for someone of my experience, I know are not providing any improved quality to the product.
How do I communicate the inconsistencies and mediocrity without coming off like, "oh you are okay with mediocre code?" I wasn't thinking this as I respect my colleagues, but one can come off this way if one is not careful.
communication productivity
asked 19 mins ago
DanielDaniel
344110
So I am less than a month in to a wonderful new job and I will get right to the point. From day one the CTO has told me to please poke holes and look for inconsistencies and what needs improvement.
On my first and second week, it was too early to find any, but on my third week I have found something.
Well, now I am meeting with the Senior Developer more so than the CTO and so I brought these inconsistencies up with him.
The response I get is, well, the client is not worried about that and we are moving away from that technology anyways.
The piece that I need to also disclose is that its a piece of technology I have spent countless hours mastering and also implementing in other companies and for other customers and so the philosophy that we are replacing it with something better and new falls short of the fact that its not going to completely go away so it behooves us to all learn it, especially for devs that come after me.
Anyway, my question is, what is the best way to address this in a way that I safeguard myself as the new guy and I am not throwing the Senior Dev under the bus?
I could have made the argument and may possibly still have the chance to make the argument to the Senior Dev, that it affects my productivity when I look at a codebase that is unnecessarily disorganized and snippets of code here and there implemented in the past that for someone of my experience, I know are not providing any improved quality to the product.
How do I communicate the inconsistencies and mediocrity without coming off like, "oh you are okay with mediocre code?" I wasn't thinking this as I respect my colleagues, but one can come off this way if one is not careful.
communication productivity
communication productivity
asked 19 mins ago
DanielDaniel
344110
asked 19 mins ago
DanielDaniel
344110
asked 19 mins ago
DanielDaniel
344110
asked 19 mins ago
DanielDaniel
344110
asked 19 mins ago
DanielDaniel
344110
344110
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f127604%2freceiving-conflicting-messages-from-people-in-leadership-roles%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f127604%2freceiving-conflicting-messages-from-people-in-leadership-roles%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
