mydev tools– a running list

Jan 2, 2017

​This list follows a format of: things I have started using, things I am still using, and things I have stopped using, to be updated semi-regularly (quarterly or half-yearly). Things ​refers to anything dev related: IDEs, languages, build tools, server environments. It serves as a register of thoughts on my development practices at any given point in time.

January - Hello 2017

Started

  • Greensock. Used this for a large animation project for Pathfinder. Incredibly powerful, but still trying to wrap my head around the best way to use it in a React context.
  • React Motion. Gets a mention here because while I've only used it in demos, I've been borrowing the fundamental concept of wrapping components in a state manager for animations for some simple animations in my work projects.
  • Visual Studio Code. Faster than Atom, better support than the JetBrains stuff, perfect for working with JavaScript, which is where I spend most of my time. The app gets monthly updates, always packed with useful stuff and things you didn't expect, like Zen Mode.

Still

  • React, Gulp, jQuery. Nothing exciting here, but I keep wondering when jQuery won’t be on this list. Seems like it’s not any time soon!

Stopped

  • Atom. Slooooooooooooow. I still like lint highlighting in Atom more than Visual Studio Code, but ran into so many issues getting those plugins to even work in the first place that I gave up on it.
  • PHPStorm. One update broke splitting panes, which I could get over if a fix release came out shortly after, but it never did. Hard to justify the cost these days when Visual Studio Code does 99% of what I wanted out of PHPStorm.

May 2016 - Initial Entry, this covers everything from the last year or so.

Started

  • React. As a UI developer, and as someone who learned how to code by creating games, React matches very nicely with how I envision web apps should be designed.
  • Webpack. The documentation is somewhat lacking, but it's clearly the most powerful build tool, especially once you have React and Babel involved.
  • Babel. Primarily for JSX, but now that I’ve started writing ES6, I can’t go back.
  • Atom. I’ve been trying it on and off since the earliest betas. It’s still not my main IDE, but it’s great for one off files.

Still

  • Craft CMS. Pixel & Tonic have been doing an amazing job supporting Craft, the community of developers behind it is really coming together, and Craft Commerce and the 3.0 release are both promising.
  • Gulp. Because it’s just a wee-bit better than Grunt.
  • jQuery. It’s still a great library from DOM manipulation and simple AJAX calls.
  • PHPStorm. I could probably get away with using WebStorm, but PHPStorm pays for itself when I have to debug something in PHP.

Stopped

  • Grunt. No point in using Grunt and Gulp and Webpack, and Gulp felt a little cleaner for my most common workflows.
  • Sublime Text. Sublime is much faster than Atom, but Atom seems to have the bigger community these days and a more transparent development timeline.
  • lodash. Haven’t found many uses for it now that I can write ES6 and transpile it.