#Communication
32 notas · última:
How to make your team read your mind
The article argues that unclear expectations make team work harder than it needs to be, and that writing a manager’s ReadMe helps surface priorities, working norms, and responsibilities.
From Tech Docs to Blog Posts: How Writing Can Transform Your Career
The post argues that writing online improves technical writing by forcing clearer reading, reflection, and outcomes. It also says exposure reduces fear and makes repeated practice easier.
From Code to Words: How to Write Well for Software Engineers
The post argues that writing is a core engineering skill because it aligns teams, reduces meetings, and creates a shared record. It frames good writing as a practice built through Identify, Iterate, and Invite.
Avoid Walking In Circles While Blazing Trails: Advice for Early Stages of Project Development
The article says early project work should accept uncertainty, focus on the most important requirements, build an MVP, choose tech with practical criteria, and keep team and client aligned.
Driving Change
Using the switch from right-hand to left-hand driving in Ireland, the article shows how change works better when it is incremental, repeated, visible, and supported by people who already adapted.
15 Best Leadership Books
A curated reading guide for leaders that highlights books on communication, habits, feedback, emotional intelligence, team trust, motivation, and practical management.
How to Stay Calm Under Pressure?
The article proposes BAA — Breath, Assess, and Act — for high-pressure moments. It says fear can lead to blabbering, premature promises, or rash fixes, so you should pause, clarify what you know, and respond directly.
Don’t be a Spineless Leader: 3 Tips to Lead Better
The post says weak leadership comes from pleasing everyone, deciding too fast, and avoiding disagreement. It recommends asking questions, stating disagreement clearly, and aligning teams, managers, and partners.
7 Tips for Killer Presentations
The article argues that strong presentations start with a clear story, a specific audience, and one message per slide. Good delivery and rehearsal keep the audience engaged.
How to Build Good Relationships Inside and Outside Your Engineering Team
The post says engineers collaborate better when they build good relationships, because isolation leads to uncertainty and weaker impact. It recommends reciprocity, trust, respect, and time spent on personal topics and shared interests.
Essential Skills for Engineers to Thrive in the AI Era
The piece argues that engineers will need clearer communication, better problem definition, curiosity, continuous learning, adaptability, and strong fundamentals to use AI well and avoid overreliance on it.
Useful and Overlooked Skills
The text lists underrated skills: tolerating inconvenience, calibrating beliefs, talking with those who disagree, getting to the point, saying no with diplomacy, and recognizing the role of luck and risk.
“How to Write” — 10 Pieces of Timeless Advice by David Ogilvy
David Ogilvy's memo says that writing well helps career advancement, is not a natural talent, and requires discipline, clarity, short sentences, revision, and focus on what the recipient should do.
Don’t Create Chaos | Stay SaaSy
The post argues that effective leadership reduces confusion: good leaders leave rooms with more certainty, clearer goals, and firmer decisions, using agendas, written confirmation, and over-communication to keep work aligned.
The 8 Mile Method
Names a negotiation tactic after Eminem's rap battle finale in 8 Mile: name the other side's strongest objection before they raise it, then work situations where that move applies.
Don't make Tech your entire personality
Developers who socialize mainly at tech meetups lose practice talking to people outside that circle. Tanay Dwivedi's fix: offline hobbies, Toastmasters, and old friends, treated as ends in themselves.
12 Hard Truths About Coding I Learned the Hard Way After 10+ Years
Twelve lessons from a decade of coding: estimates are guesses, seniority means more meetings, and almost every failed project traces back to a communication problem.
Code Is Communication: Humans First, Machines Second
00:08:48 — Code Is Communication: Humans First, Machines Second
Communication as a Developer Core Discipline
00:04:24 — Communication as a Developer Core Discipline
Noise Is More Than Static on the Line
00:09:26 — Noise Is More Than Static on the Line
How to communicate as a software engineer
The article argues that clear workplace communication is mostly about brevity, structure, and empathy: use bullets, edit before sending, leave out minutiae, and put the most important information first.
The Hardest thing about Engineering is Requirements
The post argues that requirements are hard because engineering is really a communication problem. It compares shalls, user stories, use cases, user cases, and rapid prototyping as ways to capture stakeholder intent.
Solutions Architect Tips - The 5 Types of Architecture Diagrams
The article argues that architecture diagrams should match the audience and purpose. It outlines five types—flow, service, persona, infrastructure, and developer—and explains when to use each one.
Are you a good developer already?
The post says a good developer writes working code, keeps solutions simple, avoids unnecessary repetition, keeps learning, works well in teams, seeks feedback, and communicates problems early.
Code Review Etiquette
The article explains why code reviews need shared etiquette, how harsh feedback can hurt collaboration, and how to keep critiques focused, specific, and calm.
5 Interview Mistakes You Didn't Know You’re Making
The article says interview success depends on more than prepared answers. Small talk, every question, follow-up, scheduling, and conversational balance all shape the impression you leave.
UbiquitousLanguage
Eric Evans uses “Ubiquitous Language” for the practice of building a common, rigorous language between developers and users, based on the domain model and changed as understanding of the domain grows.
Para inglês ver e brasileiro ficar esperto | Cotidiano #16
O texto contrasta o jeito brasileiro, mais disperso e excessivo, com o britânico, curto e direto, e usa uma cena em Londres para mostrar como regras claras e avisos secos funcionam.
How to Tell People You're a Fan of Their Work (Without Being Creepy)
The article says fan emails work best when they are short, specific, ask for nothing, and are not followed up on. Admiration should read as genuine, not as a request.
You can work Remote!
The post argues that remote work depends on self-discipline, overcommunication, a visible digital presence, a dedicated home office, and a morning routine, plus honesty and follow-through.
The hardest and easiest way to be a better coder
The essay argues that coder-to-coder communication is central to programming, from emotional self-awareness to readable code and kinder feedback, even if improving it is hard.
5 Ways To Be A Stronger IT Mentor
The piece says mentoring helps both mentor and mentee, then gives five practices for IT mentors: know your limits, set expectations, be available, build trust, and keep communication open.