My last gig forced us to use Asana for ticketing (!!!). It's meant as a Basecamp-like tool but I'm not sure if it delivers on that either.
Currently we use Confluence for documentation, which, like many other Atlassian products, is lacking notable features compared to cheaper competitors. Other than that, we're great: Exchange, Slack, Github (including issues), etc
Google for Business or w/e would be great, but there is no way a company this size is gonna do that.
Maybe we're both misunderstanding, but I think they meant "User Experience". Surely you agree that this is an important consideration in software development?
To contribute some anecdotal findings to the larger IT discussion in the thread, a lot of it comes down to this IMHO...
There are three levels of understanding of personal computers and how to manage them:
A) Basic understanding, the vast majority of users/clients
B) Intermediate understanding, you often find yourself walking your relatives through setting up their mail client
C) Expert understanding, you have deep knowledge of networking and user permissions for each computer on this network. You don't use apps to figure this out, you have set it up, tried it, and are proud of a system you have designed to make it all work.
I've found that many issues arise from folks working in IT whom are B that think they are C, and the frustration from not having Macs work identically as their Windows networking wizards causes friction. I think as people are getting better trained in BYOD, and the fact that there's no way around better IT training to accommodate it, is causing a sea change in adopting Macs.
Lateness is often considered rude because it shows you don't care about something. If this is a situation where that assumption is correct, then it's time to move on to a new job.
Late for meetings makes you a jerk. If you get your shit done and show up later than some arbitrary "start time" at work... your boss has a right to be like "c'mon dude" but not to penalize you. That's childish and petty, and another reason to move on.
The author is pretty open about this not being anywhere near ready. It would be better if they were open about the possibility of this loophole being patched up in the spec, making this a pretty useless trick.
Not at all, the author praises Backbone. The learning curve, busted syntax, and performance issues unfortunately ARE specific to Angular, that's the entire point of the article.
In some apps, yes, but in many others they are just as atrocious as they've always been—just adhering to material design a bit more. For example, Chrome on iOS has a pretty wonderful UX but Maps is a shitshow; it takes me several frustrated clicks to do what I want. You can never tell what a UI element does simply by looking at the screen.
Currently we use Confluence for documentation, which, like many other Atlassian products, is lacking notable features compared to cheaper competitors. Other than that, we're great: Exchange, Slack, Github (including issues), etc
Google for Business or w/e would be great, but there is no way a company this size is gonna do that.