Daniel Idaszak
@idaszak.com
React Native Dev, Tech Leadership Blogger - idaszak.com
Pinned
Daniel Idaszak
@idaszak.com
· Nov 7
Tech Leadership Newsletter
Soft Skills, Technical Writing, and Tech Leadership Newsletter.
www.idaszak.com
Hello, I'm Daniel 👋
On my blog www.idaszak.com/newsletter/ you can find content about:
⚙️ Software Engineering,
📖 Documentation,
🧠 Leadership and Soft Skills.
On my blog www.idaszak.com/newsletter/ you can find content about:
⚙️ Software Engineering,
📖 Documentation,
🧠 Leadership and Soft Skills.
Teams often rely on documentation to drive change, but the real shift happens when the environment enforces the new standard. Tools, not text, shape habits.
November 23, 2025 at 1:01 PM
Teams often rely on documentation to drive change, but the real shift happens when the environment enforces the new standard. Tools, not text, shape habits.
The most useful documentation answers “why.” The moment it tries to enforce “how,” automation usually does a better job, and stays accurate far longer.
November 22, 2025 at 1:01 PM
The most useful documentation answers “why.” The moment it tries to enforce “how,” automation usually does a better job, and stays accurate far longer.
If a rule requires everyone to “just remember it,” it’s already failing. Codifying it in automation or tooling creates consistency without adding cognitive load.
November 21, 2025 at 1:01 PM
If a rule requires everyone to “just remember it,” it’s already failing. Codifying it in automation or tooling creates consistency without adding cognitive load.
Most outdated documentation isn’t the result of poor writing. It’s a symptom of processes that were never meant to be manual.
Scripts, generators, and linters eliminate the drift.
Scripts, generators, and linters eliminate the drift.
November 20, 2025 at 1:01 PM
Most outdated documentation isn’t the result of poor writing. It’s a symptom of processes that were never meant to be manual.
Scripts, generators, and linters eliminate the drift.
Scripts, generators, and linters eliminate the drift.
A look at where documentation helps, and where automation does a better job.
CLIs, generators, linters, commit rules, IDE configs. Less manual work, fewer mistakes.
New Article at Tech Lead Toolkit.
CLIs, generators, linters, commit rules, IDE configs. Less manual work, fewer mistakes.
New Article at Tech Lead Toolkit.
November 19, 2025 at 1:01 PM
A look at where documentation helps, and where automation does a better job.
CLIs, generators, linters, commit rules, IDE configs. Less manual work, fewer mistakes.
New Article at Tech Lead Toolkit.
CLIs, generators, linters, commit rules, IDE configs. Less manual work, fewer mistakes.
New Article at Tech Lead Toolkit.
Documentation is great, until it becomes a burden.
Tomorrow I’m sharing how to replace fragile process docs with automation: CLIs, generators, linters, and shared configs.
If you want standards that enforce themselves, don’t miss it, subscribe.
Tomorrow I’m sharing how to replace fragile process docs with automation: CLIs, generators, linters, and shared configs.
If you want standards that enforce themselves, don’t miss it, subscribe.
November 18, 2025 at 1:00 PM
Documentation is great, until it becomes a burden.
Tomorrow I’m sharing how to replace fragile process docs with automation: CLIs, generators, linters, and shared configs.
If you want standards that enforce themselves, don’t miss it, subscribe.
Tomorrow I’m sharing how to replace fragile process docs with automation: CLIs, generators, linters, and shared configs.
If you want standards that enforce themselves, don’t miss it, subscribe.
Reposted by Daniel Idaszak
Introducing complex changes in big organizations is tough - spreading awareness is easy, but driving real action is harder. Learn how to make changes stick using over-communication, ADRs, and the ADKAR framework to turn awareness into lasting adoption.
August 19, 2025 at 2:06 PM
Introducing complex changes in big organizations is tough - spreading awareness is easy, but driving real action is harder. Learn how to make changes stick using over-communication, ADRs, and the ADKAR framework to turn awareness into lasting adoption.
Reposted by Daniel Idaszak
It’s Friday, and you’ve just finished work.
Did you win or lose this week — in your own perspective?
The week was intense, but it’s hard to say what you actually achieved.
Good planning can help with this:
Article about winning your weeks: read.perspectiveship.com/p/winning-th...
Did you win or lose this week — in your own perspective?
The week was intense, but it’s hard to say what you actually achieved.
Good planning can help with this:
Article about winning your weeks: read.perspectiveship.com/p/winning-th...
On Planning and Winning the Week
Get things done by balancing the supply of time with the demand of tasks.
read.perspectiveship.com
August 29, 2025 at 9:48 AM
It’s Friday, and you’ve just finished work.
Did you win or lose this week — in your own perspective?
The week was intense, but it’s hard to say what you actually achieved.
Good planning can help with this:
Article about winning your weeks: read.perspectiveship.com/p/winning-th...
Did you win or lose this week — in your own perspective?
The week was intense, but it’s hard to say what you actually achieved.
Good planning can help with this:
Article about winning your weeks: read.perspectiveship.com/p/winning-th...
Reposted by Daniel Idaszak
Communicating change once is never enough. In big organizations, messages disappear. Over-communication through multiple channels is the only way to make sure critical updates actually reach everyone.
August 20, 2025 at 12:01 PM
Communicating change once is never enough. In big organizations, messages disappear. Over-communication through multiple channels is the only way to make sure critical updates actually reach everyone.
Reposted by Daniel Idaszak
Introducing change in big teams isn’t just about telling people what’s new. Without planning for awareness, desire, knowledge, ability, and reinforcement, the change will stall before it takes hold.
August 21, 2025 at 12:02 PM
Introducing change in big teams isn’t just about telling people what’s new. Without planning for awareness, desire, knowledge, ability, and reinforcement, the change will stall before it takes hold.
Introducing change in big teams isn’t just about telling people what’s new. Without planning for awareness, desire, knowledge, ability, and reinforcement, the change will stall before it takes hold.
August 21, 2025 at 12:02 PM
Introducing change in big teams isn’t just about telling people what’s new. Without planning for awareness, desire, knowledge, ability, and reinforcement, the change will stall before it takes hold.
Communicating change once is never enough. In big organizations, messages disappear. Over-communication through multiple channels is the only way to make sure critical updates actually reach everyone.
August 20, 2025 at 12:01 PM
Communicating change once is never enough. In big organizations, messages disappear. Over-communication through multiple channels is the only way to make sure critical updates actually reach everyone.
Introducing complex changes in big organizations is tough - spreading awareness is easy, but driving real action is harder. Learn how to make changes stick using over-communication, ADRs, and the ADKAR framework to turn awareness into lasting adoption.
August 19, 2025 at 2:06 PM
Introducing complex changes in big organizations is tough - spreading awareness is easy, but driving real action is harder. Learn how to make changes stick using over-communication, ADRs, and the ADKAR framework to turn awareness into lasting adoption.
Reposted by Daniel Idaszak
Afraid of AI?
Will some jobs go extinct because of new technologies?
Yes, for sure.
It happened before.
Many times.
It's up to you.
Evolution advises us to focus on ADAPTATION.
It can help as a mental model for survival.
I wrote an article about it: read.perspectiveship.com/p/evolution
Will some jobs go extinct because of new technologies?
Yes, for sure.
It happened before.
Many times.
It's up to you.
Evolution advises us to focus on ADAPTATION.
It can help as a mental model for survival.
I wrote an article about it: read.perspectiveship.com/p/evolution
Evolution - Mental Model: AI-voiding Extinction
Species adapt, or they go extinct.
read.perspectiveship.com
August 1, 2025 at 12:03 PM
Afraid of AI?
Will some jobs go extinct because of new technologies?
Yes, for sure.
It happened before.
Many times.
It's up to you.
Evolution advises us to focus on ADAPTATION.
It can help as a mental model for survival.
I wrote an article about it: read.perspectiveship.com/p/evolution
Will some jobs go extinct because of new technologies?
Yes, for sure.
It happened before.
Many times.
It's up to you.
Evolution advises us to focus on ADAPTATION.
It can help as a mental model for survival.
I wrote an article about it: read.perspectiveship.com/p/evolution
Reposted by Daniel Idaszak
If developers can review docs in a pull request just like code, quality improves. The toolchain matters more than we admit.
June 20, 2025 at 12:04 PM
If developers can review docs in a pull request just like code, quality improves. The toolchain matters more than we admit.
If developers can review docs in a pull request just like code, quality improves. The toolchain matters more than we admit.
June 20, 2025 at 12:04 PM
If developers can review docs in a pull request just like code, quality improves. The toolchain matters more than we admit.
Documentation doesn't get immediate praise like a new feature does. That’s why teams need leaders who treat it as a deliverable.
June 19, 2025 at 12:04 PM
Documentation doesn't get immediate praise like a new feature does. That’s why teams need leaders who treat it as a deliverable.
It’s easier to justify perfect code than basic documentation. But it's the missing docs that slow teams down later.
June 18, 2025 at 12:02 PM
It’s easier to justify perfect code than basic documentation. But it's the missing docs that slow teams down later.
The best onboarding documentation isn’t comprehensive. It’s structured to avoid overwhelming someone on day one.
June 17, 2025 at 12:02 PM
The best onboarding documentation isn’t comprehensive. It’s structured to avoid overwhelming someone on day one.
Most developers haven’t yet experienced the pain of missing documentation. That’s why they don’t prioritize it, until they have to.
June 16, 2025 at 12:02 PM
Most developers haven’t yet experienced the pain of missing documentation. That’s why they don’t prioritize it, until they have to.
Many dev teams think they have a documentation problem. They usually have a tooling and process problem.
June 15, 2025 at 12:02 PM
Many dev teams think they have a documentation problem. They usually have a tooling and process problem.
Why is internal documentation so often neglected? Because no one rewards it, reviews it, or owns it.
June 14, 2025 at 12:01 PM
Why is internal documentation so often neglected? Because no one rewards it, reviews it, or owns it.
Reposted by Daniel Idaszak
Most developers avoid writing documentation, and for good reasons.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
June 12, 2025 at 1:24 PM
Most developers avoid writing documentation, and for good reasons.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
Is your documentation maintained, or just written once and forgotten? The last updated date tells a story, make sure it’s a good one.
June 13, 2025 at 12:02 PM
Is your documentation maintained, or just written once and forgotten? The last updated date tells a story, make sure it’s a good one.
Most developers avoid writing documentation, and for good reasons.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
June 12, 2025 at 1:24 PM
Most developers avoid writing documentation, and for good reasons.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.
This article explores the real blockers behind poor internal docs, from tool friction to lack of ownership, and offers practical ways teams can make documentation less painful and more useful.