Comments on: Internal tools only require the critical path https://www.robg3d.com/2012/02/internal-tools-only-require-the-critical-path/ Blog of Rob Galanakis (@robgalanakis) Wed, 08 Feb 2012 02:08:43 +0000 hourly 1 https://wordpress.org/?v=5.4.1 By: Robert https://www.robg3d.com/2012/02/internal-tools-only-require-the-critical-path/#comment-8105 Wed, 08 Feb 2012 02:08:43 +0000 http://www.robg3d.com/?p=886#comment-8105 good post. But don’t forget about us outsourcers though. We love it when you develop your tools as if they were (at least a little bit) for an external client. Ideally you want to ask yourself “is there a chance we will give this tool to a 3rd party?”.

Cheating, unfortunately does happen – some people just like shortcuts. That’s where QA comes in, or your tool, so it prevents cheating right away.

Security – many outsourcers have different clients and enforce stricter security than their clients. your tools should play along that, or we have to send them back, or spend time with your TA troubleshooting (not good for both parties).

Still, the lengths you have to go to are still way below anything if you’re billing an external client for it. So yes, do experiment!

]]>