usingpond
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.
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.
Boy, I sure hope somebody got fired for that blunder.
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.
- Lengthy learning curve.
- Not concerned with performance at all (can be a nightmare on mobile devices with low RAM).
- Google's history of throwing away and/or deprecating projects, (see Angular v1).
- I still have yet to see a Google website using Angular in any large capacity.
- Ecosystem lock-in. It tries to do a LOT of stuff, and you generally need to be doing all these things the Angular Way™.
1) Much less legible, and in some cases outright lazy 2) Extremely vulnerable to Javascript's fast-and-loose type checking.
However it's good to be AWARE of them, since you tend to see them a lot in team projects.
You've got nothing to lose, it's essentially just a naming convention for git. You won't be locked into anything.
Is this satire? How can anybody hold this viewpoint and not think of themselves as human garbage.
Also, any web developer should be thoroughly embarrassed if their unintentionally have Times on their site. That is an unequivocal "something got fucked up" error, especially because it means you didn't care enough to make a fallback.
Chrome is not a superficially better browser—as a web developer I can attest that Chrome beats out Firefox in myriad ways. Candy has no value other than flavor, and is actually bad for you. The advent of Google's release of Chrome (and the collaboration between Google and Apple engineers on WebKit) has launched the web forward at a speed that Firefox has been struggling to keep up with. That INCLUDES security and openness, not just new prefixed CSS properties.
The browser war was Firefox's to lose, and they dropped the ball. They weren't ready for Chrome, and have yet to catch up.
Why don't they embed their fonts? Indifference? Laziness? Ineptitude?
Obviously I don't mean this retro landing page, just click through to any other page of theirs. It's all Times and Arial.
Firefox has had its problems too recently, but at least it's open source and they're trying. Microsoft has literally nothing going for them on this front.
One common mistake across ALL Microsoft sites is not bothering to embed their fonts, or declare fallbacks. So it looks great on their boss' computer but everybody else gets goddamned Times New Roman.