7-Step P.R.O.C.E.S.S.
7-Step P.R.O.C.E.S.S.
7-Step P.R.O.C.E.S.S.
For Creating
For Creating
For Creating
Learn a simple and repeatable framework that we will use every day during the challenge to create new pyRevit tools from scratch.
Bonus P.R.O.C.E.S.S. Tutorials:
Bonus P.R.O.C.E.S.S. Tutorials:
00:42:15
00:47:25
The Research Example Walkthrough
BONUS LESSON
22:00
The Research Example Walkthrough
BONUS LESSON
22:00
The Research Example Walkthrough
BONUS LESSON
22:00
The 7-Step P.R.O.C.E.S.S.
for Building New pyRevit Tools
Follow repeatable 7 steps to build better pyRevit tools in less time - by making sure you focus on the right things.
1. PLAN
Prepare
Get clear on WHAT problem are you solving and WHY? And more importantly - always ask "Is It Even Worth Automating?".
4. CODE
Code
Finally coding. But many get this wrong…
The goal is NOT to write the complete script. The goal is to create a proof of concept(POC). Ignore how your code looks and works and even skip steps. Just Make It Work…
2. RESEARCH
Prepare
Research might sound boring but not as boring as wasting days…
So, look around for useful resources.
Often times you'll find code snippets or tutorials or even full scripts that will help you to create your custom tool. USE IT!
5. EDIT
Code
Only after you have a POC you should put more time and effort into the tool. This is where you'll rewrite your code to address all steps, optimize code, make it more readable and handle errors.
3. OUTLINE
Prepare
Create a simple step-by-step outline of logic flow. It can be on paper, text or digital diagram… Anything that helps you brainstorm.
6. STRESS-TEST
Code
Then, it's time to break your new tool in every way possible.
You don't want your team or boss to see a huge error message. So find and fix all issues before it's too late. Your reputation matters.
7. SHIP
Done
Finally, you can ship your tool.
Add it proudly to your toolbar and share it with the team to get them excited too. Now you can see how others click and see instant results with your new tools.
That's when you feel like a True pyRevit Developer.
The 7-Step P.R.O.C.E.S.S.
for Building New pyRevit Tools
Follow repeatable 7 steps to build better pyRevit tools in less time - by making sure you focus on the right things.
1. PLAN
Prepare
Get clear on WHAT problem are you solving and WHY? And more importantly - always ask "Is It Even Worth Automating?".
4. CODE
Code
Finally coding. But many get this wrong…
The goal is NOT to write the complete script. The goal is to create a proof of concept(POC). Ignore how your code looks and works and even skip steps. Just Make It Work…
2. RESEARCH
Prepare
Research might sound boring but not as boring as wasting days…
So, look around for useful resources.
Often times you'll find code snippets or tutorials or even full scripts that will help you to create your custom tool. USE IT!
5. EDIT
Code
Only after you have a POC you should put more time and effort into the tool. This is where you'll rewrite your code to address all steps, optimize code, make it more readable and handle errors.
3. OUTLINE
Prepare
Create a simple step-by-step outline of logic flow. It can be on paper, text or digital diagram… Anything that helps you brainstorm.
6. STRESS-TEST
Code
Then, it's time to break your new tool in every way possible.
You don't want your team or boss to see a huge error message. So find and fix all issues before it's too late. Your reputation matters.
7. SHIP
Done
Finally, you can ship your tool.
Add it proudly to your toolbar and share it with the team to get them excited too. Now you can see how others click and see instant results with your new tools.
That's when you feel like a True pyRevit Developer.
The 7-Step P.R.O.C.E.S.S. Method
These 7 steps will help you create better tools in less time and avoid wasting hours or even days on bad ideas.
Recap
1. PLAN
Prepare
Get clear on WHAT problem are you solving and WHY? And more importantly - always ask "Is It Even Worth Automating?".
4. CODE
Code
Finally coding. But many get this wrong…
The goal is NOT to write the complete script. The goal is to create a proof of concept(POC). Ignore how your code looks and works and even skip steps. Just Make It Work…
2. RESEARCH
Prepare
Research might sound boring but not as boring as wasting days…
So, look around for useful resources.
Often times you'll find code snippets or tutorials or even full scripts that will help you to create your custom tool. USE IT!
5. EDIT
Code
Only after you have a POC you should put more time and effort into the tool. This is where you'll rewrite your code to address all steps, optimize code, make it more readable and handle errors.
3. OUTLINE
Prepare
Create a simple step-by-step outline of logic flow. It can be on paper, text or digital diagram… Anything that helps you brainstorm.
6. STRESS-TEST
Code
Then, it's time to break your new tool in every way possible.
You don't want your team or boss to see a huge error message. So find and fix all issues before it's too late. Your reputation matters.
7. SHIP
Done
Finally, you can ship your tool.
Add it proudly to your toolbar and share it with the team to get them excited too. Now you can see how others click and see instant results with your new tools.
That's when you feel like a True pyRevit Developer.
© 2023-2026 EF Learn Revit API
© 2023-2026 EF Learn Revit API
© 2023-2026 EF Learn Revit API