3 ms·
Surely the best way to do it is to develop on the best machine available but then occasionally test it on inferior hardware just to make sure you're still on tr
by Havoc 15y ago
Surely the best way to do it is to develop on the best machine available but then occasionally test it on inferior hardware just to make sure you're still on track?
Intentionally crippling the entire dev environment seems a bit drastic to me.
- 51Cards 15y agoI don't see it as crippling at all... I don't develop on a 486 :) But you also don't need to sit on an i7 either which was the thought in the article. If your target audience is using typical hardware then most of the time you can easily use typical + 1 to develop. Then you can spot issues as they arise and not later when you kick to the test environment. The more you can catch in-process is less you have to re-architect later. Of course every situation will vary. Just my thoughts anyhow.
- mahyarm 15y agoThat doesn't really work when you have a complex system that spans servers, clients, databases, custom libaries,etc. And a large large test suite.