• Great resources in spinning up proper configurations for proxying public URLs to local node apps and services, plus it's a very solid and fast webserver in general.

  • Server-side JS, part of my full-stack JS approach.

  • Slack is hands down the best business and developer collaboration tool out there. I use it regularly.

  • Standards-compliant modern content delivery across many devices, what's not to love?

  • I use Redis for cacheing, data storage, mining and augmentation, proprietary distributed event system for disparate apps and services to talk to each other, and more. Redis has some very useful native data types for tracking, slicing and dicing information.

  • Great ecosystem of libraries and modules, and easy management of application resources.

  • Schema-less, JS in the console, flexible, fast, and pairs well with node/Mongoose.

  • I find Kanban to be a good collaborative project management tool, and Trello is a nice implementation of it. A few things lack, but in general it gets the job done.

  • This is the best component framework and API available today for building modern web sites and apps. I really enjoy how minimal it is, and powerful at the same time. It removes opinionated development and replaces it with logic and data philosophies, which has in turn fostered a robust and lively code and support community.

  • Easy API, does what the box says it does, good toolset for expanded email tracking when needed.

  • Used mostly when forced only.

  • I have limited experience with CloudFlare, but it has a great reputation and having a good focused CDN to rely on is paramount for high-availability apps.

  • Everyone needs a map now and again, and this is a good service for it.

  • Pretty standard file sharing, stable across multiple platforms, and it's not google.

  • DO's server management tools are quite easy and get me up and running quickly and then gets out of my way. Great pricing and SSD.

  • Flexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).

  • I find integrating Stripe as a payment option for web/mobile ecommerce to be easy and effective.

  • Ubuntu is a solid choice for *nix, and for a non-admin like myself a good community of resources to learn from.

  • I'm fluent in ExpressJS, but over the past two years I have moved to HapiJS. Similar results, but I find Hapi to be more full-featured towards my app, api and service needs. I can operate confidently in both.

  • Mainly for github Readme files, and occasionally for other documentation as desired.

  • Only when forced. Slack is king.

  • See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.

  • No real definitive reason, I find it to be the most natural way to import libraries and code in nodejs (prior to ES6 / import).

  • Research, bug hunts, general technology advice. It's a deep archive of great information.

  • Pingdom is a tool I use close to deployment of new apps or sites and periodically used to check the health of an app or site over time. The analysis of request times, assets and more is second to none.

  • Charts, charts, charts. Data visualizations are a great way to communicate information to people who need to know it, quickly and concisely.

  • Foundation has been my choice for years over Bootstrap and other similar CSS frameworks due to the naming conventions, well-designed built-in components, and it plays well with React when I'm not using ElementalUI instead.

  • Handlebars for me has taken a back seat since my full embrace of React, but previous to React it (along with its predecessor mustache) I used it heavily, both server and client side, in multiple languages.

  • Socket.IO has a decent community footprint, including integrations with popular JS frameworks, and has fallbacks to maintain an app's services if websockets are not available for some reason. Websockets are an important factor in most of the web-facing apps I build, to provide asynchronous two-way communication between the app and whatever server or data source it is connected to.

  • I use Asana as a task tracker and basic project organizer.

  • Disqus is a nice well-known and easy to use commenting engine, plays well with most any web-facing integration.

  • Twilio is a service I have experimented with, and given a project with SMS requirements I would choose Twilio to support that.

  • I use babel so I can confidently move forward using ES6 and other more modern Javascript concepts and libraries in development and still maintain compatibility with the current state of web browsers and other viewports.

  • I have been using React/Flux since just about the beginning of React time. Redux is a great upgrade and extension of the core flux concepts, and brings immutable and strict declarative state to the apps I build.

  • PHP to me is a legacy technology that I have years of experience in, and can step back into when necessary, but I do not choose to use in new projects.