Making and Questioning Assumptions: Falsehoods WordPress Developers Believe  [[3. Resources/Readwise/Full Document Contents/Articles/Making and Questioning Assumptions Falsehoods WordPress Developers Believe|Full Document Contents]] ## Document Notes ## 📝 Summarize: The article emphasizes the importance of questioning assumptions when building software and navigating the web, particularly in the context of WordPress development. It cites Akin's 33rd law of spacecraft design, which states that a good plan executed now is better than waiting for perfection. The author highlights the prevalence of "Falsehoods Programmers Believe" on the internet, discussing several misconceptions about WordPress roles, taxonomies, plugin reliability, and WordPress Cron. The overall message encourages developers to be mindful of assumptions, leverage the power of WordPress's capabilities system, and assess plugins based on their code quality and responsiveness to feedback. The article ultimately celebrates the growth and versatility of WordPress, dispelling myths about its declining popularity and applicability to big sites. ## 📝 Bullet Points: ### Assumptions and Falsehoods: - Building software requires making assumptions due to imperfect information. - Waiting for perfection is impractical; executing a good plan now is better. - Questioning assumptions is essential to avoid falsehoods. ### Falsehoods WordPress Developers Believe: #### WordPress Roles: - Roles are static across sites. - Roles are static during each request. - A user can only have one role. - Users with the same role have identical capabilities. - Capabilities persist throughout a request. #### Taxonomies: - Taxonomies are only applicable to posts. - Taxonomies are limited to the posts table. - Taxonomies cannot be shared across different object types. - Terms may be split after updating past WordPress 4.3. #### Plugin Reliability: - Popular plugins are bug-free. - Plugins with few users are untrustworthy. - Bigger plugins are always better. - Update plugins immediately after release. #### WordPress Cron: - WordPress Cron always fires on time. - WordPress Cron slows down sites. - WordPress Cron is not reliable for timing. ### Advancements and Popularity: - WordPress remains strong, with numerous large and small sites being launched. - WordPress's capabilities system is powerful and flexible. ## 📝 Paraphrase: 1. When developing software, making and questioning assumptions is crucial due to the lack of perfect information. Instead of waiting for perfection, it is better to execute a solid plan promptly. This principle, often known as Akin's 33rd law of spacecraft design, applies at any stage of the development process, where the required number of iterations is always one more than the current number. 2. On the internet, there are widespread misconceptions, known as "Falsehoods Programmers Believe," particularly within the WordPress development community. For instance, developers may assume that WordPress roles are static across sites, that a user can only have one role, or that taxonomies are limited to posts. These assumptions can lead to unintended consequences and errors in the development process. ## 📝 Conclusion: The article stresses the significance of challenging assumptions when building software and exploring the WordPress ecosystem. It addresses various misconceptions, or "Falsehoods," prevalent among developers and offers insights into WordPress roles, taxonomies, plugin reliability, and WordPress Cron. By encouraging a critical mindset and leveraging WordPress's capabilities system, developers can navigate the complexities of web development more effectively. The article ultimately celebrates the thriving and adaptable nature of WordPress, debunking myths about its declining popularity and its suitability for big sites. ## ❓ Questions: 1. Why is it essential to question assumptions when developing software or working on WordPress projects? 2. How can developers avoid falling into the trap of "Falsehoods Programmers Believe" while working with WordPress roles and taxonomies? 3. What are the implications of relying solely on popular plugins for WordPress websites? How can developers make more informed choices? 4. Explain the potential issues with WordPress Cron and how developers can ensure timely event execution on sites with low traffic. 5. How has WordPress evolved over time, and what makes it an excellent choice for both small and large websites? ## 🏷️ Auto-tagging: software development, assumptions, Akin's 33rd law, Falsehoods Programmers Believe, WordPress roles, WordPress taxonomies, plugin reliability, WordPress Cron, web development, WordPress popularity ## 📚 References: - Akin's 33rd law of spacecraft design: The article itself (no additional external sources were cited). ## 🔍 Future Research: 1. Conduct in-depth research on common "Falsehoods Programmers Believe" across various programming domains and explore strategies to avoid them. 2. Investigate the potential consequences of relying heavily on third-party plugins in the WordPress ecosystem and develop guidelines for plugin selection. 3. Examine the impact of WordPress Cron on websites with different traffic patterns and propose solutions for improving event timing accuracy. 4. Conduct a comprehensive study on the growth and adaptability of the WordPress platform over the years, comparing it to other content management systems. ## 🕵️‍♂️ Hypotheses: 1. If developers actively question assumptions during the software development process, they are more likely to identify and correct potential issues early in the development cycle. 2. Websites with a well-maintained collection of small, specialized plugins might outperform websites relying on a few large, feature-rich plugins. 3. Leveraging external monitoring services alongside WordPress Cron can significantly improve the reliability and accuracy of scheduled events on low-traffic sites. 4. The popularity of WordPress will continue to grow, with a diverse range of websites, from small blogs to large corporate platforms, adopting it as their preferred content management system. ## 📑 Methodology: 1. To investigate common "Falsehoods Programmers Believe" and their impact, conduct surveys and interviews with developers from different programming communities. 2. Analyze plugin performance and reliability by selecting a sample of popular and less-known plugins, examining their code, and reviewing user feedback. 3. Use website traffic data from various sources and employ a combination of WordPress Cron and external monitoring tools to measure event execution accuracy. 4. Conduct a longitudinal study analyzing the growth of WordPress adoption across various sectors and comparing it to other content management systems. ## 💡 Implications: Conducting research and dispelling "Falsehoods Programmers Believe" can enhance the software development process by fostering a culture of critical thinking and continuous improvement. Emphasizing code quality, responsiveness, and support in plugin selection can lead to more robust and reliable WordPress websites. Improving WordPress Cron's accuracy can enhance the user experience on sites with low traffic. Recognizing WordPress's ongoing popularity can boost confidence among developers and stakeholders, leading to broader adoption and further advancements in the platform. ## 🕵️‍♂️ Logical Validity: The main argument presented in the article is sound and coherent. The author emphasizes the significance of questioning assumptions and dispelling "Falsehoods Programmers Believe," providing examples related to WordPress development. The article supports its claims with practical insights and references to specific talks and events. There are no apparent logical fallacies in the article, and the ideas are logically connected. However, to further validate the claims, additional research and real-world case studies could be beneficial. 1. What are the main advantages of questioning assumptions when building software? 2. How does the "Akin's 33rd law of spacecraft design" apply to software development? 3. What are the most common "Falsehoods WordPress Developers Believe"? > [!note]+ Document Notes <!-- deep-read:sections start --> ## 📝 Summarize: The article emphasizes the importance of questioning assumptions when building software and navigating the web, particularly in the context of WordPress development. It cites Akin's 33rd law of spacecraft design, which states that a good plan executed now is better than waiting for perfection. The author highlights the prevalence of "Falsehoods Programmers Believe" on the internet, discussing several misconceptions about WordPress roles, taxonomies, plugin reliability, and WordPress Cron. The overall message encourages developers to be mindful of assumptions, leverage the power of WordPress's capabilities system, and assess plugins based on their code quality and responsiveness to feedback. The article ultimately celebrates the growth and versatility of WordPress, dispelling myths about its declining popularity and applicability to big sites. ## 📝 Bullet Points: ### Assumptions and Falsehoods: - Building software requires making assumptions due to imperfect information. - Waiting for perfection is impractical; executing a good plan now is better. - Questioning assumptions is essential to avoid falsehoods. ### Falsehoods WordPress Developers Believe: #### WordPress Roles: - Roles are static across sites. - Roles are static during each request. - A user can only have one role. - Users with the same role have identical capabilities. - Capabilities persist throughout a request. #### Taxonomies: - Taxonomies are only applicable to posts. - Taxonomies are limited to the posts table. - Taxonomies cannot be shared across different object types. - Terms may be split after updating past WordPress 4.3. #### Plugin Reliability: - Popular plugins are bug-free. - Plugins with few users are untrustworthy. - Bigger plugins are always better. - Update plugins immediately after release. #### WordPress Cron: - WordPress Cron always fires on time. - WordPress Cron slows down sites. - WordPress Cron is not reliable for timing. ### Advancements and Popularity: - WordPress remains strong, with numerous large and small sites being launched. - WordPress's capabilities system is powerful and flexible. ## 📝 Paraphrase: 1. When developing software, making and questioning assumptions is crucial due to the lack of perfect information. Instead of waiting for perfection, it is better to execute a solid plan promptly. This principle, often known as Akin's 33rd law of spacecraft design, applies at any stage of the development process, where the required number of iterations is always one more than the current number. 2. On the internet, there are widespread misconceptions, known as "Falsehoods Programmers Believe," particularly within the WordPress development community. For instance, developers may assume that WordPress roles are static across sites, that a user can only have one role, or that taxonomies are limited to posts. These assumptions can lead to unintended consequences and errors in the development process. ## 📝 Conclusion: The article stresses the significance of challenging assumptions when building software and exploring the WordPress ecosystem. It addresses various misconceptions, or "Falsehoods," prevalent among developers and offers insights into WordPress roles, taxonomies, plugin reliability, and WordPress Cron. By encouraging a critical mindset and leveraging WordPress's capabilities system, developers can navigate the complexities of web development more effectively. The article ultimately celebrates the thriving and adaptable nature of WordPress, debunking myths about its declining popularity and its suitability for big sites. ## ❓ Questions: 1. Why is it essential to question assumptions when developing software or working on WordPress projects? 2. How can developers avoid falling into the trap of "Falsehoods Programmers Believe" while working with WordPress roles and taxonomies? 3. What are the implications of relying solely on popular plugins for WordPress websites? How can developers make more informed choices? 4. Explain the potential issues with WordPress Cron and how developers can ensure timely event execution on sites with low traffic. 5. How has WordPress evolved over time, and what makes it an excellent choice for both small and large websites? ## 🏷️ Auto-tagging: software development, assumptions, Akin's 33rd law, Falsehoods Programmers Believe, WordPress roles, WordPress taxonomies, plugin reliability, WordPress Cron, web development, WordPress popularity ## 📚 References: - Akin's 33rd law of spacecraft design: The article itself (no additional external sources were cited). ## 🔍 Future Research: 1. Conduct in-depth research on common "Falsehoods Programmers Believe" across various programming domains and explore strategies to avoid them. 2. Investigate the potential consequences of relying heavily on third-party plugins in the WordPress ecosystem and develop guidelines for plugin selection. 3. Examine the impact of WordPress Cron on websites with different traffic patterns and propose solutions for improving event timing accuracy. 4. Conduct a comprehensive study on the growth and adaptability of the WordPress platform over the years, comparing it to other content management systems. ## 🕵️‍♂️ Hypotheses: 1. If developers actively question assumptions during the software development process, they are more likely to identify and correct potential issues early in the development cycle. 2. Websites with a well-maintained collection of small, specialized plugins might outperform websites relying on a few large, feature-rich plugins. 3. Leveraging external monitoring services alongside WordPress Cron can significantly improve the reliability and accuracy of scheduled events on low-traffic sites. 4. The popularity of WordPress will continue to grow, with a diverse range of websites, from small blogs to large corporate platforms, adopting it as their preferred content management system. ## 📑 Methodology: 1. To investigate common "Falsehoods Programmers Believe" and their impact, conduct surveys and interviews with developers from different programming communities. 2. Analyze plugin performance and reliability by selecting a sample of popular and less-known plugins, examining their code, and reviewing user feedback. 3. Use website traffic data from various sources and employ a combination of WordPress Cron and external monitoring tools to measure event execution accuracy. 4. Conduct a longitudinal study analyzing the growth of WordPress adoption across various sectors and comparing it to other content management systems. ## 💡 Implications: Conducting research and dispelling "Falsehoods Programmers Believe" can enhance the software development process by fostering a culture of critical thinking and continuous improvement. Emphasizing code quality, responsiveness, and support in plugin selection can lead to more robust and reliable WordPress websites. Improving WordPress Cron's accuracy can enhance the user experience on sites with low traffic. Recognizing WordPress's ongoing popularity can boost confidence among developers and stakeholders, leading to broader adoption and further advancements in the platform. ## 🕵️‍♂️ Logical Validity: The main argument presented in the article is sound and coherent. The author emphasizes the significance of questioning assumptions and dispelling "Falsehoods Programmers Believe," providing examples related to WordPress development. The article supports its claims with practical insights and references to specific talks and events. There are no apparent logical fallacies in the article, and the ideas are logically connected. However, to further validate the claims, additional research and real-world case studies could be beneficial. 1. What are the main advantages of questioning assumptions when building software? 2. How does the "Akin's 33rd law of spacecraft design" apply to software development? 3. What are the most common "Falsehoods WordPress Developers Believe"? <!-- deep-read:sections end --> ## Highlights - Falsehoods WordPress Developers Believe 1. WordPress roles are static across sites. 2. WordPress Roles are at least static during each request. 3. A WordPress user can only have one role 4. Two Users with the same role will have the same capabilities. 5. If a user has a capability earlier in a request, they will still have it later in the request. 6. WordPress roles are hierarchical. ([View Highlight](https://read.readwise.io/read/01gts5zb7eam0a2zyvcgc98rhn))