Here at Ingrained Technology, we love… technology. We love talking about technology. We also love independent, objective reviews. But there is a shortage of independent reviewing going on these days. Oh fan reviews occur regularly, but they are rarely objective or independent. If you love something enough to spend time writing about it, you generally aren’t seeing the shortcomings, or considering use cases other than yours.
So we have decided to fill the void. Once a quarter, we will choose a product or market, and run a review. For our first, we’ve taken a look at the pretty cool antsle Private Cloud Server, and considered its usefulness for hobbyists, enterprise developers, remote teams… Pretty much the use cases it is likely to be put to.
We performed tests on some of the claims antsle makes, and have hard data to go along with our analysis. And it’s all free. Just download it here.
Why free? We considered several options for these reviews, and have decided the first two (at least) will be given away as samples of our work, and a thank you to the high-tech community for all the cool stuff we all love to play with. Progress, largely spurred by members of the community, has taken us from text based apps written in line numbered basic to multi-targeted systems written in any of a dozen languages. We wanted to offer our little bit of support, so this first single product, and our first multi product will be downloadable here for free. The only thing we ask is that you share a link, not the PDF. That’s so we have an indication of popularity when we decide if we will continue public facing reviews. If you forward the PDF, we don’t know another person has read it. But the site will count downloads if you forward the link.
What’s next? We have not made a final decision. We’re down to four topics, and trying to single one out. But we’ll decide and get started soon.
We’re also trying to decide how much to put out. We have all of our scripts and configurations from testing saved, but the agile method that antsle uses for updates pretty much guarantees that the life expectancy of those scripts is relatively short. Though having them means you could replicate our testing (we keep them so we could rerun and validate results during the test period, you could do the same). We won’t be maintaining the scripts, since we have other duties, and that just creates technical debt that isn’t productive, so we’re arguing about whether the short term gain of putting them out is worth the long term reality of knowing they will eventually cease to work as advertised.