Why we answer questions on Reddit

Why our software development company answers WordPress questions from strangers on Reddit, and what we learn from the other developers in those threads.

Written by
Role
Magda Chmielewska
Senior Operations & Account Manager
Published
Reading time
7 min read

Why would a software development company spend time answering strangers on Reddit?

We could use that time to write another case study or LinkedIn post, something that brings people to our site. Instead, Michał, a senior web developer on our team, answers questions in various subreddits, such as r/Wordpress and r/webdev.

Almost every site we build runs on open source software like WordPress or Nuxt, so we use other people’s work every day without paying for it. Answering questions is one way to return the favor.

Michał posts from our official Reddit account, u/Coditive_. If you see ~MS below a reply, that’s him. He has spent nearly a decade building WordPress plugins, themes and integrations.

The Coditive profile card on Reddit with the bio “Official Coditive account. We help agencies and companies build fast, scalable websites with Nuxt, WordPress, WooCommerce and AI. Official Nuxt Partner. Sharing what we learn along the way.” It shows 18 karma, 31 contributions, one year on Reddit and activity in seven communities.

Our profile on Reddit: u/Coditive_

What makes a reply useful

A useful reply is usually short and honest about its limits.

How do I show posts from another site in my Multisite network?

The original poster (OP) ran a WordPress Multisite network with two sites and wanted the latest posts from one to appear on the other, without publishing them twice. Michał recommended switch_to_blog() and linked to the documentation, so they could try it themselves.

Reddit reply from u/Coditive_: “It is possible - you are correct with the data being in the same DB. There are probably ready solutions/plugins for that, but I haven’t used any so far. If you’re coding it yourself, look into the switch_to_blog() function. So the general idea is to switch to the site you want to get posts from, run the query to get 4 latest posts, and then restore to the current blog.” The reply is signed ~MS.

Michał's answer, signed ~MS. Source: r/Wordpress

Is WordPress safe enough for a small business?

Someone building a site for a small business asked whether WordPress was a good choice given the security risks. Michał compared WordPress to a popular car model. Parts are easy to find and plenty of mechanics know it. The same popularity gives thieves a reason to learn how to steal it, because one trick works on thousands of cars.

We tell our own clients the same thing: WordPress is a fine choice for a business, as long as someone owns its security after launch (that’s what our WordPress maintenance is for). When a serious vulnerability goes public, the first attacks come within hours. We wrote about what that looks like in 2026.


What we learn from other people’s answers

The best answer in a thread isn’t always ours. When it isn’t, we take notes 📝

Why does a WooCommerce rule ignore older brands?

In a WooCommerce thread, the owner of a store that sells carpet by the square meter had a minimum order rule set per brand. It only worked for brands created after the rule was added. Michał suggested saving one of the older brands with temporary values, then saving it again with the original ones, and testing a product from that brand in a private browser window. The owner tried it on several old brands. It didn’t work.

Then someone else noticed what we’d missed. The site’s theme, WoodMart, registers brands as a taxonomy, and the Perfect Brands plugin registers them again, so the rule might only be reading one of the two. Another developer explained how that happens: WooCommerce didn’t have brands of its own until 2025, so older stores can have more than one brand field. We never learned whether that was the cause, but it was a better lead than ours.

What one team learned running WordPress sites with 10,000+ posts

In a discussion about slow WordPress sites, the most useful part was OP’s own post. Their team runs news portals and big blogs with 10,000+ posts, and page and object caching hadn’t helped, because the slow parts were in how WordPress stores data.

On a site with 50,000 posts and about ten tags each, the table that links posts to their tags grows to half a million rows, and one extra index took some of those queries from seconds to milliseconds. Post meta, where every custom field is a separate row, got an index too, and the busiest fields moved to a small custom table. And because WordPress paginates with OFFSET, every crawler request for page 500 of an archive made MySQL fetch and discard 10,000 rows. Cursor-based pagination kept query times flat.

Their workflow was Query Monitor on a staging copy, plus EXPLAIN to confirm the indexes were actually in use.

Query Monitor’s Database Queries panel in dark mode. The sidebar lists Overview, Timeline, PHP Errors, Doing it Wrong, Database Queries (35, selected), Queries by Caller, Queries by Component, Timings and Logs. The Query column shows three SQL queries: SELECT option_name, option_value FROM wp_options WHERE autoload IN (‘yes’, ‘on’, ‘auto-on’, ‘auto’), then SELECT * FROM wp_users WHERE user_login = ‘admin’ LIMIT 1, then SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (1) ORDER BY umeta_id ASC.

Query Monitor lists every database query a page runs. Source: Query Monitor on WordPress.org

At the end, OP asked who else had tried the custom-table route. Michał backed the idea and named its cost.

Reddit reply from u/Coditive_: “Postmeta (and bloat that some plugins generate there) can become a huge pain on big, high-traffic sites. Something you can also think of is moving some data from postmeta to a custom table. At the cost of coding and setting it up (hooks, queries, etc.), you gain more control and flexibility.” The reply is signed ~MS.

Michał's reply on custom tables. Source: r/Wordpress

Another commenter noted that WooCommerce did the same with orders: High-Performance Order Storage keeps them in dedicated tables instead of the post tables. They also mentioned Index WP MySQL For Speed, a plugin that adds better indexes to the WordPress database.

You rarely get that kind of detail from documentation.


When a Calendly embed is enough

In a discussion about inheriting WordPress sites, Michał described a setup we’ve seen more than once. A site owner wanted visitors to book a time, so someone installed a booking plugin and several add-ons. If booking was all they needed, a Calendly embed would have done the job and left them with fewer things to update.

Sometimes the best advice is “You don’t need an agency for this.” A thread full of sales pitches is no use to the next person who finds it.


Not every question comes from a developer

In October 2026, php2shell was all over the news. It’s a pair of critical flaws in PHP itself that let attackers run their own code on a server, no login needed. PHP released fixes the same day the flaws went public, in versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

In one thread on r/Wordpress, OP said their company runs three basic WordPress sites, one of them a WooCommerce store, and asked whether they needed to do anything about “some PHP issue” everyone was talking about. Their IT person was, of course, on vacation without a laptop, and they weren’t sure what PHP had to do with WordPress.

The short answer was yes, update PHP now. Another person in the thread was already on PHP 8.4 and asked how often to update, and whether it’s safer to skip the newest version for a while. We told them to update to 8.4.27 first, since that’s the release with the php2shell fix. The move to 8.5 could wait, because 8.4 gets security fixes until the end of 2028.

Reddit thread. Another user, whose name is hidden, asks: “I’m on 8.4 but I see there is an 8.5 available. Do you have any advice on how often you should update or other guidelines (i.e. don’t go to the newest in case of bugs)?” u/Coditive_ replies that they want to be exactly on 8.4.27, the latest version at that moment. Moving from 8.4 to 8.5 is a good idea but doesn’t need to be rushed, because 8.4 has active support until the end of 2026 and security support until 2029. If they have staging, they should test the PHP update there first and then update the live server. With a custom theme or plugin, a developer can do a quick compatibility check, or they can do it themselves with AI help.

Our reply to a follow-up question in the php2shell thread. Source: r/Wordpress

Does Reddit still make sense when AI answers in seconds?

Anyone can paste a WordPress question into an AI chat and get an answer before we’ve finished reading the thread. A model can explain what switch_to_blog() does. But problems that only appear on real sites, like an older WooCommerce store with brands registered twice, reach the models through people who faced them and wrote about them. That’s why AI companies pay Reddit to use its threads as training data. If developers stop writing those answers, the models have nothing new to learn from.

A public reply also stays useful after OP has their answer. Anyone who searches for the same PHP question will find it.

We don’t know how many clients Reddit will bring us, and that’s not why we started. If you want to see what else we’ve answered, all our replies are on u/Coditive_.

Contact

Need a reliable partner?

Tell us what you want to build, improve, or validate, and we'll get back to you within one business day.