WEBVTT

1
00:00:00.260 --> 00:00:09.200
What's up, everyone? Welcome to Next in Dev. In this episode, I cover a small change to Payload CMS, some AI fluff, and more Railway magic.

2
00:00:09.500 --> 00:00:19.300
This is the first time I've recorded this podcast and haven't had a Payload CMS release to write about. They did release version 3.62.1, but that came with a single bug fix.

3
00:00:19.760 --> 00:00:30.860
The new KV feature was requiring Postgres users to create a new migration when initializing. And that's it for Payload CMS this week. Even Figma doesn't have anything for this week.

4
00:00:31.080 --> 00:00:40.580
As we head into the end of the year, I'm thinking we'll see web dev news slowing down. OpenAI says AI is advancing exponentially. Obvious.

5
00:00:41.370 --> 00:00:50.690
This news reads a bit more like a way to keep us interested in what OpenAI is doing. For example, we see again the claim that AI will soon be able to be autonomous.

6
00:00:51.300 --> 00:01:01.460
On the bright side, this obscure news calls for safety standards. Sounds like something the largest LLM company should be spearheading, right? What does this mean for you, though?

7
00:01:02.000 --> 00:01:15.660
Accelerating AI means more tools, APIs, and evolving workflows. Keep safety in mind as you continue to use AI or integrate it into your products. OpenAI also signed a partnership with AWS.

8
00:01:16.220 --> 00:01:26.480
This partnership gives OpenAI access to key AWS infrastructure. Read that as GPUs. This means that LLMs will be more accessible to us developers.

9
00:01:26.940 --> 00:01:40.310
The level of compute OpenAI receives may change how we figure out things like latency and cost. Railway introduced new enterprise features. The first is Enterprise SSO for centralized authentication.

10
00:01:40.360 --> 00:01:48.780
This is part of their efforts to provide compliant products and features. This news comes with a new landing page, which shows all enterprise features in one place.

11
00:01:49.360 --> 00:01:58.360
This is a marketing page, so it's not anything too sexy. I wrote about Railway's new Magic Config last week. There have been some new updates this week.

12
00:01:58.400 --> 00:02:06.760
The first update is you're now able to select Docker files during deployment. If you have more than one Docker file, you have the option to select any one of them.

13
00:02:07.440 --> 00:02:20.160
As part of Magic Config, environment variables are now auto-detected and pre-filled. Railway made this feature to streamline setup, but you can change anything you need to, of course. An example of this is a secret key.

14
00:02:20.540 --> 00:02:31.240
If your application needs one, Magic Config will set a value that automatically generates a secret key. Pro users now have the ability to use a new bare metal build environment for faster builds.

15
00:02:31.600 --> 00:02:42.240
This feature cuts build latency by removing overhead from virtualization. Free users have been unknowingly beta testing this feature, and hobby plan users are being migrated as we speak.

16
00:02:42.920 --> 00:02:49.480
And why does this matter to developers? Railway continues to focus on enterprise readiness, automation, and speed.

17
00:02:49.660 --> 00:03:01.280
This means teams of all sizes deploying web apps of all sizes get efficiency benefits from Railway's work. But what did I miss? There's so much happening in modern web dev that I'm sure I have missed something.

18
00:03:01.680 --> 00:03:12.700
Depending on where you are listening or reading this, you can share your thoughts either in the comments, or replying to the email, or emailing me at the email that's in the show notes of the podcast.

19
00:03:12.980 --> 00:03:18.560
I want to address your suggestions and may even include them in future podcasts. Thanks for listening. See you next time.