作为IC, 可以对不喜欢的task说不么？

zli_test 发表于 2019-1-31 12:36
Most of the replied/comments are too simple, sometimes naive :).  You all heard this: wherever there ...

Thank you very much for your long reply. I really appreciate it. I tried to communicate with my TL and he did not give me the reason for doing e2e test now. He just told me he planned to do it but all other programmers in the team are still doing development. I totally agree that developers should do the tests by themselves and that is the reason why I was doing this when I was first assigned to the task. Things went off track after that. My TL seemed to bind me to the test work while I was thinking to rotate back to development for some time. He created a bunch of tasks and assigned to me. So I will be working for testing in the next few weeks or months depends on how it goes. From his point of view, I may be more familiar with the test set up but I am also familiar with the development (I did my own research and made the implementation plan for quite a lot of features which I did the POC by myself. So I think I am the right person to turn those POC to production code). In contrast, my TL de-prioritized those features (those are very basic features like fail over or error handling). That is the reason why I think it is not a good time to do the e2e test now. For the mock data, we have a work around so it is ok for now. The time we really need it is when we deploy the code in beta at least and we would like to put the A/B test as automated regression. I think at that time, we will have more support to generate those data for sure. The last thing I was worried about is the timing. As I said, I estimated the task (generating mock data) will take at least a month while my TL thinks it is only two weeks. We discussed it in today's meeting and other team member also agreed with me. But that was towards the end of the meeting so my TL did not give the conclusion. I planned to talk to him tomorrow and I would like to know if the reason above is solid.
Thanks again for your input. I really like the way you analyzed. It really helps me to prepare my talk with my TL.

hotinherre 发表于 2019-1-31 12:56
如果想久呆， 那就忍辱负重， 和领导多沟通，和同事处理好关系，下次机会会轮到你。

如果决定要走， 就 ...

谢谢，不想久呆，所以以前一直忍着。但是最近被教育说各个公司其实都一样，所以才想着能不能有理有据的抗争一次。滑水很难，因为sprint结束要拿出东西来，这个假不了。除非两星期之后就不干了，不然躲不过去啊

认识一位大佬， 被VC请去给俩MIT Dropout 写的辣鸡做QA。他老人家把东西整明白，调顺。 成了CTO。最后俩小子被赶走。 公司卖给Intel 。捞到他的第一桶金。
不一定有普遍性， 有时 是金子当QA都能发光。

lluo0204 发表于 2019-1-31 12:11
哈哈哈，果然是一模一样啊，我这也使单元测试都没有，出了问题根本找不到，又不是我写的代码
请问你当时 ...

我是有一段时间效率很低不怎么干活，然后tech lead 跟我谈话，说让我做一个大数据相关的项目（跟我的专业相关的），然后说理解我最近没什么热情。 我就说感谢理解。 我觉得如果他们既然测试这么不规范，其实就并不是很重视测试的严格度，你就跟老板说一下大家写个QA TODO list, 然后轮流做QA, 我觉得老板也能接受。 更关键的是你要跟他说这个测试的任务尽管你理解，但是应该大家分担，你的背景不是QA, 职业发展也不是QA, 你要做一些能不能跟你专业相关的，让你有激情的项目。实在不行自己想项目，然后问老板让不让你做。

lluo0204 发表于 2019-1-31 12:09
谢谢，我也这么认为。我现在在搭e2e test的基本框架吧，然后做一些最基本的测试，发现很多问题，然后也不 ...

补充一点，研究e2e 测试是挺不错，但是要有人带，自己搞容易陷入误区。也看到前面有人建议这是个学习机会，是没错，但是如果有办法通过谈话换项目，还是要试一下的，不然你测试研究的越深，别人越叫你做测试，然后测出的毛病别的工程师还爱改不改，你即得罪人又没impact。

Scala688 发表于 2019-1-31 13:43
认识一位大佬， 被VC请去给俩MIT Dropout 写的辣鸡做QA。他老人家把东西整明白，调顺。 成了CTO。最后俩小 ...

这个故事没有普遍性啊， 还有他老人家怎么就从QA到CTO的，分了几步，怎么走的？

qizhong19920114 发表于 2019-1-31 17:35
这个故事没有普遍性啊， 还有他老人家怎么就从QA到CTO的，分了几步，怎么走的？

大佬已经在别的公司有辈分， 受VC朋友委托。真的以QA Lead出场， 因为俩小子持柴傲物。不把任何人放在眼里， 他们的CORE只在他们的机器上时不时可以run。 老兄花了半年一行行读代码。 不齿下问。 终于在TESTIng Lab里可以跑起来了。
以后谁有问题都找他解释。 俩小子也乐得清闲。 最后产品上线公司扩张。 Drop out 拒绝合作。 被赶走。 他老人家从QA Manager正式登位CTO
当然他老人家功力了得还放得下身段。

zli_test 发表于 2019-1-31 12:36
Most of the replied/comments are too simple, sometimes naive :).  You all heard this: wherever there ...

楼主答的很棒。
有个英文上的小纰漏，我之前也不是很清楚，正好借此机会查资料弄明白了。
就是communicate with和communicate to之间的区别。
如果是表示和别人交流用作intransitive verb的话，应该是communicate with。
但要是用作transitive verb，等同于convey意思的时候，应该是用communicate to。

lluo0204 发表于 2019-1-30 20:30
谢谢，楼主是打算走的，不过还在准备中，也许这个就是给我跳槽的动力吧

有动力挺好的。我也是受了很多苦，才知道自己想要什么，才发愤图强。。

如果入门就在FG可能就不会有这么深的感悟。