![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Last night I was explaining a bit of my new job to ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
rfrench. I said "They're going to have me do Thing A first, but I'm not sure I understand why yet. It seems to me I should do Thing B first instead. Having Thing B first will give us more capabilities and [bla bla bla lots of good stuff]. And hey, I don't know how to do either one yet, so it's not like changing the plan will slow me down."
I mentioned it to the CEO, Acting VPE and Product Manager, and Chief Architect. Chief Architect said hey, that might be right. Other two said waitaminit, we're not so sure, let's think about it. We all sat in a conference room for twenty minutes.
I'm doing Thing B first.
It is so weird to work at a job where my input is even considered and discussed, much less gets chosen. I am waiting for the other (the first?) shoe to drop.
rfrench. I said "They're going to have me do Thing A first, but I'm not sure I understand why yet. It seems to me I should do Thing B first instead. Having Thing B first will give us more capabilities and [bla bla bla lots of good stuff]. And hey, I don't know how to do either one yet, so it's not like changing the plan will slow me down."I mentioned it to the CEO, Acting VPE and Product Manager, and Chief Architect. Chief Architect said hey, that might be right. Other two said waitaminit, we're not so sure, let's think about it. We all sat in a conference room for twenty minutes.
I'm doing Thing B first.
It is so weird to work at a job where my input is even considered and discussed, much less gets chosen. I am waiting for the other (the first?) shoe to drop.
