I see this kind of rejection from time to time, and often times the "rockstar" who can "sling badass code" ends up learning the hard way that rejecting these tools to facilitate communication, automate deployment, improve productivity isn't about themselves or their preferences. It's about working with a team. No basketball coach ever got up in front of a team and shat on whiteboards like you just did about productivity tools. You're not cool for NOT using these tools in the same way that people are not cool FOR using these tools. Also, if you're "not dumb enough to waste time dicking around in "management tools" on projects that shouldn't be complex", maybe you should find some more challenging work, you "badass!"

To add to the Atlassian stack, Bamboo fits in very nicely with JIRA and Stash/Bitbucket and does wonders for sole developers and teams alike.

I agree that people shouldn't get hung up on details and semantics that are considered RESTful. However, I don't think avoiding these details entails being ignorant of these semantics. You mentioned the plurality of resources. The fact that you mentioned that means you are aware of this convention, which likely means others have that expectation from an API. The outcome -- use the standard. Spending a little time upfront of being aware of RESTful conventions can lead to a better API usage experience and a longer-lasting API lifetime.