351–360 of 416 posts
Earlier quoted context omitted.
Someone posts literal garbage filled with nonsense words and that's what you understand? What's going on here?
Wow I don't think I've ever made someone on Hacker News this upset before. If it makes you feel better, I chose to reply to your comment because you put the most effort into your analysis, and your comment contributed actual information, unlike a lot of the other low effort stuff.
Earlier quoted context omitted.
Wow I don't think I've ever made someone on Hacker News this upset before. If it makes you feel better, I chose to reply to your comment because you put the most effort into your analysis, and your comment contributed actual information, unlike a lot of the other low effort stuff.
Well you didn't reply to mine. You replied to meaningless word salad.
As entertaining as it can be to follow a public meltdown for 5 minutes, this hurts because Automattic was a company I used to look up to. I had the idea that some day I might work for them. Not sure this will still be possible. Maybe on a business unrelated to Wordpress. > 159 people took the offer, 8.4% of the company, the other 91.6% gave up $126M of potential severance to stay! That is an interesting (meritful, im…
Yes using percentages to claim that those people never mattered to Automattic. Classy.
Earlier quoted context omitted.
In my experience, it's more that a small webdev company runs these sites and the client pays $50-200/month to maintain it, maybe do a little SEO, etc. To recreate the site in another CMS will cost hundreds of more dollars, at minimum, (probably thousands, realistically) and even then: what CMS are they switching to that's easier to use and has as wide a variety of plugins as WordPress? Because I'm not sure that CMS e…
Okay you seem pretty cemented in this belief. My belief is that there are plenty of CMSes available. The plugin ecosystem is a side effect of a poorly developed cms, not really a feature. You can abstract a lot of need for plugins by using a CMS that isn’t “just the basics to support a plugin culture”. If you want to lock yourself into wordpress requirements then you’ll never escape it.
Earlier quoted context omitted.
Probably not too many. The average WordPress site is run by a small business that doesn’t care the slightest bit about tech industry drama, or what open source even means.
I think these days, the average WordPress site runner is trying to find a cheap/free. Non-technical solution. I help out with a sports league who run a couple wordpress sites. - One, its totally the wrong CMS for how they use it. - Two, they have almost no ability to diagnose and debug issues themselves. Honestly 80% of the issues that get raised to me are even just solved by clicking "keep plugin automatically updat…
I feel I could battle harden a WP setup with those needs.
Disable most of the admin interface. Just let them access what they need.
Announcements, schedules, and where to play - stored as ACF records on a page/post and displayed with a custom template/loop.
Slim down the admin interface to just CRUD for those items.
Earlier quoted context omitted.
A competing product would have to at least be on par in terms of quality, licensing, UI/UX, app availability, sync, web interface. They'd have to start sacrificing living animals before I'd consider switching. They're even still honoring lifelong premium access for first purchases of their apps.
We have such different experiences. Pocket Casts works, but I find nothing about it amazing. Too much Apple-like simplification in managing my queue. I found Podcast Addict to be significantly superior.
While not necessary, especially because of the proprietary sync stuff you can't self host, Pocket Cast is open source.
So whoever is good enough to land a job in this crappy market got a sweet payday and the moat will stay in the company. What a brilliant move! I think these people really overestimate how much people give a shit about their company and what they are doing. Automattic is a sweet remote first shop which pays well - albeit I've heard you have to drink plenty of BS in day to day job. Attacking WP Engine and preventing th…
You're hallucinating that part of OSS. There's no requirement in any open-source software to interact with people you'd rather not interact with, for whatever reason you have, and there are extremely low limits to your continuing obligations for past interactions if you decide to "ban" them. (I'm using my non-lawyer understanding/memory on OSI-approved licenses, but I'd appreciate counter-examples to what I'm saying here if anyone knows of them.)
Earlier quoted context omitted.
Yes I am. I’m not spinning anyone. Several of my friends took the offer, they were unhappy, it was great timing. I support them 100%.
[flagged]
Earlier quoted context omitted.
Division is probably the wrong term used, we have several divisions, you can categorize them into 2 categories: - WordPress ecosystem (majority). Around 80% of the company. - Non-WordPress ecosystem (minority). Around 20% of the company. The % of people who left is consistent between those 2 divisions.
Oh, you could have said you work for Automattic! How's the distribution of departures by tenure and level? We know one of them was Executive Director over WordPress—is she an outlier or does the departure list skew to the top? And within the "WordPress division", is the spread even between groups, or does it skew towards some groups over others?
Spread mostly evenly. I'm not sure I'm allowed to share tenure, I'm mostly going to share what was here, but tenure felt logical, most people who left were on the 3-5 years range, most of people in Automattic joined in that period of rapid hiring.