Featured· Fast Company· Nov 21
High performers can avoid costly career regrets by delegating before burnout, keeping their own records of results, asking for support early, and communicating accomplishments clearly.
- Document key workflows and delegate authority while you still have capacity, including tasks you enjoy.
- Write a case study after each important project with the problem, your actions, and measurable results; save reusable testimonials and metrics.
- Schedule regular check-ins with a mentor, supervisor, or therapist before you need urgent help.
Try todaySchedule a recurring check-in with a mentor, supervisor, or therapist.
Next Big Idea Club· Fast Company· Nov 21
Martignetti’s leadership approach starts by uncovering overlooked strengths, then balancing competing priorities and designing practices that keep your work focused and sustainable.
- Trace a turning point when your old professional story stopped working; ask what part of yourself you had hidden and what it cost.
- Map a tension such as compassion and performance; look for ways to strengthen both instead of choosing one.
- Run a small experiment at the edge of freedom and structure, then use what works to shape your practices and priorities.
Try todayWrite down one tension you face at work and identify a way to support both sides.
Dan Zhang· Fast Company· Nov 21
ClickUp argues companies should select employees with strong process knowledge to build useful AI skills, measure verified impact, and reward them for making their expertise reusable.
- Choose builders with strong performance and knowledge of where work processes break.
- Classify each AI skill by impact, record a baseline, then compare results and subtract tool and maintenance costs.
- Set rewards by verified value and how long it lasts: use bonuses for one-off gains and raises for ongoing contributions.
Try todayList one recurring process bottleneck and record its current cost, time, or failure rate before testing an AI skill.
Gergely Orosz· The Pragmatic Engineer· Nov 18
CodeRabbit CEO Harjot Gill describes using agents to ship software quickly, while maintaining quality through layered verification, staged rollouts, and human review of releases rather than individual pull requests.
- Use agents for recurring engineering work such as fixing flaky tests, improving CI, and refining caching.
- Give agents ways to verify their work: use simulations, API emulation, development environments, and staged rollouts.
- Review plans and releases that combine multiple pull requests, rather than reviewing every agent-generated pull request individually.
Try todayChoose one recurring engineering task and have an agent tackle it with a clear way to verify the result.
Gergely Orosz· The Pragmatic Engineer· Nov 16
Satya Nadella argues that as AI makes code generation cheaper, teams need stronger verification, flexible model infrastructure, and new ways to improve how they work.
- Keep the agent harness, memory, and model separate so you can change providers without lock-in.
- Build private evaluations to compare models, and verify agent outputs as if agents were insider risks.
- Route work between local models and cloud models based on capability and cost.
Try todayList which parts of your AI setup are coupled, then identify one you could make easier to replace.
Anne Neuberger· a16z· Nov 12
The plan focuses national cyber defense on critical operators and shared vendors, using AI to find and fix vulnerabilities while setting measurable, accountable sector targets.
- Prioritize operators and shared vendors whose failure could cascade across power, payments, water, communications and hospitals.
- Use AI to find vulnerabilities and test patches or workarounds, including for legacy systems that cannot be patched.
- Remove internet exposure from control systems, segment networks and test whether operations can continue manually for 72 hours.
Try todayMap your critical systems and vendors, then flag exposed control systems and dependencies that could cause cascading failures.
Gergely Orosz· The Pragmatic Engineer· Nov 10
An interview with Sean Allen on software correctness: encode invariants in language and design, use repeatable workloads to test behavior, and build validation into development rather than adding quality gates late. It also discusses limits to supply-chain defenses.
- Define software invariants and use language features that prevent invalid states from being expressed.
- Run repeatable workloads, such as a bank test, to check system behavior and database isolation.
- Build correctness validation into development from the start instead of relying on late-stage quality gates.
Try todayChoose one important system invariant and identify how to validate it during development.