AI for Technology & IT

Build with AI. Keep engineering discipline.

Use AI to prepare code, tests and documentation, with engineering review before anything reaches production.

Free · 30 minutes with Ted Deane

Meet Ted · 30+ years in software development.

Illustrative workflow

  1. InputSanitised error trace
  2. AI preparesDraft fix and test cases
  3. You checkEngineer reviews and runs

Familiar work, a useful starting point

Put AI to work on familiar tasks.

Investigate a defect

Use a sanitised error trace and a minimal example to draft a fix and regression tests.

Write a useful runbook

Turn approved setup notes into reproducible steps that another engineer can test.

Review a change

Compare a proposed change with the requirements and draft checks for failure cases, permissions and recovery.

Worked example

A small defect with a clear requirement

Illustrative example using fictional information.

AI prepares

Proposed fix for engineering review

function firstLabel(items) {
  if (items.length === 0) return 'No items';
  return items[0].label;
}
Source S1, S2

Proposed regression checks

  • []Expected: No itemsSource S1
  • [{label: 'Open'}]Expected: OpenSource S1

You check · Responsible engineer

The engineer uses sanitised context, protects credentials, reviews the input contract and runs regression checks before approving a real change.

The support is your choice

Choose the support that fits your work.

Learn with DoJo

Build and apply skills yourself, with course access, fortnightly group support and a private community.

A$250 per seat per month, excluding GST.

Get guidance with Peer Group

Work through implementation with peer discussion and one-to-one guidance. DoJo is included.

A$800 per seat per month, excluding GST.

Have it built with OpsFoundry

Discuss a workflow designed and built around your processes, systems and approval points.

Scope and commercial terms agreed separately.

A pathway around your work

Build a skill you can use.

  1. Define a reproducible defect

    Keep expected behaviour, sanitised context and a minimal example together.

  2. Try a small proposed fix

    Review the change against the requirement and prepare regression cases.

  3. Check runtime evidence

    Run the relevant checks and record both passing and failing evidence before approval.

Explore relevant learning

Learning that supports this task

A small sample of 30,000+ courses curated from around the world, all available to DoJo members.

Before you start

Common questions

Can we start with our current stack?

Yes. Bring the languages, tools, constraints and the problem you want to solve. Course selection and any implementation scope should fit your actual environment and experience.

What should I bring to the discovery call?

Bring one task, the tools you use and who checks the work. A fictional or de-identified sample can help.

Your next step

Bring one task to the conversation.

Discuss what you want to improve and a useful starting point in a free 30-minute conversation with Ted.

Bring one task, the tools you use and who checks the work. A fictional or de-identified sample can help.

Book a discovery call