如何证明你的同事，他们生产瑕疵代码？ [英] How to justify to your colleagues that they produce crappy code?
问题描述
我发现在我目前的工作中继续工作有些困难。代码库最近变得有点荒谬），我很难处理代码的某些部分。我可能是愚蠢的，但很可能只是它让我很多，开始工作的东西，很难推理。
我的老板已经意识到我的想法 - 我表达了感觉像这样工作。他请我提供错误的例子。当我指出两三个小问题时，他说是的，确定，但重构会花费他很多钱，我们必须得到产品（不是第一次听到这个）。
我不得不承认，这些例子不是最引人注目的，但问题实际上很难解释。它是由许多小的坏决定整个代码库组成。 （我们也看到这个问题是绝对主观的）。例如，错误的命名，处理null，样板，不使代码可重用（或相反）等。可能会再次重新考虑别人的代码，以证明我会有所不同。
你有想法如何处理这个？
有时候你的同事程序员做的事情与你有很大不同，你可能觉得错误的事情可能有积极的方面。我们都有我们的学校，我们来自。我想我遇到了程序员，他们抱怨我不太明白的事情，我经常感到有些事情需要被抱怨。
确保您可以将您抱怨的内容推断为具体的劣势。如果没有其他原因，你可以激励中层管理人员做出改进。难以推断为可测量事实的事情通常源自品味/风格的差异，而不是质量（有关于这个主题的看法）。 smacl 发布的回答提供了良好且具体的建议！
如果您可以将您的疑虑转化为真正的不利，那么我真的不同意，当人们说，一个人必须接受这样的情况。我已经暴露了这个问题不止一次，让我告诉你，重构不是解决问题的办法。 重构只修复症状。
接受这种情况与说质量差的产品线昂贵和令人沮丧的维护是我公司可以生活的东西。。这种情况很少发生。然而，管理层（即那些有优先次序的项目）在技术上通常不会意识到问题是什么，或者为什么开发是昂贵的。
这就是为什么你需要一个开发组织，包括技术主管，总建筑师，良好的组织结构和分层模型等。经验丰富软件专业人士谁已经看到的道路导致，如果你忽略某些方面的发展。
要坚持你的公司，尝试改变你从根本上做事的方式，或者你找到另一个工作地点，并确保在面试期间了解他们在每天的发展中如何工作。
祝你好运
I am finding somewhat difficult to carry on working in my current job.
The codebase has become a bit wild lately (but definitely not the worse I've seen), and I'm having a hard time dealing with some parts of the code. I could be stupid, but most likely it's just that it demotivates me a lot to start working on something that is hard to reason about.
My boss is already aware of my thoughts - I expressed what it feels like to work like this. He asked me to provide examples of what was wrong. When I pointed out two or three small issues, he said "yeah, ok" but that refactoring costs him a lot of money, and that we have to get the product out (not the first time I hear this).
I have to admit that the examples were not the most compelling, but the problem is actually tough to explain. It's made up of a lot of tiny "bad decisions" throughout the codebase. (We also see this issue is absolutely subjective). For instance, bad naming, dealing with nulls, boilerplate, not making code reusable (or the opposite) and so on. It can be tiring to re-think someone else's code over again to justify I would have done it differently.
Do you have thoughts on how to deal with this? I am a bit fed up of having to go hacking around a quick 'n dirty codebase every time!
Sometimes your fellow programmers do things very differently than you, and things you might feel are way wrong might actually have positive aspects. We all have our schools we come from. I think I've come across programmers who complain about things I don't understand equally as often that I myself have felt something needs to be complained about.
Make sure you can deduce what you complain about into a concrete disadvantage. If for no other reason so that you can motivate middle management about improvements to make. Things that are hard to deduce into measurable facts usually originates from difference in taste/style rather than quality (there are boooks to read about this subject). The answer posted by smacl have good and concrete advice!
If you can deduce your concern into a real disadvantage, then I really do not agree when people say that one have to "accept" situations like this. I've been exposed to this problem more than once, and let me tell you, refactoring is not the solution to the problem. Refactoring only fixes the symptoms.
Accepting a situation like this is the same as saying "bad quality product lines and expensive and frustrating maintenance is something my company can live with". This is ofcourse seldomly the case. However management (i.e. those with the go/no-go on what projects to prioritize) are very often not technically aware of what the problems are, or why development is expensive. They shouldn't have to be for that matter.
That's why you need a development organization with technical leads, chief architects, a good organisational structure and tiered model etc. Experienced software professionals who have seen where the road leads to if you ignore certain aspects of development. It's about changing the "culture" of your team(s).
Either you stick with your company and try to change how you do things from the roots, or you find another place to work and make sure you find out during the interview exactly how they work in every-day development.
Good luck
这篇关于如何证明你的同事，他们生产瑕疵代码？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
