使用敌对工具编码的提示？ [英] Tips for coding using hostile tools?

问题描述

我正在使用错误的工具开发应用程序。我不想陷入这个权利或错误 - 平台已经被祝福为战略，没有什么会改变现在。但我希望有人可以给我一些如何充分利用这些情况的提示。

I am developing an application using the wrong tools. I don't wish to get into the rights or wrongs of this - the platform has been blessed as Strategic and nothing is going to change that now. But I'm hoping somebody can give me some tips on how to make the best of the situation.

我们使用服务器端语言，我们称之为X，客户端HTML / JS / CSS（在IE6上）。 X从应用程序开发的角度来看是原始的（但是对于数据处理来说非常好，这就是为什么我们使用它）;它甚至没有用户定义的功能的概念，所以试图使应用程序模块化在任何方式是一个挑战。想想成千上万行的嵌套if / then / else语句。

We use a server-side language, let's call it X, and client-side HTML/JS/CSS (on IE6). X is primitive from an application development point of view (but excellent for data processing, which is why we are using it); it doesn't even have the concept of user-defined functions, so trying to make the application modular in any way is a challenge. Think tens of thousands of lines of nested if/then/else statements.

我目前的假设是，减少代码的意大利面因子是不可能的，真正伟大的文档是我唯一的武器，反对这成为一个完全不能支持的噩梦，结束了TheDailyWTF。

My current assumption is that reducing the spaghetti-factor of the code will not be possible, and that really great documentation is my only weapon against this becoming a totally unsupportable nightmare that ends up on TheDailyWTF.

任何人有任何其他想法？

Anybody got any other ideas?

（我没有提到什么语言X是简单的，因为我希望解决使用缺陷工具的一般问题，而不是X的任何特定策略。）

(I don't mention what language X is simply because I'm hoping for answers to the general problem of working with deficient tools, not any particular tactics for X.)

编辑：

好的，对于病态的好奇，X是SAS。我不想让问题集中在函数式宏是函数（他们不是，不能实现设计模式），或者责怪它 - 鉴于这个特定项目的约束，我实际上同意决定使用它！我还确信，大多数软件是在令人难以置信的非最佳环境下开发的（破碎的工具，糟糕的管理，霸道的遗产负担等），并且必须有策略，使事情发挥作用。

Ok, for the morbidly curious, X is SAS. I didn't want the question to focus on whether function-style macros are functions (they are not, and cannot implement design patterns), or to blame it - given the constraints of this particular project, I actually agree with the decision to use it! I am also sure that the majority of software is developed in incredibly non-optimal environments (broken tools, bad management, overbearing legacy burden, etc.), and that there must be strategies for making things work even so.

推荐答案

有X有注释吗？

。

这篇关于使用敌对工具编码的提示？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！