conversely, is the coder who is always the bottleneck also the one putting in all the hours?
相反地,总是成为瓶颈的程序员,是不是也是把所有时间都投入工作的那位?
for instance, a coder with user interface coding experience is only needed on the support branch of version 1.0 when there are defects associated with the user interface.
例如,一个拥有用户界面编码经验的编码人员只有在1.0版本的支持分支上、当出现了与用户界面相关的瑕疵时才被需要。
now if a client coder attempts to pass the wrong kind of object to adddictionaryio(), the php engine will throw a fatal error.
现在,如果客户机编码器试图将类型错误的对象传递给adddictionaryio(),php引擎将抛出一个致命错误。
therefore, during the inception, elaboration, and transition phases of version 1.0, that coder will not be fully utilized.
因此,在1.0版本的先启、精化和产品化阶段,这种编码人员得不到充分的利用。
you have to be product manager, if not the actual coder and designer.
就算不去搞编程设计,你也得当产品经理。
a great coder keeps tabs on software and is constantly finding ways to improve his usage of them.
一个好的程序员会密切关注软件的发展,不停地在尝试新的方法来提高自己对他们的掌控能力。
an html coder tshould be able to look at a file containing an xml-rpc procedure call, understand what it「s doing, and be able to modify it and have it work on the first or second try.
html编码人员应该能够查看包含xml-rpc过程调用的文件,理解其进行的工作,并能够对其进行修改,只需一两次尝试就能使其正常工作。
as it stands, nothing is stopping a coder from passing an entirely random object to adddictionaryio().
正如所显示的,没有什么阻止编码器将完全随机的对象传递给adddictionaryio()。
using php v4, you would have to test the argument types in this example to be absolutely sure that the coder passes around the right kind of objects.
使用phpv4 时,必须测试本例中的参数类型,以绝对确保编码器传递类型正确的对象。
this model relies on the coder understanding and managing the whole soapenvelope.
这个模型依赖于可以完整解析和管理整个soapenvelope 的编码器。
companies find themselves using in-house coder teams, but that」s not necessarily speedy or cheap.
公司自己用的是内部开发团队,但是那么做未必就省事或省钱。
as noted earlier, the peak level of effort for a coder is high in the construction phase of each program branch.
正如之前提到的,编码人员的工作峰值水平在每个项目分支的构建阶段是很高的。
just as dangerous is the cowboy coder who rides in to save the day, but leaves a lot of half-assed code behind for other people to deal with.
这很危险,就像牛仔程序员一样,他们沖进来拯救危机,离开时剩下很多半途而废的代码,让别人去解决。
memory management is usually handled by requests from the coder to allocate and release blocks of memory.
内存管理通常是由来自编码人员的请求处理的,以分配和释放内存块。