This is a great opportunity. Tech and business journalists / bloggers / podcasters will want to talk about it. It won't be the big story, but a fun side-piece to chat about before the big story, or something.
Make sure you put out an official PR statement when you have your new name and send it out to as many journalists and pundits you can find. If you have a Twitter, definitely post the announcement there. If you don't have Twitter, get one right now.
We are a bunch of hard-working tech founders putting together this web shop, to help build and scale awesome products. We in our previous avatars have built, payment processing gateways(acquired), ERPs, CRMs, hyperlocal apps, RESTful APIs for banking systems, and much more. Our team comprises of Mobile Developers, Infrastructure Engineers to AI Researchers.
We are a bunch of hard-working tech founders putting together this web shop, to help build and scale awesome products.
We in our previous avatars have built, payment processing gateways(acquired), ERPs, CRMs, hyperlocal apps, RESTful APIs for banking systems, and much more.
Our team comprises of Mobile Developers, Infrastructure Engineers to AI Researchers.
---
We are a bunch of hard-working tech founders putting together this web shop, to help build and scale awesome products.
We in our previous avatars have built, payment processing gateways(acquired), ERPs, CRMs, hyperlocal apps, RESTful APIs for banking systems, and much more.
Our team comprises of Mobile Developers, Infrastructure Engineers to AI Researchers.
Could you also talk a bit of detail as to how, once the setup has been done, one can go about provisioning the EC2 instance? In fact, provisioning instances, setting up softwares and packages are what are important.
Résumé/CV: We are a bunch of hard-working tech founders putting together this web shop, to help build and scale awesome products.
We in our previous avatars have built, payment processing gateways(acquired), ERPs, CRMs, hyperlocal apps, RESTful APIs for banking systems, and much more.
You should read more about us on our site - [Apcelent](apcelent.com)
Testing is something I do a lot, and like talking about a lot as well. There are no hard and fast answers to testing, like other stuff, there are lots of opinions(they are like assholes, everyone has them, and the others' stinks) about testing. So here goes mine(not necessarily correct, but worth putting them here). I am putting them as one liners, let me know your thoughts.
1. What do you mean by unit in unit tests?
An implementation of very basic feature, probably not more than 100 lines of code.
2. What do you test when you write a unit test?
We test the basic correctness, eg. given a url, if it exists assert 200, if not assert 404.
3. What should not be tested?
The inbuilt libraries should not be tested. Eg. If you are using a library say django, you should assume it comes pre tested and should not spend time writing tests for them.
4. What should be the depth of the tests?
There are no rules, but you should stop when you feel like you are humming inception theme.
We are a dynamic web studio. We do high end web and mobile apps. We have considerable expertise in python web frameworks mainly django. We write modular javascript using backbonejs. Find more about us at : http://www.fruiapps.com
Following are the services we offer: http://www.fruiapps.com/services/