Click any tag below to further narrow down your results
Links
Amazon built a competitive advantage around forcing clear thinking through mandatory memo writing — six-page documents that executives had to read silently before discussing. Now that AI can generate those memos instantly, people skip the thinking step entirely, and the author argues this is eroding decision quality and trust across the company.
- Amazon's writing ritual (30-minute silent reading sessions, red-pen feedback) forced rigorous thinking before wasting colleagues' time; AI-generated documents bypass this filter, leading to half-baked decisions that compound over time.
- Performance reviews have devolved into managers copy-pasting AI summaries of AI summaries, turning what used to drive career growth conversations into "a conversation between two prompts" with humans as intermediaries.
- The author proposes a practical rule: use AI freely for reversible "two-way door" decisions (status updates, code reviews, routine tasks), but require humans to write and read for irreversible "one-way door" decisions (strategy, hiring, major architecture changes).
The author argues that standard hiring practices—especially heavy reference checking—don't actually predict future performance better than we think they do. After 50+ hires, he's learned that we mistake subjective judgment and past narratives for objective truth, while ignoring how much a person's performance depends on their environment and manager.
- Multiple references from the same company or network often reflect a shared narrative rather than independent information, and references themselves are biased participants, not neutral observers.
- Past experience is a poor predictor for roles involving rapidly changing technologies and requirements; someone's ability to learn and adapt matters more than years in adjacent roles.
- Most hiring advice is anecdotal autobiography—individual companies rarely hire enough people in similar roles to prove statistically which methods actually work, yet we treat personal success as universal methodology.
- We evaluate candidates heavily but rarely assess whether the company, manager, or system will actually enable good performance, treating professional capability as an individual trait rather than a system outcome.
A manager and engineer at a security firm discuss how AI tools have stripped away the satisfaction of deep technical work—replacing problem-solving with prompt management and eroding the sense of ownership over code. They explore whether the tradeoff of faster output for lost engagement is worth it, and what might make the role meaningful again.
- Engineers report losing satisfaction because AI handles complexity they once owned, shifting their role from critical thinking toward management-style coordination rather than hands-on technical work.
- The manager acknowledges the real cost: after 15 years mastering a skill, watching AI surpass you at it is demoralizing, but the solution isn't rejecting AI—it's using it to tackle harder problems instead of just faster ones.
- Post-holiday malaise and team disorganization compound the issue, but the underlying problem is that engineers feel disconnected from their own work and the codebase direction when development moves too fast.
The author argues that staying in comfortable jobs too long creates "career debt" — lost growth and opportunity that compounds over time. He outlines three types of career debt (comfort, saying yes to everything, avoiding difficult conversations) and offers concrete audits to identify and fix them.
- Comfort in a role without growth or good management is a losing bet: the author spent two years stagnating at Amazon in a senior position with an under-leveled manager, then needed two years to recover the lost ground.
- Overcommitting to low-value tasks (like volunteering for 1,000 interviews) drains focus from high-impact work and feels productive while actually building debt.
- Avoiding difficult conversations makes problems worse — bad news delivered late becomes a crisis, while early delivery is just information.
@dklineii on X
This is a skills file for building an AI-generated morning brief that reads your calendar, email, tasks, team chat, and metrics, then returns a one-screen plan. It walks through six reads (Day, Decisions, People, Meetings, World, Move) and six prompts to run it, including a "people radar" for spotting team members who need attention.
- The brief runs as a 15-minute daily routine, ideally before opening email, so your priorities set the day rather than your inbox.
- Four rules govern output: name actual meetings and times instead of generic advice, flag missing data instead of stopping, actually research external contacts, and never fabricate.
- The People read is presented as the key differentiator for managers, since it covers team check-ins, commitments from 1:1s, and early signs of disengagement.
- The author suggests pasting the article into Claude Cowork to build the skill, connecting your tools, and scheduling it to run overnight.
This article explains how to turn routine 1:1 meetings into strategic sessions by covering three key topics: current status, career growth, and future direction. It stresses that strong manager relationships drive promotions and offers a simple framework to structure each meeting for maximum impact.
- The quality of your 1:1 relationship with your manager determines how fast you get promoted, based on nearly 20 years and 20+ managers at Amazon
- Split each 1:1 into three threads: status update (max 5 minutes), career growth (goals, skill gaps, concrete asks like intros or stretch assignments), and future direction (upcoming projects, team priorities, org shifts)
- A 30-minute meeting is enough to cover all three threads if structured with a clear agenda
This article outlines four clear indicators that your manager has disengaged—lack of specific feedback, being passed over for new projects, disappearing 1:1s, and postponed career talks. It then offers direct steps to re-engage them by asking for expectations and presenting a concrete growth plan.
- Vague, minimal feedback ("looks good") and being excluded from decisions signals disengagement, not trust-based autonomy
- Consistently getting routine/low-visibility tasks while the same colleagues get high-profile projects is a red flag if it repeats over months
- Shrinking or disappearing 1:1s mean you've lost your advocate and are out of the loop
- Career conversations that keep getting deferred to "next quarter" with vague advice mean the manager hasn't invested real thought in your growth
Non-programming leaders starting to contribute to code with LLMs can increase iteration speed and introduce diverse perspectives, but this also risks compromising the implicit architecture of the codebase. As more non-engineers make changes, maintaining design intent and code maintainability becomes a challenge, requiring developers to adapt their roles to focus on architectural oversight. Despite these risks, democratizing coding could lead to better solutions as more perspectives are included in the development process.
- LLMs are lowering the barrier enough that non-engineer bosses/founders are now directly committing code, not just prototyping
- The real risk isn't code quality but erosion of implicit architecture—decisions and conventions that were never written down and that LLMs can't infer
- This forces a shift in developers' roles toward explicit architectural oversight and codifying design intent so it survives contact with non-engineer contributors
- Despite the risks, wider participation in coding could surface better solutions by incorporating more diverse perspectives into development