# Ada Talk at Carolina Code Conference

**URL:** https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820
**Category:** Events
**Tags:** spark, ada, gnat, alire
**Created:** [October 12, 2026, 3:04pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820 "2026-10-12T15:04:45Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![pyj](https://forum.ada-lang.io/user_avatar/forum.ada-lang.io/pyj/32/5_2.png) [@pyj](https://forum.ada-lang.io/u/pyj)
#### Post date: [October 12, 2026, 3:04pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/1 "2026-10-12T15:04:45Z")

</div>

I gave my first live talk about Ada at the Carolina Code Conference, “Writing Open Source Ada in 2026.”

> **[Paul Jarrett: Writing Open Source Ada in 2026 (2026) · Carolina Code Conference](https://carolina.codes/speakers/2026/paul-jarrett)**
>
> Paul is a software engineer who started ada-lang.io, and holds a BS in Computer Science from Virginia Tech, and an MS in Computer Science from Georgia…

---

<div class="post-metadata">

### Author: ![cantanima](https://forum.ada-lang.io/user_avatar/forum.ada-lang.io/cantanima/32/121_2.png) [@cantanima](https://forum.ada-lang.io/u/cantanima)
#### Post date: [October 12, 2026, 5:27pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/2 "2026-10-12T17:27:23Z")

</div>

One comment: Ada’s organization at the package level was not unusual at the time. Modula-2, Modula-3, and Oberon do the same thing. M2 and Oberon didn’t have generics, but M3 did, and its implementation was somewhat similar to Ada’s, except that Ada did things for you that M3 didn’t: with M3 you have to manually create a new file to instantiate every generic package. I like M3, but that was a pain.

---

<div class="post-metadata">

### Author: ![OneWingedShark](https://forum.ada-lang.io/user_avatar/forum.ada-lang.io/onewingedshark/32/305_2.png) [@OneWingedShark](https://forum.ada-lang.io/u/OneWingedShark)
#### Post date: [October 12, 2026, 6:07pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/3 "2026-10-12T18:07:48Z")

</div>

Nicely done; I thought that was a pretty good “lite presentation”.

---

<div class="post-metadata">

### Author: ![Irvise](https://forum.ada-lang.io/letter_avatar_proxy/v4/letter/i/7ba0ec/32.png) [@Irvise](https://forum.ada-lang.io/u/Irvise)
#### Post date: [October 12, 2026, 7:14pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/4 "2026-10-12T19:14:49Z")

</div>

Really good talk, nice work!

---

<div class="post-metadata">

### Author: ![pmnw](https://forum.ada-lang.io/letter_avatar_proxy/v4/letter/p/c37758/32.png) [@pmnw](https://forum.ada-lang.io/u/pmnw)
#### Post date: [October 13, 2026, 11:50am UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/5 "2026-10-13T11:50:27Z")

</div>

This was a nice and friendly presentation!

Criticism: too much too fast for an Ada speaker like me.  
I’m convinced Ada presentations should focus on software engineering fundamentals enabled by the type system and packages.  
Urges to also showcase generics, tasks, contracts, or formal verification, need to be resisted.  
These topics (and their Ada syntax) are too dense informationally to make them comprehensible in a quick talk.

---

<div class="post-metadata">

### Author: ![pyj](https://forum.ada-lang.io/user_avatar/forum.ada-lang.io/pyj/32/5_2.png) [@pyj](https://forum.ada-lang.io/u/pyj)
#### Post date: [October 13, 2026, 10:51pm UTC](https://forum.ada-lang.io/t/ada-talk-at-carolina-code-conference/4820/6 "2026-10-13T22:51:33Z")

</div>

> [@pmnw](#):
>
> I’m convinced Ada presentations should focus on software engineering fundamentals enabled by the type system and packages.  
> Urges to also showcase generics, tasks, contracts, or formal verification, need to be resisted.

I covered the parts which impressed me, as someone who has worked in over a dozen languages. Built-in newtypes, nominal pointer types (access types), generic packages and built-in task systems _are_ relatively novel compared to mainstream languages. I also see contracts and formal verification as the future of software engineering, so I couldn’t omit those.

I should have asked for more time, but I tried to hit the points that surprised me the most, and still had to leave things out (e.g. static and dynamic predicates).
