Community + Code: Episode 27 - Miriam Schwab

๐ **Source:** [Community + Code: Episode 27 - Miriam Schwab](https://www.youtube.com/watch?v=_Tmz9qsXJvo)
> [!note]+ Document Notes
> tags: [community-building, open-source, elementor, agency-to-startup, wordpress-career]
> author: [MISSING]
> source: Community + Code
> reference: [https://www.youtube.com/watch?v=_Tmz9qsXJvo]
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> # ๐ท๏ธ Title: Community + Code: Episode 27 - Miriam Schwab
>
<!-- deep-read:sections start -->
## ๐งญ Table of Contents
- [๐ Summary](#-summary)
- [๐ Main Content](#-main-content)
- [๐๏ธ Notes](#๏ธ-notes)
- [๐ References](#-references)
- [๐ฃ๏ธ Paraphrase](#๏ธ-paraphrase)
- [๐ฐ Newsletter](#-newsletter)
- [โ
Action Items](#-action-items)
- [๐งช Hypotheses](#-hypotheses)
- [๐ Methodology](#-methodology)
- [โ Questions](#-questions)
- [๐ฎ Future Research](#-future-research)
- [๐ก Implications](#-implications)
- [๐ง Learning Styles Assessment](#-learning-styles-assessment)
- [๐ Accessibility Assessment](#-accessibility-assessment)
- [๐ DEIB Assessment](#-deib-assessment)
- [โ
Logical Validity](#-logical-validity)
- [๐ก๏ธ DARVO Analysis](#-darvo-analysis)
- [๐ฏ Conclusion](#-conclusion)
## ๐ Summary
- Miriam Schwab's journey from English literature graduate to Head of WordPress at Elementor, spanning 20 years in the WordPress ecosystem
- Built a successful 13-year agency before founding Stratic, a Jamstack-WordPress hybrid platform that served Fortune 500 companies
- Joined Elementor after acquisition, became the bridge between the 21-million-install company and the WordPress community
- Established Elementor's Five for the Future program and community presence at a scale most agencies never reach
- Demonstrates how technical curiosity, community relationships, and entrepreneurial thinking compound over decades
## ๐ Main Content
Miriam Schwab's career illustrates how deep specialization in WordPress can create unexpected opportunities across multiple business models. Starting as a freelance content writer with an English literature degree, she noticed websites were more interesting than the content she was writing for them. This observation led to self-teaching web development and positioning herself as one of Israel's first professional WordPress service providers around version 3.0.
Her 13-year agency focused on custom WordPress sites for tech companies and large nonprofits. The consistent learning curve and meaningful client work sustained her interest, though she maintained product ambitions throughout. When her children grew older, she transitioned to founding Stratic, combining WordPress's content management capabilities with Jamstack's performance benefits through static site generation.
Stratic solved a specific enterprise pain point: marketing teams wanted WordPress's familiar interface while technical leaders needed the performance and security of static sites. The platform attracted Fortune 500 companies, the UN, and government clients by serving as a bridge between these two constituencies within organizations.
Elementor acquired Stratic after a relationship that began years earlier at small Israeli WordCamps. The founders had sponsored events when they were "three guys with a folding table," creating connections that lasted through their growth to 21 million active installs. This demonstrates how community relationships can create business opportunities on unexpected timelines.
As Head of WordPress at Elementor, Schwab created a role that didn't previously exist to address specific gaps in how the company engaged with the WordPress ecosystem. Her responsibilities include managing the Five for the Future program, ensuring plugin guideline compliance, maintaining partner relationships, and serving as the company's community face.
### ๐๏ธ Notes
#### โฑ๏ธ [00:00:00](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=0) Introduction and Background
- Two decades in WordPress, started as freelance content writer
- Met at post-COVID WordCamp US San Diego when representing newly-acquired Stratic
- English literature degree after switching from computer science due to Hebrew language barriers
#### โฑ๏ธ [00:03:12](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=192) Early Technology Interest
- Father bought PC when she was eight, got second computer for kids
- Typed code from books to create simple games
- Early internet fascination with connecting to strangers globally
- Websites became more interesting than content writing
#### โฑ๏ธ [00:08:45](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=525) Agency to Startup Journey
- 13-year agency serving tech companies and nonprofits in Israel
- Well-positioned as early professional WordPress adopter around version 3.0
- Constant learning curve kept work interesting
- Product ambitions throughout but focused on agency until kids were older
#### โฑ๏ธ [00:15:30](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=930) Stratic Platform Vision
- Combined WordPress backend with static site deployment
- Solved enterprise conflict between marketing teams (wanted WordPress) and technical leaders (needed performance/security)
- Jamstack trend inspiration from Matt Biilmann's Netlify case study
- Fortune 500 companies, governments, UN as clients
#### โฑ๏ธ [00:18:45](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=1125) Elementor Relationship History
- Met founders at early Israeli WordCamps when they were "three guys with a folding table"
- Started with Pojo theme product before Elementor
- Long relationship before acquisition opportunity emerged
- Awkward first WordCamp representing Elementor week after joining
#### โฑ๏ธ [00:25:00](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=1500) WordPress Platform Loyalty
- Tested other platforms but always frustrated by limitations
- WordPress consistently enabled achieving goals
- Self-described "fake developer" who understands tech but doesn't want to write code
- Community quality and learning resources kept her engaged
#### โฑ๏ธ [00:32:15](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=1935) Head of WordPress Role Definition
- Created position to address community engagement gaps
- Team came from other tech companies, not WordPress background
- Manages Five for the Future program, plugin compliance, partner relationships
- First Elementor speaker, created speaking program for others
#### โฑ๏ธ [00:38:00](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=2280) Role Complexity and Prioritization
- Entrepreneurial position requiring self-motivation
- Similar to CEO work: relationship-driven, staying current on developments
- Creates internal AI/WordPress newsletter
- Reports to CEO but operates with significant autonomy
#### โฑ๏ธ [00:42:30](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=2550) Five for the Future Program
- Leadership knew it was "the right thing to do" before she advocated
- Financial sponsorship rather than internal contributor time
- Started with performance team, expanded to multiple teams
- Brand investment argument alongside moral imperative
#### โฑ๏ธ [00:47:45](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=2865) Open Source Contribution Philosophy
- Realistic expectations for smaller agencies with tight margins
- Larger companies have responsibility once thriving
- Open source contribution as brand investment in ecosystem
- "Return on connection" rather than direct ROI
#### โฑ๏ธ [00:52:00](https://www.youtube.com/watch?v=_Tmz9qsXJvo&t=3120) Elementor's Growth Success
- 21 million active installs, became #1 WordPress plugin
- Right product at right time, initially free version only
- Customer feedback focus despite massive scale
- Careful hiring process and talented team
- Humble leadership with strategic focus
## ๐ References
- [Community + Code Podcast](https://www.youtube.com/watch?v=_Tmz9qsXJvo)
- [Miriam Schwab's website](https://miriamschwab.me)
- Stratic platform (acquired by Elementor)
- Five for the Future WordPress program
- WordCamp events and WordPress community
## ๐ฃ๏ธ Paraphrase
Miriam Schwab's career demonstrates how deep specialization in WordPress can create compound opportunities across different business models. She transitioned from content writing to agency work to startup founder to corporate community leader by maintaining consistent engagement with the WordPress ecosystem over two decades. Her role at Elementor bridges a 21-million-install company with the open source community, showing how relationships built at small events can scale to enterprise impact. The interview reveals how technical curiosity, community investment, and entrepreneurial thinking can create career paths that didn't exist when you started.
## ๐ฐ Newsletter
Ever wonder how a content writer becomes the WordPress community bridge for the world's most popular plugin? Miriam Schwab's journey from freelance writing to heading WordPress relations at Elementor (21 million installs!) shows how curiosity and community connections compound over decades. She started noticing websites were more interesting than the content she wrote for them, taught herself WordPress around version 3.0, built a 13-year agency, founded a Jamstack startup that served Fortune 500 companies, and now manages Elementor's Five for the Future program. Her story proves that staying curious about the tools you use daily and showing up consistently in community spaces can open doors you never imagined. Plus, she just built her new site with AI and WordPress - because even WordPress veterans keep experimenting!
## โ
Action Items
#### DevRel
- Document "return on connection" metrics for community event attendance and sponsorships
- Create internal newsletters about industry developments to keep non-community teams informed
- Establish clear pathways from community engagement to business outcomes
- Develop speaking programs that scale beyond single advocates
#### Community
- Build relationships at small events that may scale over time - the "folding table" sponsors of today could be major partners tomorrow
- Create bridge roles between large companies and open source communities when teams lack ecosystem context
- Establish Five for the Future programs focused on specific pain points (performance, security, etc.)
- Maintain realistic expectations for contribution based on company size and resources
#### WordPress
- Core: Document pathways for large companies to engage meaningfully with contribution teams
- Community: Create mentorship programs connecting established agencies with newer community members
- Marketing: Highlight success stories of long-term community relationship building
- Five for the Future: Develop targeted sponsorship opportunities for specific WordPress teams and initiatives
## ๐งช Hypotheses
- Community relationships built at small events create disproportionate business value over 5-10 year timeframes
- Companies with 1M+ users have moral and business imperatives to contribute to open source ecosystems
- Bridge roles between large companies and open source communities become essential as products scale
- Deep platform specialization creates more career opportunities than broad technical skills
- Self-taught "fake developers" can succeed in technical roles by understanding systems without writing code
- Open source contribution functions as brand investment with unmeasurable but significant returns
## ๐ Methodology
- Longitudinal career tracking: Follow WordPress community members over 10-20 year periods to identify relationship ROI patterns
- Contribution impact analysis: Measure business outcomes for companies with established Five for the Future programs
- Community bridge effectiveness: Survey large WordPress companies on community engagement gaps before/after dedicated community roles
- Platform specialization outcomes: Compare career trajectories of WordPress specialists vs. generalist developers
- Event relationship mapping: Track business relationships that originate at WordCamps and other community events
## โ Questions
- How do you quantify "return on connection" from community events and long-term relationship building?
- What organizational structures best support bridge roles between large companies and open source communities?
- How should contribution expectations scale with company size and revenue in WordPress ecosystem?
- What percentage of WordPress businesses should realistically be expected to contribute beyond using the platform?
- How do you maintain entrepreneurial autonomy within large corporate structures?
## ๐ฎ Future Research
- Impact measurement frameworks for open source community investment by large companies
- Career pathway analysis for WordPress ecosystem professionals across different business models
- Relationship network effects in open source communities over extended time periods
- Organizational design patterns for community-facing roles in technology companies
- Scaling challenges for community-driven companies as they reach enterprise adoption levels
## ๐ก Implications
- **Practice**: Deep platform specialization may create more opportunities than broad technical skills
- **Policy**: Large WordPress companies need clear contribution expectations and support frameworks
- **Education**: Community relationship building should be taught as professional development skill
- **Funding**: Five for the Future sponsorship models could be replicated across other open source projects
- **Career Development**: Bridge roles between technical and community functions will become increasingly valuable
## ๐ง Learning Styles Assessment
Reading level estimate: Grade 12-13 (Flesch-Kincaid). Professional vocabulary with conversational tone.
#### ๐ Visual learners
- Present: Career timeline visualization showing transitions between roles and companies
- Improve: Infographic of WordPress ecosystem relationships, Elementor growth charts, Five for the Future program structure diagrams
#### ๐ Aural learners
- Present: Full podcast audio, conversational interview format
- Improve: Audio highlights reel, key quotes for sharing, transcript with speaker timestamps
#### ๐ฃ๏ธ Verbal learners
- Present: Clear explanations of technical concepts, analogies for complex business relationships
- Improve: Glossary of WordPress ecosystem terms, comparison tables of different career paths
#### ๐งฉ Kinesthetic learners
- Present: Career decision points that listeners can relate to their own situations
- Improve: Interactive career path explorer, "What would you do?" decision scenarios, contribution calculator
#### ๐ง Logical learners
- Present: Clear chronological progression, cause-and-effect relationships in career development
- Improve: Decision trees for career transitions, ROI frameworks for community investment, contribution impact metrics
#### ๐งโ๐คโ๐ง Social learners
- Present: Emphasis on community relationships and networking value
- Improve: Discussion prompts about community building, networking strategy worksheets, mentor matching frameworks
#### ๐งโโ๏ธ Solitary learners
- Present: Individual reflection opportunities about career paths and specialization choices
- Improve: Self-assessment tools for community involvement, personal contribution planning templates
#### ๐ฟ Naturalistic learners
- Present: Ecosystem metaphors for WordPress community relationships
- Improve: Community sustainability frameworks, contribution lifecycle thinking, long-term relationship cultivation strategies
## ๐ Accessibility Assessment
#### Screen reader semantics
- Present: Clear heading structure, speaker identification in transcript
- Improve: Speaker role descriptions, technical term definitions, link context for external references
#### Keyboard navigation
- Present: Standard video player controls, transcript text selection
- Improve: Timestamp navigation shortcuts, searchable transcript, chapter markers
#### Contrast and readability
- Present: Clear video quality, readable transcript formatting
- Improve: High contrast transcript options, adjustable text size controls
#### Media and captions
- Present: Full transcript provided
- Improve: Synchronized captions, speaker identification in captions, key term highlighting
## ๐ DEIB Assessment
#### Cultural breadth
- Present: International perspective (Israel to US), multiple business models represented
- Improve: More diverse geographic examples, acknowledgment of privilege in network access
#### Inclusive language
- Present: Avoids jargon where possible, explains technical concepts
- Improve: Define industry-specific terms, provide context for WordPress ecosystem newcomers
#### Representation
- Present: Female technology leader, non-traditional educational background
- Improve: Acknowledge barriers others might face, discuss diversity in WordPress community
#### Psychological safety
- Present: Honest discussion of challenges and failures alongside successes
- Improve: Content warnings for business stress discussions, alternative pathway validation
## โ
Logical Validity
#### Strong reasoning
- **Career progression logic**: Clear cause-and-effect relationships between community involvement and professional opportunities with specific examples (WordCamp connections leading to acquisition)
- **Platform specialization benefits**: Well-supported argument that deep WordPress knowledge created more opportunities than broad technical skills
- **Community investment ROI**: Logical framework for treating open source contribution as brand investment rather than direct revenue driver
#### Fallacies
- **Survivorship bias**: Success story may not reflect typical outcomes for community-focused career strategies - not all WordCamp relationships lead to acquisitions
- **Post hoc reasoning**: Some career successes attributed to community involvement may have resulted from other factors like market timing or individual talent
#### Tone of voice
- **Conversational and authentic**: Natural interview flow with genuine enthusiasm for WordPress community and technology
- **Humble expertise**: Acknowledges luck and timing while demonstrating deep knowledge and strategic thinking
## ๐ก๏ธ DARVO Analysis
No DARVO patterns detected. The interview maintains a collaborative, growth-minded tone throughout with honest acknowledgment of challenges and failures alongside successes.
## ๐ฏ Conclusion
Miriam Schwab's career trajectory demonstrates how consistent community engagement and deep platform specialization can create compound opportunities across multiple business models. Her role bridging Elementor's 21-million-install scale with WordPress's open source community illustrates the growing importance of dedicated community professionals as technology companies scale. The key insight for WordPress professionals is that relationship building at community events and sustained ecosystem engagement often creates more career value than purely technical skills, though both remain important for long-term success.
---
## Full Transcript
[00:19] Hi, welcome back to Community and Code.<br>[00:21] I'm Chris, Jazz Sequence on the<br>[00:23] internet, and today we've got a guest<br>[00:25] I've been wanting to get on the show for<br>[00:26] a while. Miriam Schwab has been in the<br>[00:29] WordPress world for two decades. I first<br>[00:31] met her several years ago at Word Camp<br>[00:33] US in San Diego, which was the one that<br>[00:36] was the first one after COVID when we<br>[00:38] were all still trying to figure out how<br>[00:39] to stand next to each other, which also<br>[00:41] happened to be right after her company<br>[00:43] Stratic had just gotten acquired by<br>[00:45] Elementor. And she was sent to represent<br>[00:47] a company she had only just barely<br>[00:48] joined. Miriam started as a freelance<br>[00:51] content writer who noticed that the<br>[00:53] websites she was building were actually<br>[00:54] more interesting than the writing<br>[00:56] itself. So, she taught herself how to<br>[00:58] build them and then built a 13-year<br>[01:00] agency serving tech companies and<br>[01:01] nonprofits in Israel. Then, she went<br>[01:04] full startup mode, co-founded Stratic,<br>[01:06] raised venture capital, got into<br>[01:07] accelerators, the whole nine yards.<br>[01:09] Stratic ended up with Fortune 500<br>[01:11] companies and governments on it. And<br>[01:13] then Elementor acquired it, which is how<br>[01:15] she ended up as head of WordPress at<br>[01:18] Elementor, a title that basically means<br>[01:20] she does everything that keeps the most<br>[01:22] installed WordPress plugin in the world<br>[01:25] connected to the community that made it<br>[01:27] successful. We talked about what it's<br>[01:29] actually like to build a community<br>[01:31] presence inside a 21 million install<br>[01:34] company. Yes, you got that number right.<br>[01:36] why she thinks contributing to open<br>[01:38] source is a brand investment and how the<br>[01:40] connection she made with the Elementor<br>[01:42] founders at a tiny word camp in Israel<br>[01:45] many years ago eventually led to all of<br>[01:47] this. Let's get to it. Welcome to<br>[01:50] Community and Code, the podcast where we<br>[01:51] talk to the human beings behind the<br>[01:53] commits. And I'm here today with Miriam<br>[01:55] Schwab. Miriam is a head of WordPress at<br>[02:00] Elementor. uh longtime WordPress uh<br>[02:03] developer, contributor, uh been in a lot<br>[02:06] of WordPressy things for a very long<br>[02:08] time. Um speaker, uh mentor, all sorts<br>[02:12] of things. Miriam, welcome to the show<br>[02:14] and tell us about yourself.<br>[02:16] >> Well, thank you for having me. Um about<br>[02:19] myself. Well, I I got into WordPress<br>[02:24] when I was actually providing freelance<br>[02:28] services um for content writing. That's<br>[02:32] what I was doing first. My degree is in<br>[02:34] English English literature and that<br>[02:35] seemed like a pretty natural progression<br>[02:38] from that. But the truth is that when I<br>[02:42] started studying in university, I<br>[02:44] started I was studying computer science<br>[02:46] actually. But um I had just moved to<br>[02:50] Israel and while I knew Hebrew quite<br>[02:52] well, there's a difference between<br>[02:54] knowing Hebrew for like standard<br>[02:57] conversation and studying computer<br>[02:58] science in Hebrew.<br>[03:00] >> That is a whole other level. And I found<br>[03:03] that I really just didn't know what they<br>[03:05] were talking about. Like I didn't know<br>[03:07] what was going on. I didn't know what<br>[03:09] the words meant. Um, and so I decided to<br>[03:14] switch into basically the only thing<br>[03:15] that was taught in English at the time<br>[03:16] in Israel, which was computer, which was<br>[03:18] English literature. I've always had a<br>[03:20] dual love for technology and act and and<br>[03:24] literature. Actually avid reader. Um, I<br>[03:27] do also enjoy writing, but also have<br>[03:31] loved technology since I was a kid. Um,<br>[03:34] my dad bought us our first like PC. I<br>[03:38] don't know how old I was, like maybe<br>[03:39] eight. But he was he bought two<br>[03:42] actually. First he had one and I think<br>[03:44] we were driving him crazy. We're like<br>[03:45] especially me that we were always we<br>[03:47] always wanted to use it. It was so cool<br>[03:49] that he actually got a second one for us<br>[03:51] in his office space in our house. Like<br>[03:53] he would be on one and we I well I would<br>[03:55] be on the other. Um and he would buy me<br>[03:57] these coding books where they would just<br>[04:00] have the code on like printed pages like<br>[04:02] this old school, right?<br>[04:04] >> Yeah. and I would type it in and then it<br>[04:06] would turn into like a snake game or<br>[04:07] something and I was like amazed. And he<br>[04:09] would also buy me these magazines. Um I<br>[04:12] think it was called 321 contact. It was<br>[04:14] like a science magazine and you know it<br>[04:17] was about like nature science and tech<br>[04:20] science. I always loved the things about<br>[04:21] space and all that. Anyway, so I always<br>[04:23] had like very strong interest uh and<br>[04:27] love for where technology was going. Um,<br>[04:29] but it just the the way things worked<br>[04:31] out was that I studied English<br>[04:33] literature, which I actually really<br>[04:34] loved. Um, but then after I finished it,<br>[04:37] I figured, okay, I'm going to work in<br>[04:38] that kind of space, which I did. But<br>[04:40] then what was happening was the content<br>[04:43] that I was writing was going into<br>[04:45] websites. And the websites were way more<br>[04:48] interesting to me than the content I was<br>[04:49] writing. I was like, and I like I was<br>[04:52] enamored with the internet and what it<br>[04:54] offered. Made so many things accessible<br>[04:57] to all of us. you know any qu now you<br>[05:00] know with AI it's like a whole other<br>[05:01] level but then already just the idea<br>[05:03] that I could search for information and<br>[05:05] get it and um and that websites gave<br>[05:07] people a way to<br>[05:10] be in front of many other people so I<br>[05:14] started to teach myself to build<br>[05:15] websites um that was the other wonderful<br>[05:18] amazing thing about the internet that um<br>[05:20] it was very embedded in an open-source<br>[05:24] philosophy and approach and that's what<br>[05:26] made it what it is so people also share<br>[05:28] share a lot of information online um so<br>[05:31] I could learn from others like basically<br>[05:32] I would just search for okay how do I do<br>[05:34] this how do I do that you know Stack<br>[05:35] Overflow all that kind of stuff and then<br>[05:37] uh yeah so I taught myself to build<br>[05:39] websites and started to offer that as a<br>[05:40] service and then things went from there<br>[05:44] >> I remember the very first time I<br>[05:48] experienced the internet I was probably<br>[05:50] at a library on one of their computers<br>[05:52] they just barely got like computers<br>[05:54] hooked up to the internet or something<br>[05:56] probably dialup I don't know It had to<br>[05:58] have been dialup. Um, and like like that<br>[06:02] was like when Yahoo<br>[06:04] was like what you used and um like I<br>[06:09] mean there was a couple other like<br>[06:10] directories but like Yahoo was the thing<br>[06:13] and like there was just like just like<br>[06:15] lists of links and you didn't know what<br>[06:17] any of the links were and you would<br>[06:19] click on a link at random and it would<br>[06:20] take you to some weird site. you're<br>[06:21] like, "Okay, this is interesting." And<br>[06:23] then at the bottom of that weird site,<br>[06:24] there'd be like<br>[06:25] >> uh find the next uh site in this web<br>[06:28] ring.<br>[06:29] >> And then you would click on that and<br>[06:30] you'd get to some other random site that<br>[06:32] was tangentially related to the last<br>[06:34] site you had on. And then you just get<br>[06:35] into these like you deep rabbit holes of<br>[06:38] like weird interlin<br>[06:41] pieces like parts of because the only<br>[06:42] way that you would know<br>[06:45] how like the only way that you would<br>[06:46] find another site was from some other<br>[06:49] site that might have linked to it<br>[06:50] through like a web ring or a guest book<br>[06:52] or like something like because there<br>[06:54] wasn't there wasn't there wasn't ranking<br>[06:57] in search like Google search engine<br>[07:00] ranking wasn't a thing like it would<br>[07:02] like there was no Google like it was<br>[07:03] just like a bunch of just random text<br>[07:06] pages that had a hyperlink that took you<br>[07:09] someplace like you had no idea where you<br>[07:11] were going.<br>[07:12] >> Right. Totally. It was a weird and<br>[07:15] wonderful thing. It was like we all<br>[07:17] could get access to other people's<br>[07:20] weird, random, cool, fascinating,<br>[07:23] strange like ideas and representations<br>[07:26] of themselves. And it was so<br>[07:28] interesting. Like that was the other<br>[07:31] thing that I really loved about the<br>[07:32] internet specifically like beyond<br>[07:34] computers and technology was that you<br>[07:37] could become you could just you know<br>[07:40] talk to someone regardless of where they<br>[07:42] were<br>[07:43] >> and hear their thoughts and communicate<br>[07:46] with them. Whereas in the past it was a<br>[07:49] phone call was doable but okay that<br>[07:51] wasn't gonna happen with like strangers<br>[07:53] and you know maybe email at some point<br>[07:57] but like that was a whole other level of<br>[07:59] connection with people removing the<br>[08:02] constraint of<br>[08:04] geographic proximity which was always a<br>[08:07] type of constraint and that also was so<br>[08:09] cool to me.<br>[08:10] >> Yeah. Yeah. For sure. So like every one<br>[08:12] of these these web pages on the internet<br>[08:14] on the the very early internet like<br>[08:16] represented a single human being<br>[08:18] somewhere else in the world that was<br>[08:21] completely different and and separate<br>[08:22] from you that you would never have expo<br>[08:24] been exposed to previously. And I I've<br>[08:26] told this story before but I paid for<br>[08:29] access to a BBS before I paid for access<br>[08:31] to the internet. So like I was like even<br>[08:34] even while I was going to the library<br>[08:36] and like like browsing online, the thing<br>[08:38] that I found most interesting was<br>[08:40] hanging out with people in chat rooms.<br>[08:42] Um,<br>[08:43] >> and like there that that was also like a<br>[08:46] weird weird wild wonderful space of like<br>[08:50] like the dialup and then like hyper term<br>[08:54] and like like logging into this like<br>[08:58] textbased thing and like navigating<br>[09:00] through like an interconnected uh web of<br>[09:03] these like there's like a network that I<br>[09:05] uh that I subscribe to like there is a<br>[09:07] network of these BBS servers and so you<br>[09:09] would pick which server in which city<br>[09:11] you would want to hang out in um yeah uh<br>[09:16] so so you got you got started writing uh<br>[09:19] on websites and then you started getting<br>[09:21] interested in websites when when we met<br>[09:24] I think the first time we met it was uh<br>[09:26] Word Camp San Diego or no Word Camp US<br>[09:28] in San Diego. Um and uh at the time uh<br>[09:33] it was the tail end I think of Stratic<br>[09:35] because I think like you were uh you<br>[09:37] were just like it it had had not yet<br>[09:40] been announced that Elementor had<br>[09:41] acquired Stratic which was your agency.<br>[09:44] Um so where is the where is the<br>[09:46] intervening years between like uh making<br>[09:49] your first website to uh running your<br>[09:52] own agency that gets acquired by<br>[09:54] Elementor? Like what is what happens in<br>[09:56] the in between time? So actually I went<br>[09:59] agency<br>[10:01] tech company startup that was stratic.<br>[10:04] Stratic was a platform for publishing<br>[10:06] WordPress website<br>[10:08] right<br>[10:09] >> and then acquisition by elementor. So<br>[10:11] >> basically it went like this.<br>[10:14] >> Discovered that I love websites. Start<br>[10:16] building websites. Start to add that as<br>[10:19] an offering in addition to content.<br>[10:22] Start to push that more as an offering<br>[10:24] because it was much more fun for me. Um,<br>[10:26] and then that like positioned me to be<br>[10:28] one of the first people to offer<br>[10:29] WordPress as a professional solution,<br>[10:32] not just as a blogging platform for<br>[10:34] amateurs uh, in Israel actually. So I<br>[10:38] was well positioned when people started<br>[10:40] to turn around around version three of<br>[10:42] WordPress and were like, "Oh, actually<br>[10:44] this is a great option for our company<br>[10:46] or organization websites. Who can do<br>[10:49] that for us?" Oh, Miriam, because I was<br>[10:50] already I was already doing it and<br>[10:52] people like kind of started, you know,<br>[10:53] it's like word of mouth and whatever.<br>[10:55] So, so started to do that and building<br>[10:58] custom WordPress websites for uh<br>[11:00] companies, a lot of tech companies and<br>[11:02] large nonprofits that you know needed<br>[11:04] specific attention for their activity.<br>[11:07] Um it was just me at first and then grew<br>[11:09] it out to be an agency. So did that for<br>[11:11] 13 years. All along the way, I did have<br>[11:13] ideas for products.<br>[11:15] >> Like especially as the years went on, I<br>[11:16] had like I had more and more of like a a<br>[11:19] push to move into the product space, but<br>[11:23] >> I I gave it a few goes, but um at the<br>[11:26] time, so like I had I was having kids<br>[11:28] and I was, you know, they were little<br>[11:30] and the agency and I had to force myself<br>[11:33] to realize that like you really have to<br>[11:35] learn to say no even to yourself. like I<br>[11:38] when I bit off more than I could chew,<br>[11:40] too many things paid a price. So I left<br>[11:43] that and kept building sites and really<br>[11:45] enjoyed it. Like that was like 13 years<br>[11:47] of offering services. Um it was always<br>[11:51] interesting because the companies were<br>[11:53] interesting or the organizations like<br>[11:56] that made the work also meaningful and<br>[11:57] also each one had their own you know<br>[12:00] unique take or need and so we had to<br>[12:03] learn to do things that we hadn't done<br>[12:04] before. there was constant learning<br>[12:05] curve but at a certain point it did<br>[12:07] start to feel like okay I've done this<br>[12:10] for like quite a while also my kids were<br>[12:12] getting bigger and I wanted like a a<br>[12:16] next challenge<br>[12:18] and I had always I had really wanted to<br>[12:21] move into the product space and then<br>[12:23] that timing was around the start of the<br>[12:26] Jamstack trend<br>[12:29] >> and um I read a blog post by Matt Bilman<br>[12:32] the one of the co-founders of Netlefi<br>[12:35] where he did a case study where he<br>[12:37] generated a static version of a<br>[12:38] WordPress site and of course performance<br>[12:40] was better and you know all that the<br>[12:43] scalability. I was like oh my goodness<br>[12:45] that's really cool. I I could see that<br>[12:47] Jamstack had issues because it led<br>[12:50] people to having to do I don't know how<br>[12:52] else to describe it. Too many<br>[12:54] somersaults in the air to achieve the<br>[12:55] same thing that WordPress was<br>[12:58] >> you know like you're reinventing the<br>[12:59] wheel the whole time.<br>[13:00] >> Yeah. But I thought, what if we combine<br>[13:03] these two worlds, give people WordPress<br>[13:05] as their like uh source of truth where<br>[13:08] they work and they know how to work and<br>[13:10] marketing teams feel comfortable, but<br>[13:12] that's like hidden. It's uh it's almost<br>[13:14] like a staging site and then they deploy<br>[13:16] a static version of the site to the<br>[13:18] internet and then that site is super<br>[13:20] fast, resilient, scalable, like it<br>[13:22] solves all their issues. A lot of the<br>[13:25] companies that came on board with<br>[13:27] Stratic, it was driven by their CISOs or<br>[13:30] someone who was like a a CTO type person<br>[13:34] who couldn't stand this the company was<br>[13:37] running a WordPress site. They were not<br>[13:39] sleeping at night because of it. These<br>[13:41] were people who were like let's say they<br>[13:42] were tech companies a lot of them you<br>[13:45] know their tech stack is super high-end<br>[13:47] you know um with an eye towards the<br>[13:50] future but then their marketing team is<br>[13:52] using what they saw as like a legacy<br>[13:53] platform but the marketing team wanted<br>[13:55] it because it was their power tool. So<br>[13:58] Stratic bridged those two groups within<br>[14:00] the company gave the marketing company<br>[14:02] team what they wanted and then the tech<br>[14:04] team or the tech leaders could sleep at<br>[14:06] night. So um that was like the vision of<br>[14:08] it and it ended up coming to fruition<br>[14:10] with uh Fortune 500 companies using it,<br>[14:12] governments, the UN um you know all<br>[14:15] sorts. So um so built it up raised uh<br>[14:19] venture capital funding for that and did<br>[14:21] that for like six years. I was in some<br>[14:23] startup accelerators at the beginning<br>[14:25] which was a great experience. The whole<br>[14:26] thing was a great experience like wild<br>[14:28] fun great learning experience. Met<br>[14:30] amazing people lots of sleepless nights<br>[14:33] for me and my co-founder and our team. a<br>[14:35] lot of pain and suffering also building<br>[14:38] a startup is you you have to go into<br>[14:41] with a lot of uh emotional strength or<br>[14:43] something. But um but yeah and then uh<br>[14:49] Elementor I knew the founders um they I<br>[14:53] met them first when I was organizing<br>[14:55] word camps in Israel. So, one of the<br>[14:56] first ones that I did, they sponsored at<br>[14:59] the time. They were like three guys with<br>[15:02] like a folding table that was like they<br>[15:03] were so small. And um I think the first<br>[15:06] time they sponsored it was like<br>[15:07] pre-elementor. They had um a product<br>[15:09] before that that they called Pojo. It<br>[15:11] was like a theme that was more<br>[15:13] customizable, but then they took that to<br>[15:14] the next level with Elementor. um but<br>[15:16] they would sponsor and so we always<br>[15:17] stayed in touch um and were friends and<br>[15:20] then they were watching Stratic and had<br>[15:23] an eye on it and and that's where we<br>[15:26] ended up but when I saw you in San Diego<br>[15:29] first of all that was a weird word camp<br>[15:31] remember that<br>[15:32] >> like co<br>[15:34] >> it was it was it was the first thing<br>[15:36] postcoid I think yeah it was the first<br>[15:38] big event postco and people were<br>[15:40] freaking out about it too like they<br>[15:42] >> don't stand too close to me wear many<br>[15:45] masks Y it was really limited. It was<br>[15:47] like 100 people.<br>[15:50] >> It was more than 100 people.<br>[15:52] >> More. It was like some really small<br>[15:54] amount.<br>[15:54] >> It was definitely small for for a word<br>[15:56] camp for sure.<br>[15:57] >> Yeah, it was. I I really think it wasn't<br>[15:59] more than 200 people. I remember the<br>[16:00] number being like super small. Um but it<br>[16:03] was right like like right after like<br>[16:06] maybe the week after Estratic had joined<br>[16:09] Elementor like we were super new there.<br>[16:12] I was trying to figure out like I I felt<br>[16:15] a little bit like what am I doing here?<br>[16:17] >> Yeah.<br>[16:18] >> Do<br>[16:19] um and it was the first time I went to<br>[16:21] an event with Elementor.<br>[16:23] >> Um<br>[16:24] and I was just I was just like trying to<br>[16:27] figure out my place in the in the<br>[16:29] company like from that perspective. So<br>[16:32] yeah, that's met.<br>[16:33] >> Yeah. No, I I remember that. I remember<br>[16:35] you like talking about how like your<br>[16:37] your company was just acquired and you<br>[16:39] really didn't know what your title was<br>[16:42] or what you would be doing anymore, but<br>[16:44] like here you are.<br>[16:46] >> Yeah. They're like obviously you should<br>[16:48] go to Word Camp because like you know<br>[16:51] they know they know me. They knew me and<br>[16:53] like and my involvement in the WordPress<br>[16:54] community. So if anyone's going to go to<br>[16:55] word camp with elementary it should be<br>[16:57] me. like I didn't yet feel like part of<br>[17:00] the team and<br>[17:03] yeah it was it was very it was like a<br>[17:06] bit awkward for me. So yeah that that's<br>[17:10] kind of the journey more or less from<br>[17:12] agency to stratic to elements. Uh, I<br>[17:16] want to take a a step back and I want to<br>[17:18] ask, uh, was there ever like like was<br>[17:21] there ever something else that you<br>[17:23] looked at besides WordPress or have you<br>[17:25] been like deep into WordPress from day<br>[17:28] one?<br>[17:30] >> You know, sometimes when I've been<br>[17:31] interviewed in the past, they're like,<br>[17:33] uh, what are your other interests and<br>[17:34] hobbies? You know, that kind of thing.<br>[17:37] I'm like, I I'm just I have none.<br>[17:42] I have always been all in on WordPress<br>[17:45] like<br>[17:47] you know I think one of the there's like<br>[17:49] a few reasons for that. Uh I always<br>[17:51] found it really fun and interesting.<br>[17:53] There's always something new to learn<br>[17:54] which is which matters to me. So it was<br>[17:56] it was not boring. Um and really the<br>[18:00] people like I really just loved meeting<br>[18:02] the community. When I started going to<br>[18:04] like more global work camps, I, you<br>[18:07] know, I met people that I had been<br>[18:08] following or connected with online and<br>[18:10] then you meet them in person, it's a<br>[18:11] whole other story.<br>[18:13] And I just, you know, I really loved<br>[18:15] meeting people and seeing what they were<br>[18:16] working on. And it just continuously<br>[18:19] stayed interesting and fun and nice,<br>[18:22] like just a really nice, pleasant,<br>[18:24] um, good-hearted, I would say, like I<br>[18:27] don't know, community. So, so I've I've<br>[18:30] always been in it. You know, obviously<br>[18:32] throughout the years as things develop<br>[18:35] and evolve like on on the web and in<br>[18:38] tech, I've looked at other solutions to<br>[18:41] see if, you know, I don't want to be<br>[18:42] left behind and I don't, you know, I<br>[18:44] want to make sure that also, let's say,<br>[18:46] in my agency day days, to make sure that<br>[18:48] we're offering the right solution for<br>[18:49] them. But every time I tested something<br>[18:51] out, I got frustrated by it. It was<br>[18:53] always limited. Um it just it was never<br>[18:57] as good and it was I never felt as good<br>[19:00] working with it. So uh you know I dabble<br>[19:02] but like in the end just just stuck with<br>[19:05] it and<br>[19:07] yeah I'm like a onetrick pony.<br>[19:10] I mean, you know, like I I sort of had a<br>[19:13] similar experience when I was<br>[19:14] freelancing is like um when I first<br>[19:17] started freelancing, um I was working<br>[19:19] for a company and I was like a contract<br>[19:22] freelancer and they sort of had their<br>[19:24] own way of doing things which involved<br>[19:27] um getting like doing your whole design<br>[19:30] in Photoshop and then using the slicing<br>[19:33] tool to like make a HTML like tablebased<br>[19:37] website out of that. Um that was like<br>[19:39] the very early days. Um so that was all<br>[19:42] like just straight up HTML. But um but<br>[19:46] we also used Zen Cart uh whenever there<br>[19:49] was an e-commerce platform. So I got<br>[19:51] pretty good at at styling that. But when<br>[19:53] I broke away and started freelancing on<br>[19:55] my own, um Zen Cart was still a thing<br>[19:58] that I was doing for a little bit. Um uh<br>[20:00] just because I was familiar with it. But<br>[20:02] like I played a little bit in Jumla. I<br>[20:04] played a little bit in Magento. Um but<br>[20:08] uh but WordPress was the thing like when<br>[20:10] I started using it for myself like that<br>[20:13] was just so much easier when especially<br>[20:15] like because at the time I think what I<br>[20:17] was doing was like I had found a script<br>[20:20] that would essentially like it would be<br>[20:22] you'd make an HTML page and then there's<br>[20:24] like a little JavaScript uh thing that<br>[20:25] you would put in there and then so like<br>[20:27] this area of the page is editable from<br>[20:31] some kind of like a backend kind of<br>[20:33] thing through this JavaScript thing and<br>[20:35] it would actually write changes to the<br>[20:37] HTML, right? Um, and that was like that<br>[20:40] was like the thing that I would do if if<br>[20:42] somebody needed to update their site on<br>[20:44] their own, um, was was write that in.<br>[20:47] And I was like, when I found WordPress,<br>[20:49] it's like, okay, so that's easier and<br>[20:52] there's so much more stuff here. Like,<br>[20:54] why am I ever doing anything else like<br>[20:56] that? Um, and I think there was a period<br>[20:58] of time where I'm like, okay, let's make<br>[21:00] sure I'm doing the right thing. And I<br>[21:01] tried all the other CMSs and and<br>[21:03] installed them and gave them a go. And I<br>[21:06] think Expression Engine was a thing that<br>[21:08] was big at the time. And like uh<br>[21:11] >> you know what I even tried for some<br>[21:12] reason? Cold Fusion. I don't know if you<br>[21:14] remember that.<br>[21:15] >> Yeah. Yeah. Yeah.<br>[21:17] >> I I don't think I ever tried Cold<br>[21:18] Fusion. That seemed a little bit too<br>[21:20] daunting.<br>[21:20] >> Buying a giant book.<br>[21:22] >> Yeah.<br>[21:22] >> And I was like that seems cool. There<br>[21:25] was something cool about it, but<br>[21:26] everything was just like more<br>[21:28] complicated.<br>[21:29] >> Yeah.<br>[21:29] >> Yeah. Yeah. And I and you know I think<br>[21:32] about like you know I work at Pantheon<br>[21:33] and obviously we do um Drupal and<br>[21:36] WordPress and even now like I talk to<br>[21:39] Drupal developers and I've gone to a<br>[21:40] couple Drupal events and it's like okay<br>[21:42] like I get I get what Drupal is good at.<br>[21:46] It's also not the thing that I would use<br>[21:50] because it is there's there's a learning<br>[21:53] curve. There's a very steep learning<br>[21:55] curve or or there's like there's a whole<br>[21:58] category of professionals that exist in<br>[22:01] the Drupal ecosystem that WordPress has<br>[22:03] never had because it's never needed it<br>[22:05] because it's just the people that like<br>[22:07] manage the the the website. like not the<br>[22:11] people that put the content into the<br>[22:12] website, but the people that manage like<br>[22:14] the configuration and like structure of<br>[22:17] the website. It's like that's the<br>[22:19] category of people like we talk about in<br>[22:21] WordPress like there's sort of site<br>[22:22] builders and like maybe they're not<br>[22:24] writing the content or whatever, but<br>[22:25] there's sort of but you don't really<br>[22:26] need that. Like it's it's generally<br>[22:29] speaking uh accessible enough for for<br>[22:33] anyone. So, like I totally like relate<br>[22:34] to what you're saying, obviously, like<br>[22:36] we're both here, but yeah, I'm always<br>[22:38] I'm always interested in in the the<br>[22:42] decision-making process that that leads<br>[22:44] people to like kind of stick with a<br>[22:47] thing for for as long as I mean, you and<br>[22:49] I both have.<br>[22:51] >> I think it's like WordPress made the<br>[22:53] decisions for me. What I mean is every<br>[22:56] time I tried to get something to happen<br>[22:58] in WordPress, it happened like I was<br>[23:00] able to make it happen more or less.<br>[23:03] Whereas in other platforms, I wasn't<br>[23:05] able to. So I kept choosing the one that<br>[23:09] enabled me to do what I wanted to do. I<br>[23:13] am what I call a fake developer. And<br>[23:16] what I mean is I<br>[23:19] like bar I sat at some point in writing<br>[23:22] code and I hated it. I hated it. I don't<br>[23:24] want to do that. I want to get things<br>[23:26] together. I love tech and I understand<br>[23:28] it. So that makes me really annoying<br>[23:31] because like I back on things from I've<br>[23:34] managed development teams and so I've<br>[23:37] learned about that. But um I'll never be<br>[23:40] the one sitting and writing code. So I<br>[23:42] want to work with a platform that allows<br>[23:44] me this like weird fake developery type<br>[23:46] person to achieve what I want to<br>[23:48] achieve. And and that and it was always<br>[23:51] WordPress.<br>[23:53] Yeah, the thing that that kept me around<br>[23:55] was<br>[23:57] uh especially at the beginning was<br>[23:59] anytime I had a question about how to do<br>[24:00] X, there was always an answer.<br>[24:03] >> Whether it was whether it was in the<br>[24:05] codeex or a blog post or something like<br>[24:07] I there was always an answer somewhere.<br>[24:09] Um whereas whenever I used something<br>[24:11] else, maybe there is an answer or maybe<br>[24:14] there wasn't or maybe there was a forum<br>[24:16] but maybe that forum hasn't been posted<br>[24:18] to in three months. Like<br>[24:19] >> right<br>[24:20] >> like it was never it was never<br>[24:21] consistent but WordPress was always<br>[24:23] consistent for sure.<br>[24:24] >> Totally.<br>[24:25] >> And now you're the head of WordPress.<br>[24:26] What does that mean?<br>[24:29] >> So a nice segue, right?<br>[24:32] >> Speaking of which,<br>[24:35] it is the nice segue. So what does it<br>[24:37] mean? Well, I I was at like elementary<br>[24:42] for like six months and then uh the<br>[24:44] founders said, "Would you like to take<br>[24:46] on this position? We don't know what to<br>[24:48] call it." And we don't exactly have a<br>[24:52] job description. We know we need someone<br>[24:55] like you doing something like this.<br>[24:58] >> Sure.<br>[24:59] >> And what do you think? So<br>[25:03] I I was<br>[25:04] >> How was the How was the position<br>[25:06] pitched? like what was the what were the<br>[25:07] things that that they knew that they<br>[25:10] needed? So I could see after joining<br>[25:14] actually I could even see before joining<br>[25:16] from the outside um<br>[25:19] Elementor the their flagship product the<br>[25:22] page builder or editor whatever you want<br>[25:24] to call it uh is obviously very popular<br>[25:27] right it's most popular plugin it powers<br>[25:30] over 20 million sites um and from the<br>[25:33] beginning it caught on and uh grew quite<br>[25:35] quickly<br>[25:37] but as the company grew and hired talent<br>[25:41] ent and the people at the company are<br>[25:43] very talented. They didn't come from<br>[25:45] within WordPress.<br>[25:47] So<br>[25:48] you had the founders who were WordPressy<br>[25:51] people but you know they're founders so<br>[25:53] they can only be so involved in<br>[25:57] community related you know ecosystem<br>[26:00] stuff.<br>[26:02] Um and and the the rest of the team,<br>[26:06] they came from other tech companies, you<br>[26:08] know, um and not necessarily even from<br>[26:10] open source. And when you're working in<br>[26:13] open source, there's definitely like a<br>[26:17] culture to that, you know. Um and<br>[26:22] there were a few things that were<br>[26:24] lacking. It's not just um community.<br>[26:26] It's like um how do we communicate with<br>[26:29] all the levels of the ecosystem and h<br>[26:33] how are our relationships with all of<br>[26:36] the companies essentially that are<br>[26:38] contributing to WordPress by creating<br>[26:41] other products where we have shared<br>[26:42] users?<br>[26:44] um how do we make sure always that the<br>[26:48] way that we're deploying our products to<br>[26:50] the repo is 1,000% aligned with the<br>[26:54] guidelines.<br>[26:56] There were some missteps before I took<br>[26:57] on this position and it wasn't out of um<br>[27:01] it wasn't because they were trying they<br>[27:03] trying to not meet the guidelines. It<br>[27:05] was because there wasn't really someone<br>[27:07] who could fully be on top of it and or<br>[27:11] something that I do on an ongoing basis.<br>[27:13] Check with the plug-in team whenever we<br>[27:18] want to implement something in the<br>[27:19] plug-in that we think should be reviewed<br>[27:22] and to make sure that it really aligns<br>[27:23] with the guidelines. And only if they<br>[27:24] say yes, that's okay, do we go ahead<br>[27:26] with it. We don't want to ever be doing<br>[27:30] something that's not okay. So, we're<br>[27:31] very we're super careful. And that's<br>[27:34] something also<br>[27:37] um setting up our five for the future<br>[27:38] program. Um that was an interesting<br>[27:41] process for me. Uh I had to you know<br>[27:44] research all of that and figure out<br>[27:47] where we can even do that. We had to<br>[27:48] first we had to figure out internally<br>[27:49] are we going to um align or just uh<br>[27:54] contribute internal resources like<br>[27:56] people time but we we couldn't um<br>[27:59] everyone was too tight. So the so then<br>[28:03] the decision was to sponsor<br>[28:04] contributors. Okay, but how do we do<br>[28:05] that? How do we sponsor contributors in<br>[28:07] a meaningful way? Which teams need<br>[28:10] contribution? Um so I had like I spoke<br>[28:12] to a ton of people in the community um<br>[28:15] you know the from the contribution<br>[28:18] related teams on WordPress.org to<br>[28:20] contributors themselves to figure out<br>[28:22] how we could start. I think the first<br>[28:25] sponsor contributor was on the<br>[28:26] performance team because at that time<br>[28:29] that was a big pain point. Oh, and um<br>[28:31] Google was working on it and they they<br>[28:33] asked us if we want to like work on it<br>[28:35] with them and like make you know help<br>[28:37] with that team. So that's where we<br>[28:38] started. It seemed like a good good<br>[28:41] place to fill in the blanks. Um and then<br>[28:43] contri grew it from there. At this point<br>[28:46] we have contributors to performance,<br>[28:49] plug-in review, theme review, hosting,<br>[28:53] AI, and I I think something else but I<br>[28:56] can't remember. Um so and you know I<br>[29:00] manage that and stay in touch with them<br>[29:02] on ongoing basis get reports on what's<br>[29:03] being done to try to make sure that our<br>[29:06] contribution is valuable. So um so that<br>[29:09] was another thing and it's generally<br>[29:14] anything related to element within<br>[29:16] WordPress. It's a very broad uh position<br>[29:19] and it involves also partnership type of<br>[29:20] rel like activity whether it's like with<br>[29:23] a dollar sign attached or not. Um, I've<br>[29:27] kind of become the face of Elementor<br>[29:30] within the community. So, that's helpful<br>[29:33] for people who are trying to reach out<br>[29:34] to Elementor and having a hard time.<br>[29:36] That was very much the case before I<br>[29:38] took on the position. Like, if you want<br>[29:39] to talk to someone Elementor, like good<br>[29:41] luck. It wasn't again that they didn't<br>[29:42] want to be talked to. It was that there<br>[29:46] wasn't someone to do that. So, people<br>[29:48] reach out to me directly. They find me<br>[29:49] wherever or they know me like and it's<br>[29:51] different kinds of questions. they want<br>[29:54] to, you know, increase compatibility<br>[29:56] with Elementor and they like need some<br>[29:58] dev input or um they created something<br>[30:02] for Elementor and they want to show it<br>[30:03] to us and like whatever or like there's<br>[30:05] it's hosting companies they're like this<br>[30:07] they're encountering some issue in the<br>[30:09] past that that kind of communication was<br>[30:12] full of friction. Now we have a lot of<br>[30:14] shared Slack channels with a lot of<br>[30:16] partner companies in the space and it's<br>[30:18] great. We can really like make sure that<br>[30:21] all of our shared users have good<br>[30:22] experiences.<br>[30:24] Um yeah, I don't know. It's like it's so<br>[30:26] many things. I at some point I started<br>[30:28] documenting what I do because I was like<br>[30:29] what am I doing?<br>[30:32] But um but it's it's always interesting<br>[30:35] because things are always changing um<br>[30:38] and I'm always learning. So yeah, it's<br>[30:40] it's an interesting position.<br>[30:43] I know that for me as as a developer<br>[30:46] advocate like I went from you know being<br>[30:49] on an engineering team where like what I<br>[30:51] do in a day or in a week is very<br>[30:55] specific. It's like we have these sprint<br>[30:57] goals, we have these specific tickets,<br>[30:58] we are have a cadence like this stuff<br>[31:02] needs to get done by this date and and<br>[31:04] that's just what you're working on. And<br>[31:07] in developer relations that's<br>[31:10] kind of a lot more wibbly wobbly timy<br>[31:13] wimy like you kind of have to like it<br>[31:15] really demands that you are self<br>[31:18] motivated because otherwise you're just<br>[31:20] going to be twiddling your thumbs and<br>[31:21] like who knows what what totally like<br>[31:23] how are you going to prioritize this<br>[31:24] thing over that thing or whatever or<br>[31:26] you'll just get pulled in a million<br>[31:28] different directions and never be able<br>[31:29] to focus on anything and context<br>[31:31] switching is already like you know huge<br>[31:33] like I imagine that is pretty similar<br>[31:36] for you as well. So, how do you sort of<br>[31:38] like yeah prioritize what it is that<br>[31:42] you're thinking about in any given day?<br>[31:44] >> Oh my gosh, totally. So, first of all,<br>[31:46] you have to be a self-starter. At least<br>[31:47] I have to be. Also,<br>[31:50] >> it's sort of like in many ways it's sort<br>[31:51] of entrepreneurial, isn't it?<br>[31:53] >> Oh, totally. Which is amazing. And I um<br>[31:56] I've said that internally actually that<br>[31:58] uh I I actually didn't know how I was<br>[32:00] going to last at elementary. Not because<br>[32:03] of them, but because I had never been an<br>[32:06] employee before.<br>[32:09] And I was afraid of the like that what<br>[32:13] would happen is why I had never been an<br>[32:15] employee, which is that people would<br>[32:16] start telling me what to do. Not that I<br>[32:18] don't I I love getting feedback and<br>[32:20] input and direction. I love it. But when<br>[32:22] someone's like, "You must do this, you<br>[32:24] must do that." And like, I don't know,<br>[32:25] that kind of thing, which is what I<br>[32:27] figured it's like to be an employee, I<br>[32:28] was just like, "That's not for me." But<br>[32:30] this position is very entrepreneurial<br>[32:32] and a lot of what I do feels like what I<br>[32:34] did when I was the CEO of Stratic.<br>[32:37] >> Um, because a lot of work of leading a<br>[32:41] company, and just I'm just to put that<br>[32:43] just a disclaimer, I'm not saying that<br>[32:45] I'm leading Elementor at all. I am not.<br>[32:48] But when I was leading a company, I a<br>[32:52] lot of it was very relationship driven<br>[32:54] and also very a lot of like staying<br>[32:57] current on developments, competitive,<br>[32:59] you know, um developments,<br>[33:03] tech, all that kind of stuff. It was<br>[33:05] like a combination of both. And I do a<br>[33:06] lot of that now. Like I actually create<br>[33:08] an internal weekly newsletter about AI<br>[33:11] and WordPress now for example<br>[33:13] >> to keep everyone up to date on where<br>[33:15] it's going, what other companies are<br>[33:18] developing. Um to bring that all<br>[33:19] together. I think that the more<br>[33:21] information anyone has, the better the<br>[33:23] decisions they can make. And that's how<br>[33:25] I was a CEO and that's kind of what I'm<br>[33:27] doing now. So, but like I so a lot of<br>[33:30] what I do is is selfarter type stuff<br>[33:32] where I just see a need and I I work to<br>[33:36] fill that gap. In the beginning, there<br>[33:38] was a lot of stuff that I was trying to<br>[33:40] fix like um you know our for the future<br>[33:45] program even how we sponsored word camps<br>[33:47] I it it wasn't my vibe. Let's just say<br>[33:51] that it like I didn't like it. I wanted<br>[33:53] us to be more involved. like I was the<br>[33:56] first person to speak on behalf of<br>[33:58] Elementor. Like they had never had<br>[34:00] speakers,<br>[34:01] >> that kind of thing. But then I created a<br>[34:02] program encouraging other people to<br>[34:03] apply to speak and now I'm not the only<br>[34:05] speaker which is amazing. Um so there's<br>[34:08] like a lot of things that I Oh, also I<br>[34:09] wanted us to sponsor other word camps<br>[34:12] around the world even if we're not going<br>[34:13] there just to support them. So set up<br>[34:15] like a process and like a way to do<br>[34:17] that. Um I'm very fortunate that the<br>[34:20] company and the leadership basically<br>[34:22] like just support and believe in me and<br>[34:25] trust me. So um the message to me more<br>[34:28] or less is you do you<br>[34:31] now go forth. So and I report to the CEO<br>[34:36] um and you know I love when I get<br>[34:39] direction and feedback and ideas from<br>[34:40] him but mostly I'm just doing what I<br>[34:43] think I should do. So there's like stuff<br>[34:45] that I maintain<br>[34:47] and then there's stuff that comes up<br>[34:49] that needs attention. So obviously and<br>[34:51] especially if it's like um critical that<br>[34:54] will get priority. Um and then there's<br>[34:56] just new challenges or relationships or<br>[34:59] things or whatever that uh come come my<br>[35:01] way that uh that I pick up. Attending<br>[35:04] events on behalf of Elementor that also<br>[35:06] is something that wasn't really<br>[35:08] happening before. I think it's important<br>[35:09] for us to have like an actual person at<br>[35:12] these events. Elementary is such a<br>[35:13] significant player that you know for<br>[35:16] example at Cloudfest which I'm not at um<br>[35:18] because I couldn't get there in the end<br>[35:19] but we should be at Cloudfest. We're a<br>[35:22] leading web company. How can we not be<br>[35:24] there? So I started going on behalf of<br>[35:26] Elementor.<br>[35:28] Um yeah it's just it's it's a great<br>[35:32] position. I'm very fortunate that I have<br>[35:33] the the backing and belief of of the<br>[35:36] company's leadership and um that allows<br>[35:38] me to bring to to fruition my my<br>[35:42] entrepreneurial spirit which I I think<br>[35:45] would be hard if I couldn't.<br>[35:47] >> You mentioned five for the future and<br>[35:49] and sponsoring word camps and things and<br>[35:52] um wearing my uh WP community collective<br>[35:56] president hat for a minute. um like<br>[35:59] obviously you know sponsored<br>[36:02] contribution or or contribution<br>[36:05] with with compensation uh and<br>[36:08] sponsorships in general like this is<br>[36:10] like it shouldn't be a controversial<br>[36:12] topic but yet like a lot of companies<br>[36:14] that are using WordPress aren't<br>[36:15] necessarily giving back to the ecosystem<br>[36:17] or giving back to the the the open-<br>[36:19] source uh project itself like talk<br>[36:22] through that conversation within<br>[36:24] Elementor of like building up this<br>[36:26] program which like does does like how<br>[36:31] how does how do you see contribution in<br>[36:33] in how it works at Elementor and how<br>[36:35] does like leadership or your your you<br>[36:37] know CEO that you report to like how<br>[36:39] does how does that sort of internal like<br>[36:43] financial math uh align with like the<br>[36:45] ideological goal of like yeah we need to<br>[36:48] actually contribute back to this thing<br>[36:49] that we're like essentially profiting<br>[36:51] off of.<br>[36:55] So they knew that they wanted to set up<br>[36:58] a fight for the future program. Like<br>[36:59] when they it wasn't like I had even<br>[37:01] brought it up or someone I don't know<br>[37:03] what the internal conversation was. I<br>[37:04] had been there not that long. I was<br>[37:06] still trying to figure out who I am and<br>[37:07] what I am and all that kind of stuff. Um<br>[37:09] I don't remember that we had actually<br>[37:11] discussed for the future. I think it was<br>[37:13] probably something that I felt like they<br>[37:14] should set up but I also didn't think it<br>[37:15] was necessarily my place to bring it up.<br>[37:17] Like I didn't know how much I could you<br>[37:19] know flag things yet. Uh, turns out that<br>[37:23] Elementor is very much a company where<br>[37:25] you can express your opinion, but I had<br>[37:27] to learn that. Yeah, it's great. Um,<br>[37:30] so when so that was actually like the<br>[37:32] first thing that they tked me with like<br>[37:33] get get us set up please with a five for<br>[37:36] the future program. They didn't say how<br>[37:38] except for like I mentioned when they<br>[37:39] said we're going to sponsor like<br>[37:40] financially rather than uh internally.<br>[37:44] >> Go forth and do it. Um<br>[37:47] why? Because it's the right thing to do.<br>[37:50] That's it. So<br>[37:52] when you have an open and also and we're<br>[37:56] I think it's um very much to the credit<br>[37:58] of uh Elementary's leadership that<br>[38:00] that's their perspective. They knew they<br>[38:02] needed to do this thing. They knew it<br>[38:03] was the right thing to do. They needed<br>[38:05] someone to like just set it up properly.<br>[38:08] Um who uh is a WordPressy person. That's<br>[38:11] what our CEO often says about me. Like<br>[38:13] I'm WordPressy. And it's I think you<br>[38:16] understand what that means. I think<br>[38:17] other may think that sounds weird but I<br>[38:20] like I I live and breathe the ecosystem<br>[38:22] and I understand it nuances and you need<br>[38:25] someone like that I think um especially<br>[38:27] in a large organization like Elementor<br>[38:29] that's very it's it's all about uh<br>[38:32] WordPress. So um they knew it was the<br>[38:35] right thing to do. So when you have an<br>[38:37] open source product, I think a company<br>[38:41] ends up making uh some decisions based<br>[38:44] on<br>[38:46] what is the right thing to do for that<br>[38:49] community at some point. Like it's not<br>[38:52] feasible for large for smaller<br>[38:54] organizations. It really it often is not<br>[38:56] no matter what anyone says. Like I know<br>[38:59] what it's like when I was running my<br>[39:01] agency. we were just running from like<br>[39:03] after projects, you know, you're just<br>[39:04] like finish one, you're like where's the<br>[39:06] next project going to come from? There's<br>[39:07] not much breathing room at all,<br>[39:09] >> you know. Um, so I think people need to<br>[39:13] like be realistic about their<br>[39:14] expectations about who's contributing.<br>[39:15] Like yes, that agency is profiting off<br>[39:18] of WordPress. But<br>[39:20] but what does that mean? It means that<br>[39:22] maybe they can pay their uh other<br>[39:26] contractors or employees and maybe give<br>[39:27] themselves a living wage. You know what<br>[39:29] I mean? Like often that's the case. So<br>[39:31] have a little sympathy. Um but once you<br>[39:36] have like a like a thriving word open<br>[39:38] source project um product then it<br>[39:40] becomes necessary. So there's like the<br>[39:43] it's the right thing to do. But then I<br>[39:46] think if we're going to look at it from<br>[39:48] like a dry<br>[39:50] financial perspective,<br>[39:52] companies invest a lot of uh money in<br>[39:56] things that don't have a direct ROI.<br>[40:00] For example,<br>[40:02] brand<br>[40:04] brand is critical. I have learned the<br>[40:06] importance of brand since joining<br>[40:07] Elementor. I was very cynical about it.<br>[40:12] And now I see how much it matters how a<br>[40:15] brand as you know you have to have a<br>[40:18] real product standing behind it that<br>[40:19] gives people value. But when you that<br>[40:21] and you have a brand wrapping it,<br>[40:22] wrapping it up, it gives people a<br>[40:25] certain sentiment or they have a certain<br>[40:26] sentiment towards you and maintaining<br>[40:28] that um growing it and investing it is<br>[40:32] super important. So a company like<br>[40:34] Elementor invests a lot in brands also<br>[40:36] and I think that you can say that<br>[40:40] investing in contributing back to open<br>[40:43] source is a brand investment<br>[40:48] to the ecosystem. It's like our brand is<br>[40:51] that we are collaborative cooperative<br>[40:54] um contributing we are doing the right<br>[40:57] thing and we are good citizens of the<br>[40:58] ecosystem.<br>[41:00] So that's I think the<br>[41:03] business side argument that can be made<br>[41:07] for it.<br>[41:08] >> Yeah. I mean obviously uh I'm involved<br>[41:10] in a lot of these conversations as well.<br>[41:11] all developer relations is very much uh<br>[41:14] in the the sort of brand and less direct<br>[41:19] ROI sort of side of things because like<br>[41:23] I I I've said this before like<br>[41:25] internally like the the stuff that I<br>[41:27] that Devril produces the content and and<br>[41:30] the the outputs that we produce very<br>[41:33] often is maybe on a very long tail like<br>[41:37] I'm not going to write a blog post<br>[41:38] that's going to lead to uh 500<br>[41:41] incoming leads, right? I'm going to<br>[41:43] write a blog post that someone's going<br>[41:44] to read in two weeks and then in six<br>[41:47] months they're going to remember that<br>[41:48] blog post that I wrote something smart<br>[41:50] about Pantheon doing something cool and<br>[41:52] they're going to be like, "Oh, well,<br>[41:53] we're looking for something for this<br>[41:56] project that we're that we're coming to<br>[41:57] and maybe they'll be part of the<br>[41:59] conversation, right?" Like yeah I I<br>[42:02] always get like whenever when ROI comes<br>[42:04] into the conversation about like<br>[42:05] sponsorships or about like open source<br>[42:08] uh good Samaritanism<br>[42:10] good Samaritanism<br>[42:12] um or or like whatever uh like yeah it's<br>[42:15] it's already like I I just like I just<br>[42:17] smirk like whenever I hear ROI in those<br>[42:19] conversations because like you're not<br>[42:21] going to get ROI from any of that stuff<br>[42:23] but what you're going to get is<br>[42:24] something intangible. Um, and uh, John<br>[42:27] Hawkins was on uh, a few episodes ago.<br>[42:30] Um, and he he said that so John Hawkins<br>[42:34] uh, used to lead a or co-lead a an<br>[42:36] agency and they spent I think two years<br>[42:39] just going to every word camp that they<br>[42:41] possibly could. Um, and it was wild. It<br>[42:45] was kind of insane. They uh, but what he<br>[42:49] said that he learned come chemist out of<br>[42:51] that is not ROI, it's return on<br>[42:53] connection. Um because it's those<br>[42:56] connections that you get from those<br>[42:58] events, from meeting people and having<br>[43:00] the conversation in person uh leads to<br>[43:03] other opportunities. Maybe not today,<br>[43:05] but like he was saying that like he they<br>[43:07] got leads and he's gotten leads that are<br>[43:10] like somebody he's never met before that<br>[43:13] someone he did meet talked to their<br>[43:15] friend and said, "Oh, you should talk to<br>[43:17] this person because they're doing<br>[43:18] something that's really similar to what<br>[43:19] you're looking for." And like that<br>[43:20] doesn't exist if you're not like having<br>[43:22] the conversation in the first place.<br>[43:24] >> Oh, totally. There's no question that<br>[43:26] when I started going to word camps<br>[43:29] around the world and speaking that it<br>[43:32] had a huge impact on the future of my<br>[43:35] career. At the time I would speak, I<br>[43:38] don't know how many people would be in<br>[43:39] the hall and I would get zero feedback.<br>[43:41] You know, like often it's just like<br>[43:42] thanks, bye. But then six months later<br>[43:46] someone would get in touch for a web<br>[43:48] project or you know all and I would<br>[43:51] always say just took one person in the<br>[43:53] audience that that talk meant something<br>[43:55] to them that it was worth it but it's<br>[43:57] stuff that that kind of activity it's<br>[44:00] timeconuming it's expensive it's you<br>[44:02] know it's very easy to say never mind we<br>[44:05] live in a digital age I'm going to sit<br>[44:06] here behind my screen and that will be<br>[44:08] enough but you can't compare to the<br>[44:11] power of a real connection<br>[44:13] And it's the kind of thing that builds<br>[44:15] up over time and you don't you can't<br>[44:18] predict how like what is going to mean<br>[44:20] and so you can't also be doing it<br>[44:22] because you think at some point you're<br>[44:24] going to get something out of it. I<br>[44:26] started going um because I wanted to<br>[44:29] connect more with the WordPress<br>[44:30] community and I could see how impactful<br>[44:35] it was for me to speak. I didn't know<br>[44:36] what it was going to do, but I knew that<br>[44:38] it was like it mattered and it meant<br>[44:40] something for for my work. So, but how<br>[44:45] it play out, I had no idea.<br>[44:48] But it turned out to play out like in<br>[44:50] many ways um very well. But I just loved<br>[44:53] meeting the people. So like, you know,<br>[44:55] you have to be in it because you love<br>[44:57] the people. And if good stuff comes your<br>[44:59] way, great. And by the way, it goes the<br>[45:01] other way also. I've been very fortunate<br>[45:04] to help many people along the way who<br>[45:07] know me. Like it goes both ways. Like I<br>[45:09] sometimes I think, "Wow, so good that<br>[45:10] person knows me." Yeah.<br>[45:12] >> You know, because I can help them out<br>[45:14] with something. And um yeah, it's<br>[45:17] definitely it's been a journey, but it's<br>[45:19] it's worth it.<br>[45:21] I want to I want to talk a little bit.<br>[45:22] Uh this probably be the the last bit,<br>[45:25] but I think that it's you you mentioned<br>[45:27] a number and you mentioned it too like<br>[45:30] uh when we were doing the live stream uh<br>[45:32] for for Angie. Um<br>[45:35] >> uh like the number of of Elementor<br>[45:37] installs is some ridiculously high<br>[45:40] number that I can't even fathom a<br>[45:41] product uh being used that much.<br>[45:45] um like what<br>[45:48] was it always like was was it like that<br>[45:50] when you joined first of all and then<br>[45:53] what do you credit Elementor's<br>[45:56] I mean objective success to<br>[46:01] >> so Elementor has been growing at a fast<br>[46:04] pace basically since it was launched I<br>[46:05] can't remember the exact numbers but<br>[46:07] like within I don't know 6 months or a<br>[46:10] year of them launching uh Elementor they<br>[46:13] had reached like million installs. It<br>[46:15] was it was like a very short amount of<br>[46:17] time and the growth hockey stick was<br>[46:19] like crazy.<br>[46:20] >> And then since then it's been growing.<br>[46:22] Um when I joined it wasn't yet the most<br>[46:26] popular plug-in in the repo. It was like<br>[46:29] number three and it was like and we<br>[46:31] would pay attention and then it's at one<br>[46:33] point we're like oh my gosh it bypassed<br>[46:35] Yoast. Yoast was like number two and we<br>[46:37] went to number two and then one morning<br>[46:39] we woke up and we're like we're number<br>[46:41] one. It was crazy.<br>[46:44] Um, so<br>[46:46] why is it growing?<br>[46:49] First of all, I think from the be like<br>[46:50] in the start it was just really the<br>[46:53] right product at the right time. It was<br>[46:54] that combination which is like winning<br>[46:56] the lottery. And I'm not saying it was<br>[46:58] luck because they built a product that<br>[47:00] people really wanted, but like they<br>[47:01] built that product that people really<br>[47:03] wanted at the exact right time. M<br>[47:06] >> um there were some other products<br>[47:08] already out there but they there the the<br>[47:10] element approach gave people more<br>[47:13] capabilities and then people just loved<br>[47:15] it and they were just talking about it<br>[47:16] and then they were sharing it and also I<br>[47:18] think at that time at least I don't know<br>[47:20] how long but it was the only the free<br>[47:23] version they it took them a while until<br>[47:25] they started offering the the pro<br>[47:27] version.<br>[47:28] Um, but I think that that like going all<br>[47:32] in on open source like that was also uh<br>[47:36] a key to their success.<br>[47:38] Um,<br>[47:40] they've been<br>[47:42] uh good at listening to customer<br>[47:44] feedback. There's a lot of complaints,<br>[47:45] you know, that why don't you do this,<br>[47:47] why don't you do that, but like if you<br>[47:48] think about the scale, so the number is<br>[47:50] now like 21 million um active installs,<br>[47:54] which is crazy.<br>[47:55] >> So just imagine how many opinions there<br>[47:56] are there.<br>[47:57] >> Sure. 21 million<br>[47:59] >> basically. So, um, so obviously<br>[48:02] elementary can't do everything. There's<br>[48:04] a lot of one of the things that I I<br>[48:06] couldn't believe when I joined because<br>[48:08] they they're so big that like how much<br>[48:12] they cared about like one person saying<br>[48:14] something negative.<br>[48:15] >> I'm like, you're so big. You're growing<br>[48:17] at like I don't know how many sites a<br>[48:19] day and you care that Joe over there.<br>[48:23] But they cared and they were always<br>[48:25] listening. Um, so I think that probably<br>[48:28] plays a role as well. And then you know<br>[48:30] just really talented people working<br>[48:33] together. I have also learned so at<br>[48:36] elementary<br>[48:38] HR is super important in terms of hiring<br>[48:41] the right talents. They they they'll<br>[48:43] spend as long as it takes to fill a<br>[48:45] position until they feel like more than<br>[48:47] 100% that the the fit is right. Um and<br>[48:51] there you know there's a lot of<br>[48:52] appreciation for that and the the people<br>[48:54] who work at element are really really<br>[48:56] very brilliant and it's really fun<br>[48:58] working with them everyone you know has<br>[49:00] their like area of expertise and they<br>[49:02] really are an expert in that area. So<br>[49:05] whatever it is even like what I'm doing<br>[49:07] whenever I'm doing anything so on the<br>[49:09] one hand I'm kind of like a lone island.<br>[49:11] I don't have a team. I report to the CEO<br>[49:13] he's super busy. I'm like doing my own<br>[49:15] thing. So but I work horizontally. So<br>[49:18] like uh you know if we're sponsoring a<br>[49:20] word camp I have to pull in finance,<br>[49:22] legal design. If we're like going to<br>[49:25] have a booth, right? Um and<br>[49:30] everyone's just so smart and like brings<br>[49:32] such value to the project that I the<br>[49:34] output will be really good. So, so I<br>[49:37] think that as well and of course our the<br>[49:39] co-founders Ariel and Yoni, their vision<br>[49:42] is very focused um and strategic and<br>[49:44] they're always thinking and rethinking<br>[49:48] and they're also if they hear this<br>[49:50] they're probably not going to be like<br>[49:52] how they're um they're like they have<br>[49:56] humility meaning they don't think they<br>[49:58] know everything as all we're all like<br>[50:00] everyone is always discussing things and<br>[50:01] yes they'll make a decision in the end<br>[50:02] but um they don't think they know<br>[50:04] everything And um yeah, I don't know.<br>[50:07] It's like I guess it's a combination of<br>[50:08] factors, but uh yeah, it's wild the<br>[50:12] reach that the company has.<br>[50:13] >> Yeah.<br>[50:14] >> Yeah.<br>[50:15] >> Yeah.<br>[50:16] >> Well, thank you very much uh Miriam for<br>[50:18] being on the show. Uh I'm hopefully<br>[50:21] we'll get to meet someplace uh in the<br>[50:24] next year. Uh I'm sure we tend to like<br>[50:27] rotate in similar circles uh as it were.<br>[50:30] Um, uh, where can people find you on the<br>[50:34] internet?<br>[50:35] >> So, actually, I just built myself a<br>[50:37] website.<br>[50:37] >> Oh, yeah.<br>[50:38] >> Yeah. Miam Schwab.me. Someone took<br>[50:40] miriam.com.<br>[50:43] They're not doing anything with it. So,<br>[50:44] I took miriam.me. Um, it's a WordPress<br>[50:47] site that I built with AI. I was super<br>[50:48] excited about it. So, you can I have a<br>[50:50] contact form there and I have links, but<br>[50:52] you can obviously find me on LinkedIn,<br>[50:54] uh, TwitterX,<br>[50:56] um, all the usual places. I'm there. Oh,<br>[50:59] make WordPress slack, post status Slack,<br>[51:03] >> all the slacks. Yeah,<br>[51:04] >> all the slacks.<br>[51:06] >> Uh, well, yeah, thanks again. Uh, thanks<br>[51:08] for for being on the show. Thank you,<br>[51:09] everyone who might be watching or<br>[51:11] listening to this in the future, and<br>[51:12] we'll see you on the internet.<br>[51:14] >> Bye.
<!-- deep-read:sections end -->
## Highlights
- Some career successes attributed to community involvement may have resulted from other factors like market timing or individual talent
- Note: ๐ Fallacy: Post Hoc #fallacy/post-hoc