blocks|key|4926830|text|你不应该在你的高年级学生看到它之前，就认为自己已经完成了。拒绝应该发生在设计的时候。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4926831|然后出现了一个问题，那就是它是否可以被重新分解成可以接受的东西。如果是第一个，那就去做吧。如果是后者，你需要和你的老板讨论如何在未来避免这种情况。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

You should never have reached the point where you consider yourself finished, before your seniors see it. The rejection should have happened at design-time.

Then comes the question if it can be refactored into something acceptable or not. If the first, then just do it. If the latter, you need to discuss with your boss how this situation can be avoided in the future.

blocks|key|4926784|text|如果有人拒绝了你做的好事，你该怎么做？|type|blockquote|depth|inlineStyleRanges|entityRanges|data|4926785|在进行更多的编码之前，请询问验收标准。|unstyled|4926786|这个特性的范围应该是什么？|unordered-list-item|4926787|哪些工具和语言是可以接受的(即可以使用ExtJS)？|4926788|还有哪些其他约束(支持的浏览器、代码大小、.)？|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|P|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<blockquote>
 How should you proceed when somebody rejected a good thing you made?
</blockquote>

Ask for acceptance criteria before doing any more coding.

<ul>
<li>What should be the scope of this feature?</li>
<li>What tools and languages are acceptable (i.e. is it OK to use ExtJS)? </li>
<li>What other constraints are there (supported browsers, codesize, ...)?</li>
</ul>

blocks|key|1185875|text|和高级人员谈谈为什么你的项目不合适，以及他们希望你下次做什么不同的事情。采取的态度是，无论它是多么好，它是不合适的。不要对抗性。项目被拒绝是痛苦的，但学习下次该做什么比和可能有理由拒绝它的人争论要有建设性得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185876|您还可以询问代码质量。具体一点:选择一个特定的部分，并问为什么会这样。很可能是你不喜欢它的原因。|1185877|此外，尽量避免被视为一个没有经验的新人，他认为他知道一切都应该如何。了解事情是这样的原因。它们可能不是很好的理由，而且你可能不同意它们，但如果不具体解决这些问题，你就不会改变任何事情。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Talk to the senior people about why your project wasn't suitable and what they'd like you to do differently next time. Take the attitude that, however good it was, it wasn't suitable. Don't be confrontational about it. Having a project rejected is painful, but learning what to do next time is far more constructive than arguing about it with people who probably have reasons for rejecting it.

You can also ask about the code quality. Be specific: take a particular part and ask why it's that way. There may well be reasons for what you don't like about it.

Also, try to avoid being seen as the new guy without experience who thinks he knows how everything should be. Learn the reasons why things are the way they are. They may not be good reasons, and you may disagree with them, but you're not going to change anything without specifically addressing them.

blocks|key|4926743|text|ExtJS是一个相当大的库，对商业开发人员有许可证费用。我很惊讶你在你的解决方案中使用它之前没有事先得到批准。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4926744|你还写道：|4926745|我想重组代码，因为我的公司的编码结构很糟糕，我想改进这一点。|blockquote|4926746|这不是件容易的事。如果团队的其他成员认为没有问题，那么这可能是不可能的。在这种情况下，你要么必须适应，要么与一个更复杂的团队找到一个新的职位。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|L|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]]|I|$]]

ExtJS IS a pretty big library, and there is a license fee for commercial developers. I'm surprised you didn't get prior approval before using it in your solution. 

You also write:

<blockquote>
 I would like to restructure the code, as the coding structure in my company is very bad and I want to improve that.
</blockquote>

This will not be easy. If the rest of the team thinks there is no problem, then it is probably impossible. In that case you will either have to adapt or find a new position with a more sophisticated team.

blocks|key|1185803|text|认为这是一个比程序员更广泛的问题，但总的来说:如果您的团队负责人说他们有偏好(听起来他们更喜欢较小的代码)，那么就让您的代码符合他们的偏好。或者搬到一个和你一样工作的团队。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185804|通常，把它当作一种学习经验--让他们充分解释他们希望你做什么。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Think this is a much wider question than something relevant for programmers, but in general: if your team lead has said they have a preference (sounds like they prefer smaller code) then to proceed, make your code fit their preference. Or move to a team which works the same way you do.

Generally, treat it as a learning experience - get them to explain fully what they would prefer you to do.

blocks|key|1185854|text|在题目标题中，你建议你仍然认为你创造的是“好的”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185855|第一件事就是接受事实，不是因为我这么说，而是因为它被拒绝了。就像其他人一样，你需要学习。正如在其他答案中所述，在开始之前获取需求。当他们不接受你创造的东西时，问他们为什么，接受答案，修复它，然后再交付。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

In the title of the topic you suggest you still think that what you created is "good".

The first thing to do is to accept that it isn't. Not because I say so but because it has been rejected. Like everyone else you need to learn. As stated in other answers, get the requirements before you begin. When they do not accept the thing you made, ask them why, accept the answer, fix it and deliver again.

blocks|key|1185918|text|在我的第一份(和现在的)工作中，人们教会我的第一件事之一就是问问题，特别是在开始的时候。如果有人想让你做些什么，那么仔细问一问，当你有一个实现的想法时，不要犹豫，写一个简短的(没有人想逐页阅读，但半页通常是可以的)规范，并询问这是否可以。如果你认为的是好的，他们可能会留下深刻的印象，如果不是，他们可以告诉你之前，你所描述的情况发生。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

One of the first things people at my first (and current) job taught me is to ask, especially in the beginning. If someone wants you to do something, ask more closely and when you have an implementation idea, don't hesitate to write up a short (nobody wants to read pages upon pages, but half a page will usually be fine) spec and ask whether that is okay. If what you thought of is good, they might be impressed, if not they can tell you before the situation you describe happens.

blocks|key|4926758|text|我非常肯定，您并没有使用extjs中的所有内容。如果他们的借口是extjs是一个很长的文件，而且这个库很可能是由许多小函数组成的，那么将您正在使用的函数放到另一个文件中，然后带着新的解决方案(使用这个小文件)返回到您的老板那里。他们的借口没有道理。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|entityMap^0|C|5|W|5^^$0|@$1|2|3|4|5|6|7|G|8|@$9|H|A|I|B|C]|$9|J|A|K|B|C]]|D|@]|E|$]]]|F|$]]

I'm pretty sure that you're not using everything inside <code>extjs</code>. If their excuse is that <code>extjs</code> is a long file, and since the library is most probably structured in many small functions, put the functions that you're using in another file and go back to your bosses with your new solution (that uses the small file). Their excuse will not make sense.

blocks|key|1185900|text|如果你认为你有一个更好的方法做某事，证明它。提供确凿的证据证明你的解决方案在某种程度上是更好的。这可能是更快的加载时间、运行时性能、更高的内聚力、更低的耦合或任意数量的度量。您可能希望了解什么指标对您的团队或公司很重要，这样您就可以知道什么才是有说服力的论点。不管是什么，做个实验并产生一些数据。如果它使你错了，承认它并从经验中吸取教训。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

If you think you have a better way of doing something, prove it. Produce hard evidence that your solution is better in some way. That could be faster load times, runtime performance, higher cohesion, lower coupling, or any number of metrics. You might want to find out what metrics matter to your team or company so that you know what will make a convincing argument. Whatever it is, come up with an experiment and produce some data. And if it turns you're wrong, admit it and learn from the experience.

blocks|key|1185998|text|下一次，考虑执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185999|编写一份设计建议，概述您想要做什么、它将拥有哪些模块以及需要哪些外部依赖项。|unordered-list-item|1186000|一旦有了一个“好看”，写一个更详细的设计。|1186001|一旦得到了“继续”(“前进”比“好看”强)，编写你的应用程序，在整个过程中寻求反馈。|1186002|这给你在投入大量时间之前获得反馈的充分机会。它给你的高年级学生一个提供指导的机会，在你走上他们不赞成的道路之前。它还提供了多个点，其中有机会去“实际上，这会更好.”以及“我们不再需要这个了，对不起.”|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|M|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]]|K|$]]

Next time, consider doing the following:

<ul>
<li>Write a design proposal, outlining what you want to do, what modules it will have and what external dependencies are needed.</li>
<li>Once that has a "looks nice", write a more detailed design.</li>
<li>Once that's been given a "go ahead" (a "go ahead" is stronger than "looks nice"), write your application, seeking feedback through the process.</li>
</ul>

This gives you ample chance to get feedback before investing lots of time. It gives your seniors a chance to provide guidance, before you've gone down a track they won't approve of. It also provides multiple points where there's a chance to go "actually, this would be better..." as well as "we won't need this anymore, sorry..."

blocks|key|4926719|text|好吧，如果js文件的大小是个问题的话，我会检查您是否可以将它去掉一点，使它变小，从而使他们感到高兴。或者做一个真正的测试案例，让人们看到加载时间是正常的。之后，您还可以回来说：“顺便说一句，...I也有这个功能，而可用的...it只需要这么多kb。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Well, if only the size of the js file is an issue, I would check if you could somehow strip it down a little to make it smaller and thereby make them happy. Or make a real test case where people see that the loading time is ok. Afterwards, you could still come back and say "by the way ...I also have this and that feature available ...it just takes so and so many kb"

blocks|key|1185824|text|在您再浪费时间处理不可接受的解决方案之前，请请求最大的文件大小，如果您能够满足该要求，他们会接受您的解决方案吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185825|这是你的第一次，还是他们习惯于让你从事被拒绝的项目？|1185826|不幸的是，除非你能读心术，否则情况可能会变得更糟。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Before you waste anymore time working on unacceptable solutions, ask for the maximum file size and if you can meet that requirement, will they accept you solution.

Is this a first for you or are they in the habit of letting you work on projects that get rejected?

Unfortunately, it will probably get worse until you can read minds.

blocks|key|1185930|text|我做了一些在完成后被客户拒绝的项目。我感觉很糟糕，但是，由于没有什么可做的，最好的办法就是从经验中吸取教训，昂首阔步，相信自己，继续新的项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I made some projects which were rejected by client after finished. I felt bad, but, as there was nothing to do about, the best way to not feeling bad is to learn from the experience, hold your head high, trust yourself and go on on new projects.

blocks|key|1185838|text|您打算改进代码结构，但是您创建了一个文件，超过了最大接受量？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

You were going to improve the code structure, but you created a SINGLE file, that exceeds the maximum acceptance?

I made an application in extjs, and it was rejected by my technical architect, project manager, and team leader because it was a big JavaScript file. It feels very bad when you develop an application and it is rejected by your seniors.

I don't want to feel bad and I want to concentrate on my work. I would like to restructure the code, as the coding structure in my company is very bad and I want to improve that.

I want to work better and grow - how should I proceed?

How should you proceed when somebody rejected a good thing you made?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在extjs中创建了一个应用程序，它被我的技术架构师、项目经理和团队负责人拒绝了，因为它是一个很大的JavaScript文件。当你开发一个应用程序时，感觉非常糟糕，并且被你的高年级学生拒绝了。我不想难过，我想集中精力做我的工作。我想重组代码，因为我的公司的编码结构很糟糕，我想改进这一点。我想做得更好，成长--我该怎么做？

问如果有人拒绝了你做的好事，你该怎么做？
EN

回答 14

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如果有人拒绝了你做的好事，你该怎么做？EN

回答 14

Software Engineering用户

Software Engineering用户

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如果有人拒绝了你做的好事，你该怎么做？
EN