In the first quarter of 2026, while redefining the Lifehacker Premium paid community (see Launching Paid Membership Subscriptions from the Brand’s Earliest Stage), Raymond Hou (Raymond) made two related infrastructure decisions. He moved the community’s existing “Hacker Coins” check-in points system off the third-party Discord bot Mee6 and built a custom version; and, for selecting a platform to connect membership payments with Discord roles, he passed on the seemingly more flexible Recur and chose the more conservative but mature Teachify. Both decisions happened in January, with March 1 set as the unified launch date for the new system. This process also offers a concrete example of how “having development skills” after Raymond’s shift to A Full Shift to AI Agent Collaboration in 2026 changed his operating decisions.
What Are Hacker Coins, and Why Build Them In-House?
Hacker Coins are check-in points within the community. Members earn points by checking in to a designated channel with something like “three things I’ll do today,” then exchange them in the “Hacker Coins Store” for prizes such as physical books, online-course redemption codes, and branded souvenirs. Under the old system, the Mee6 bot issued and looked up points through commands such as /coins and /remove-coins.
A concrete tool limitation, rather than frustration, drove the custom build: Mee6 could not put redeemable products directly into the Notion database Raymond normally used, leaving prize management and the points system separate. Raymond’s judgment in the team channel was direct: since he now had development skills, rather than accommodating the bot’s limitations, he could “just make a new version.” The custom version awards points as soon as a check-in message is posted, uses /balance to look up a balance, consolidates product and member data in Notion, and adds hidden triggers as Easter eggs for fun.
The cost of the decision was deliberately controlled. Raymond chose to “run the old and new systems in parallel and set a stop-loss point.” The old Hacker Coins did not become invalid immediately; the leaderboard and historical records were preserved, and members could redeem their accumulated points through February 28. On March 1, the old points would be reset and the new system would take over. Processing redemptions also avoided using a deduction command that could distort the leaderboard. Instead, they used a separate page for manual bookkeeping, “letting the first version’s records remain in the past and preserving them intact.”
The Trade-Off Between Teachify and Recur
The platform choice concerned linking “paid subscription payments” with “Discord roles” in the upgraded membership system: successful payers should automatically receive the community role, and lose it when their membership expires. The candidates were the newer Recur and the established Teachify.
Raymond’s decision was based mainly on a peer’s practical feedback, rather than on a feature list alone. The peer pointed out that although Recur had Discord role functionality, few people were actually using it. Teachify, on the other hand, already had servers with thousands of members running the same integration, making its stability more verifiable. Given the explicit requirement—“at this stage, we only need a stable role integration”—Raymond chose the proven Teachify, leaving Recur as an option to assess later if he launched a SaaS or a small custom paid tool. This shows a preference: keep infrastructure stable and reserve experimentation for the product itself.
Teachify still involved friction. In a later discussion, Raymond noted that it did not allow unrestricted HTML, CSS, and JS uploads using a Vibe Coding workflow, limiting page-editing flexibility. Its domain structure (apex domain and subdomain) also meant existing course and checkout links could not be changed freely. These limitations were accepted as known costs rather than grounds to reverse the decision.
Significance and What Followed
Taken together, the two decisions reflect the same logic. At a key point in a major membership-system redesign, choose mature, verifiable solutions for core infrastructure (Teachify and a migration that runs old and new systems in parallel), and put the effort of custom building and experimentation into the parts that directly improve community experience and fit into the organization’s own data system (Hacker Coins). Building Hacker Coins also sent a signal: when “being able to code” became part of Raymond’s daily capabilities, decisions that once required making do with third-party tools could include “just build a more suitable one yourself.”
After the new system launched in March, public records offered a sign of community activity. In April 2026, Raymond described the members’ Discord voice channels—“the co-learning room, talent room, and sofa area; every voice channel is full of people”—providing indirect evidence that the membership and community-mechanism redesign had been taken up.1
Details have been de-identified: this entry records only the decision logic and trade-offs. It does not reproduce internal information such as the exact number of old points redeemed, product prices, member lists, or division of responsibilities.
Source
Footnotes
-
Raymond Hou, “The Remarkable Scene in the Paid Members’ Discord Tonight,” public Facebook post, 2026-04-18. View original ↩