AI Leaders and Thinkersβ€’β€’6 min readβ€’1097 words

πŸ€– AI Development - Nockchain and PRL Token Integration

⚑Direct Technical Summary

Nockchain, a decentralized finance (DeFi) platform, has integrated the PRL token from the PRL protocol. This integration allows for the use of PRL as a wrapped token on Nockchain.

πŸ€– AI Development - Nockchain and PRL Token Integration

Nockchain, a decentralized finance (DeFi) platform, has integrated the PRL token from the PRL protocol. This integration allows for the use of PRL as a wrapped token on Nockchain. The PRL protocol is the original creator of the POUW (Proof of Useful Work) consensus algorithm used by Nockchain.

Key Points:

  • Wrapped Token Integration: Nockchain has integrated the PRL token, allowing for its use as a wrapped token on the platform.

  • POUW Consensus Algorithm: The PRL protocol is the original creator of the POUW consensus algorithm used by Nockchain.

  • Token Utility: The integration of PRL as a wrapped token on Nockchain provides utility for users and developers.

πŸ”— Resources:


πŸ“Š Marketing - Human-Centric Approach to Sales

Most people are not concerned with marketing metrics such as funnels, CTRs, and press releases. Instead, they are worried about everyday human concerns such as getting a promotion, their health, and their love life. As marketers, it is essential to remember that we are selling to people, not just numbers.

Key Points:

  • Human-Centric Approach: Marketers should focus on human concerns rather than just marketing metrics.

  • Sales Focus: Sales should be centered around people's needs and desires, not just numbers.

  • Marketing Strategy: A human-centric approach to marketing can lead to more effective sales and customer engagement.

🚨 Code Quality - The Cost of Cutting Corners

Cutting corners in code development can lead to fragile and vulnerable codebases. A developer shared their experience of shipping clean, secure code, but then cutting corners due to a deadline. The result was a codebase that felt fragile and vulnerable.

Key Points:

  • Code Quality: Cutting corners in code development can lead to fragile and vulnerable codebases.

  • Deadline Pressure: Deadlines can lead to cutting corners, which can have negative consequences.

  • Code Maintenance: A fragile codebase can be difficult to maintain and may require significant resources to fix.

πŸš€ Jev Workflows 0.3 Release Candidate

Jev Workflows 0.3 release candidate is now available. This release includes a Codex plugin for tool/model/task decisions, failure diagnosis, and completion checks. The plugin is open-source and optional, with no plugin-imposed call quotas.

Key Points:

  • Jev Workflows 0.3: The release candidate includes a Codex plugin for tool/model/task decisions, failure diagnosis, and completion checks.

  • Open-Source: The plugin is open-source and optional.

  • Call Quotas: There are no plugin-imposed call quotas.

🚫 Liability Gap in AI Development

A simple legislative fix can patch the liability gap in AI development. If an AI agent does something that would be a tort for a human, someone should be liable. If no downstream actor intended or was negligent with respect to the conduct, the buck should stop with the developer.

Key Points:

  • Liability Gap: A simple legislative fix can patch the liability gap in AI development.

  • Tort Liability: If an AI agent does something that would be a tort for a human, someone should be liable.

  • Developer Liability: If no downstream actor intended or was negligent with respect to the conduct, the buck should stop with the developer.

πŸš€ Community Engagement - Automating Automation

The community is 1000x-ing the updates to cookbooks, best practices, and use cases. The Factorio-ing is real too; some of the highest leverage additions are automating your automation, like teaching your agents how to use Jev directly in your automation.

Key Points:

  • Community Engagement: The community is 1000x-ing the updates to cookbooks, best practices, and use cases.

  • Automation: Automating your automation can lead to significant leverage and efficiency gains.

  • Jev Integration: Teaching your agents how to use Jev directly in your automation can be a high-leverage addition.

πŸ€– Team Communication - New Expressions

Some new favorite expressions in the team include "slashgoaling" (prompting the agent or coworker to complete a task), "how's your pdoom today" (are you okay), and "what's goal.md" (what is our objective function for this project).

Key Points:

  • Team Communication: The team has adopted new expressions to improve communication and collaboration.

  • Agent/Coworker Interaction: The expressions "slashgoaling" and "how's your pdoom today" can be used to interact with agents or coworkers.

  • Objective Function: The expression "what's goal.md" can be used to clarify the objective function for a project.

🚫 Amazon's Agent Strategy

Amazon will allow agents as soon as they can be sure there won’t be one winner in the agent space. If there are 100 meaningful agent products, supporting them all makes sense. If there are only one or two doing all the shopping, Amazon gets taxed or cut out.

Key Points:

  • Amazon's Agent Strategy: Amazon will allow agents as soon as they can be sure there won’t be one winner in the agent space.

  • Agent Diversity: Supporting multiple agent products can lead to a more diverse and competitive market.

  • Taxation/Cut-Out: If there is only one or two dominant agent products, Amazon may be taxed or cut out.

πŸ“š Education - Public vs Private Schools

My (hard earned) opinion on public vs private vs whatever is ultimately it comes down to admin + teachers + standards, and in no school do you get to choose your admin or teachers or standards (you get what you get and you don't get upset). So if you can, my advice is to leave.

Key Points:

  • Education: The choice between public and private schools ultimately comes down to admin, teachers, and standards.

  • Admin, Teachers, and Standards: These factors are outside of a student's control, regardless of the school type.

  • Advice: If possible, consider leaving a school that does not meet your needs.

πŸ€– Consumer Behavior - Instinct vs Muse

Most consumers prefer the ease and speed of Muse over Instinct, despite Instinct being technically superior. Tech nerds may argue about the technical differences, but consumers are not concerned with these details.

Key Points:

  • Consumer Behavior: Consumers prefer the ease and speed of Muse over Instinct, despite Instinct being technically superior.

  • Technical Differences: Tech nerds may argue about the technical differences, but consumers are not concerned with these details.

  • Ease and Speed: Ease and speed are more important to consumers than technical superiority.

πŸ“‚Source / Implementation:AI Leaders and Thinkers / resources-269.md
GitHub Repository↗

Related AI Leaders and Thinkers Breakdowns

Drishtant Ghosh (Drix10)
Drishtant Ghosh (Drix10)β€’Author & Engineer

Technical founder and engineer working across AI systems, developer infrastructure, and cybersecurity.