tom (@codebytom) header
tom (@codebytom) profile picture

Software Engineer working at @automattic on WooCommerce, prev @atlassian

Manchester, UK.
Joined April 2023
Photo by tom (@codebytom)Photo by tom (@codebytom)Photo by tom (@codebytom)Photo by tom (@codebytom)Photo by tom (@codebytom)Photo by tom (@codebytom)Photo by tom (@codebytom)
Don’t confuse the ability to ship with having something worth shipping.
22
26
8
305
9,917
For starters, the feature wasn't killed. It's still in active development to be more performant on non-purpose-built infra. Secondly it's working on WordPress VIP! RTC with presence, and it works great and is in active use. Troubling that the EmDash team continues to lie about its competition, not a great look.
WordPress tried to ship collaborative editing in 7.0. The release ended up getting held back, and then the feature was killed because implementing it well was so complicated in WordPress's architecture. In EmDash on Cloudflare it's simple.
6
6
41
2,144
You made your site a home. When it needs a little more room to grow, moving shouldn’t mean starting over. Bring more of what you’ve built—your pages, images, design, and more—to a @WordPress site you own. Start your next chapter: wordpress.com/move/?utm_sour…
1
4
1
13
3,036
In #woocommerce 11.4, you can have multiple product collections on the same page and they are filterable independently
1
4
7
361
Today the PHP project released security updates addressing two critical "PHP2Shell" vulnerabilities. If your site is hosted on @wordpressdotcom, @WordPressVIP, @wpcloudofficial, @Pressable, @tumblr, or any Automattic infrastructure, you’re already protected. Managing PHP yourself? Here’s what to do: automattic.com/2026/10/21/yo…
5
69
15
179
42,931
Your sites are already protected against the recently disclosed PHP security issues. Automattic worked closely with the PHP Security team to ensure that all sites hosted on our platform were protected as soon as possible. There’s nothing our customers need to do. Really. Back to your regularly scheduled coffee. bit.ly/4hVzO82
4
10
3
71
50,351
This year, #WCMCR will be BarCamp-style. ▶ No traditional sponsors ▶ No traditional talks Instead, we'll have a surprise keynote session in the morning, with 3 afternoon sessions split over our venue. 🔗 manchester.wordcamp.org/2026… #WCMCR 🐝
1
1
1
4
362
tom retweeted
We have a new default theme for @WooCommerce available now, called Purple. It's early days, but is already a great starting point for block-based, commerce-centric @WordPress sites. Help us improve it!
8
11
3
37
3,101
I like the web for people, sites that live and grow, like people. 100 years from now you should feel the people who lived there.
1
1
1
9
1,585
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto → getartcraft.com/apps
510
3,348
703
27,441
3,319,814
Launched an experiment on WordPress.com last week that attempts to match up new writers with other new writers:
6
22
2,664
A client wanted a blog. He designed it in Claude and had no idea how to make it happen. I did not have a lot of time so made it into a theme and loaded it to a 3 bucks a month @wordpressdotcom instance. Took less than 20 minutes including registering his domain. He is over the moon!
1
4
6
1,257
RSS is such a beautifully boring piece of technology. A site publishes a feed. Your reader checks it. New stuff appears.
36
6
4
125
13,036
Real talk. It's easy to bitch and moan about the number of WordPress security releases we've seen over the past few months. I get it. Updating and checking sites takes time, especially when you're responsible for dozens (100s?) of them. But those releases also mean people are finding vulnerabilities, reporting them, and doing the work to fix them. Researchers and maintainers are taking responsibility for software that millions of people depend on. That's a sign of a healthy community. It doesn't make the vulnerabilities any less serious, or put WordPress above criticism. It does give us a response we can examine and fixes we can apply. And “I'll just build it with AI” doesn't get you out of any of this. Neither does switching CMSs or writing everything yourself. Whatever you build still needs security review and ongoing maintenance. A working website can still be a vulnerable website. Fewer public security reports don't automatically mean fewer security problems. Personally, I want people looking for flaws in the software I use, and people committed to fixing what they find. I'm glad WordPress has that community. If you're building your own alternative, who's doing that work six months after launch?
17
28
8
108
14,144
On September 30th, @DevelopWoo is hosting an online chat all about block themes. We've got @mikemcalister of @BuildWithOllie alongside Woo blocks engineers Lucio Giannotta and Karol Manijak to share their experience and answer questions. Register here: developer.woocommerce.com/20…
1
15
4
29
4,839
interesting reversal happening where typos are now a sign of effort
106
368
65
4,373
135,881
In the next version of #woocommerce, you will be able to set the sale price for all variations quickly with new bulk action added in github.com/woocommerce/wooco…
2
6
227