Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

question: is doing `.run(...)` on a task within a task an antipattern?

example:
```@task
def do_other_stuff(name: str)
  return f"hello {name}"

@task
def do_stuff():
  result = do_other_stuff.run("christian")```

It’s not. Just know it’s not a first class task with retries and results and state tracking. It’s just the python under the hood.

so related: is this a way to create a general "helper" function to "say_hello"?

```@task
def generate_name():
  return "christian"

@task
def generate_hello(name: str):
  return f"hello {name}"

def say_hello():
  name = generate_name()
  hello = generate_hello(name)
  return hello

with Flow(...):
  response = say_hello()```

Yeah that is fine. Not sure if you need the return but that will work!