What's in Your Stack?
Thanks for taking part in this series. The goal is provide brief, but informative overviews of technologies and practices people are using in IT. That is, "what's in your stack." There are 4 questions below, and the end result (published at http://RedMonk.com/cote) will narrow down on one of the answers with a follow-up question (and answer) from me.

The goal is to provide people with a peek at what technologies, hardware, frameworks, practices, and such others are using for their development. This isn't intended to be a discussion of business models, products, or other things like that except as a way to inform how various technologies and practices are a good, or poor, fit for those "business" goals: just a discussion of technologies used.

Previous posts, as examples: http://www.redmonk.com/cote/topic/whats-in-your-stack/
Sign in to Google to save your progress. Learn more
What to do
Please answer as many or as few of the below as you'd like (answering all of them would be great). I'll take the best answers (usually just one) to use for the final posting - the goal is to be brief, but informative, so posting all of them will not always work. Additionally, once I narrow down the answers, I'll send over one follow-up question to drill-down just a bit.

Feel free to be as brief or thorough as you'd like and/or have time for. Being comprehensive isn't critical, while going over the helpful tools and techniques that others can learn from is more the point. Also, don't share anything that's secret or that you don't want published on the web, obviously.

The final format will be (1.) the profile from the first question (I'll always include that), (2.) the selected answer(s), (3.) the follow-up question, and, optionally, (4.) any additional commentary I add.

Also, if there's any pictures of your development space ("the office"), hardware setup, or even a screenshot that shows of your stack, feel free to send it along.
Questions
In all of these questions, if there's something new, interesting, or experimental you do that's even tangentially related, feel free to include it.
Email address
So we can contact you, we won't publish it, obviously
Who are you?
First, describe your project, company, organization - the "business"/function the stack is supporting. Also feel free to tell us about yourself.
How would you describe the development process you follow?
How do you plan out what to do, manage the execution of coding (or "requirements," stories, etc.), test it out, release it, and then start the cycle all over again? E.g., "we use Scrum, but modify the orthodox way by doing this."
What tools are you using for development and delivering your software?
E.g., if you're a SaaS or deploying to the cloud, how are you doing that? Tools could be things like IDEs, frameworks & SDKs, hardware for workstations or build farms, project management tools, wireframe editors, analytics tools to watch people in production (if a SaaS app), diagnostic tools... just anything you want to comment on that's used as part of getting your application out the door.
Tell us about a recent tool, framework/SDK, or practice that you started using that worked out really well, much better than you'd thought. And/or, what's one that didn't work out well?
Anything else you want to tell us?
Related blog posts, Twitter handles, or just other info about your stack you think people would find interesting.
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of RedMonk. Report Abuse
Google Forms