WEBVTT

1
00:00:00.000 --> 00:00:02.241
Every repo has the same question.

2
00:00:02.241 --> 00:00:03.516
How do I build this thing?

3
00:00:03.516 --> 00:00:07.878
Bash scripts, a makefile, a Cake file nobody remembers writing.

4
00:00:07.878 --> 00:00:11.546
At TimeWarp, the answer is always one word. dev.

5
00:00:12.246 --> 00:00:17.647
Our repos all carry a dev CLI, in the same folder, with the same name and the same shape.

6
00:00:17.647 --> 00:00:21.550
Learn it once, and you can walk into any repo and get to work in seconds.

7
00:00:21.550 --> 00:00:25.072
Today, we follow one of them: TimeWarp.Nuru itself.

8
00:00:25.772 --> 00:00:27.287
It didn't start this way.

9
00:00:27.287 --> 00:00:32.384
Builds used to be a pile of separate runfiles: build, clean, test, each on its own.

10
00:00:32.384 --> 00:00:36.562
Task 256 rolled them into one dev command, with two big goals.

11
00:00:36.562 --> 00:00:38.071
Shrink the CI file.

12
00:00:38.071 --> 00:00:41.471
And run the exact same commands on your laptop that CI runs.

13
00:00:42.171 --> 00:00:44.535
Here's TimeWarp.Nuru's dev CLI.

14
00:00:44.535 --> 00:00:51.437
Ten commands: build, test, format, analyze, verify samples, and the full workflow, plus clean, check version, release and self-install.

15
00:00:51.437 --> 00:00:56.269
And notice: nobody wrote this help screen.

16
00:00:56.269 --> 00:00:59.803
It's generated straight from the code, so it can never drift out of date.

17
00:01:00.503 --> 00:01:02.788
This is the whole entry point.

18
00:01:02.788 --> 00:01:05.844
Give it a name, register a few services, discover the endpoints, and run.

19
00:01:05.844 --> 00:01:07.055
About fifteen lines.

20
00:01:07.055 --> 00:01:10.204
There's no switch statement and no argument parsing to maintain.

21
00:01:10.204 --> 00:01:12.702
Every command lives in its own small file.

22
00:01:13.402 --> 00:01:16.106
And each command is a plain C# class.

23
00:01:16.106 --> 00:01:17.446
A route attribute names it.

24
00:01:17.446 --> 00:01:21.603
Options are typed properties, so a boolean flag really is a boolean.

25
00:01:21.603 --> 00:01:29.754
The compiler checks it, your IDE autocompletes it, and the restore and build calls go through TimeWarp.Amuru instead of fragile shell strings.

26
00:01:30.454 --> 00:01:31.908
Now here's the free stuff.

27
00:01:31.908 --> 00:01:37.108
Clean, check version, release and self-install aren't written in this repo's dev CLI at all.

28
00:01:37.108 --> 00:01:40.128
They come from the shared Nuru dev CLI endpoints.

29
00:01:40.128 --> 00:01:44.472
Here they're pulled in as source, and every other repo gets them from the NuGet package.

30
00:01:44.472 --> 00:01:49.993
And with AOT switched on, self-install compiles the whole tool into one fast native binary.

31
00:01:50.693 --> 00:01:56.776
Because it's built on TimeWarp.Nuru, the dev CLI inherits the plumbing for free. Help. Version.

32
00:01:56.776 --> 00:01:59.886
Capabilities, with filtering and search.

33
00:01:59.886 --> 00:02:01.273
JSON arguments.

34
00:02:01.973 --> 00:02:03.962
Capabilities is the superpower.

35
00:02:03.962 --> 00:02:07.920
It prints every command, every option, and every type as JSON.

36
00:02:07.920 --> 00:02:13.073
An AI agent reads that contract and knows exactly what it can call. No guessing.

37
00:02:13.073 --> 00:02:14.485
No scraping help text.

38
00:02:15.185 --> 00:02:17.719
Our agents have a skill for exactly this.

39
00:02:17.719 --> 00:02:20.734
Step one, ask dev for its capabilities.

40
00:02:20.734 --> 00:02:21.630
Step two, run the command.

41
00:02:21.630 --> 00:02:28.324
The same tool serves you, CI, and your agents, so nobody keeps a separate set of instructions.

42
00:02:29.024 --> 00:02:32.238
Now, CI. The GitHub workflow is a thin trigger.

43
00:02:32.238 --> 00:02:43.022
It checks out, sets up .NET, logs in to NuGet with short-lived OIDC credentials, and then the real work is one call: dotnet run dev.cs -- workflow.

44
00:02:43.022 --> 00:02:45.045
The build logic lives in C#.

45
00:02:45.045 --> 00:02:47.624
YAML just handles the login and cleanup.

46
00:02:48.324 --> 00:02:50.367
The pipeline itself is C#.

47
00:02:50.367 --> 00:02:55.304
The workflow command reads the GitHub event and picks pull request, merge, or release mode.

48
00:02:55.304 --> 00:02:58.554
Then it calls the clean, build, and test handlers directly.

49
00:02:58.554 --> 00:03:03.083
Your whole CI is code you can read, refactor, and step through in a debugger.

50
00:03:03.783 --> 00:03:05.915
And because it's code, it's testable.

51
00:03:05.915 --> 00:03:10.125
This test pins down that a manual dispatch never publishes by accident.

52
00:03:10.125 --> 00:03:12.919
Try writing a unit test for a bash script.

53
00:03:12.919 --> 00:03:14.702
Here, it's just another test.

54
00:03:15.402 --> 00:03:16.592
So here's the payoff.

55
00:03:16.592 --> 00:03:20.406
One C# tool that runs on Windows, Mac and Linux.

56
00:03:20.406 --> 00:03:23.123
Typed, so mistakes die at compile time.

57
00:03:23.123 --> 00:03:25.203
Testable, like the rest of your code.

58
00:03:25.203 --> 00:03:31.754
And callable by people, pipelines and agents alike. Clone a repo. Type dev. You're home.
