How to Work with a Developer in Creative Production


  • TL;DR / Intro (10 mins)

    • A developer creates software and applications, working with others to complete tasks efficiently.
    • Common tasks include programming, systems design, integration, time management, collaboration, problem-solving/debugging, version control, learning new software/techniques, and optimization.

  • What kinds of work do you NOT produce, but people often think you do?

    • Developers integrate assets created by other teams rather than creating all assets themselves.

  • What are your role(s) called in the industry?

    • Software Developer, Game Developer, Game Designer, Systems Designer, Technical Designer, Combat Designer, UI/UX Designer, and more.

  • Required resources and tools (5 mins)

    • Depends on the project, but common tools include Unity/Unreal Engine, Visual Studio/JetBrains IDE, GitHub/Plastic SCM for version control, Miro/LucidCharts/Trello for diagrams, and Slack/Discord for communication.
    • Project leads may enforce specific software based on project scope and team size.

  • Deliverables and time estimation (15 mins)

    • Commonly use organizational tools like Jira, Scrum, and asset spreadsheets to track progress.
    • Time estimation varies depending on tasks and may encounter issues like programming bugs, software crashes, integration issues, and communication errors.

  • Giving Instructions and Feedback (15 mins)

    • Documentation, tutorials, and onboarding new developers are essential for starting tasks.
    • Constructive feedback is encouraged through various mediums like in-person meetings, virtual sessions, images, drawings, text, etc.

  • Traits of high-quality work

    • Hard-working, motivated, communicates effectively, meets deadlines, helps others, asks for help when needed, accountable, comments code, dedicated, enthusiastic, goes the extra mile.

  • Traits of sloppy, rushed work

    • Procrastinates, poor communication, lacks collaboration, misses deadlines, avoids seeking help, doesn't comment code, lacks dedication, dispassionate, ignores communication.

  • Best Practices for Collaboration (15 mins)

    • Problem-solving, effective communication, meeting deadlines, addressing knowledge gaps, and avoiding laziness are crucial.
    • Project leads/coordinators should assist in resolving issues.

  • Vocabulary for effective communication

    • Version control, deliverables, game engine objects, types of developers, coding interfaces, external tools, etc.

  • Additional Resources