[…] client and you have a well-defined set of requirements, though you know from experience what you’re building is going to need to: scale, be amendable to change, support the addition of future features. When this happens, it’s far easier to want to generalize the codebase so that you can support future features even though […]
Search: “support” (Page 24 of 68)
We found 336 results for your search.
[…] workflow (and the price doesn’t hurt either). Day One. is an application that I use to basically journal things that go on during the week. It has support for markdown, pulls it time, geolocation, and weather data from photos EXIF information, and gives you sleek overviews of your entries on Mac, iPad, and iPhone. […]
[…] why I think it’s a solid option when it comes to working as a local web server for WordPress-based development. It’s easy to setup, it’s got built-in support for WordPress, it uses Nginx (which is often faster than Apache is my experience), and it provides a great way to allow others to tunnel into […]
[…] to learn, because of what is and what isn’t supported by the nature of versioning. For example, we were using GrumPHP in a recent project which has support for a variety of tools but we were unable to use, say, PHPMD because of lack of adoption of the PSRs. As far as I’m concerned: […]
[…] do so for several reasons. Sometimes it has to do with their feature set, at times it has to do with the fact that I want to support the team behind them, and sometimes it’s a combination of the two (along with a bit more). MonsterInsights When it comes to tracking analytics, I prefer […]