7 karma · joined November 13, 2014
You've completely got me on that one. On the bright side, it requires much less cost of ownership than a more traditional DB solution.
So, there's that. :)
I would probably expect the same thing from my employees as well. If I was to blame my bad attitude on the hours, that would be a total cop-out.
I've always had issues with soft-skills; especially in the area of attitude and communication skills. I've done a lot of work in the last couple of years to try and be a better communicator (and hopefully a better human being).
I'm still a work in progress though.
It's non-trivial for most teams to setup personally managed dependencies for their dependencies (e.g., cvs, package management, etc.).
Maybe it's just my experience, but outside of the enterprise realm, I generally don't see that sort of thing.
I know I've gotten plenty of "temporary failure resolving..." issues when trying to work with APT repos.
I've always told customers that PayPal is great if you are doing a store/e-commerce. If you're doing anything else, it can be absolute Hell to deal with and you're going to be better off using Stripe or Authorize.Net.
In my experience, WordPress is not built for developers or designers. It's built to be simple and extensible from the end-user's point of view. Most end-users don't expect absolute perfection and accept that it will do 90% of what they want. As long as it keeps doing that, no one will care what a "mess" the insides of it are.
However, I think they know that if they completely abandoned the .NET framework, there would be a community of very upset devs that have spent their entire careers investing in Microsoft. Instead, they're doing a slow withdrawal and "giving it to the community".
I think that in the long term, they're going to be focusing more on Sharepoint, SQL Server, and Azure; less on .NET. That's just IMHO.