text stringlengths 0 1.49k |
|---|
[177.90 --> 183.74] I forget the names because I'm getting old and it's been a long time. |
[185.84 --> 187.64] I worked with Sri Borda. |
[187.78 --> 190.38] Jeff Lamb was involved in the early days of this. |
[190.38 --> 198.90] So this was really around the DLR and this whole IronPython or the dynamic language runtime |
[198.90 --> 202.32] for .NET, basically. |
[203.06 --> 206.06] But Sri Borda was the team lead at the time. |
[206.22 --> 210.76] And then there was a Jim DeVille involved and a few more people. |
[210.76 --> 218.28] So I worked with IronRuby by writing a book for Manning, which never got published because |
[218.28 --> 222.22] Microsoft canceled the project before the book was finished. |
[224.72 --> 227.48] Or at the same time that the book was finished, really. |
[228.44 --> 235.52] And so then from there, I also started a startup at that point where I was going to do real-time |
[235.52 --> 236.92] social media filtering. |
[236.92 --> 244.60] You can look at today, which probably would be the most similar to IFTTT, because you could |
[244.60 --> 246.24] set up some query parameters. |
[246.58 --> 252.58] And if a Twitter feed or a Facebook feed or whatever social media feed would raise an event |
[252.58 --> 258.34] that matches those query parameters, it would trigger yet another webhook or some other event |
[258.34 --> 261.12] that you could then react to. |
[262.08 --> 267.18] To do so, I had to analyze the Twitter files and so on. |
[267.42 --> 270.10] And Ruby didn't get me far enough. |
[270.22 --> 272.70] So I started looking for something else and I found Scala. |
[274.04 --> 278.52] Scala at that time only had Lyft as a web framework. |
[279.04 --> 282.16] And Lyft, people said it was very interesting. |
[282.30 --> 287.74] But from my point of view, it was a web framework that conflated all kinds of responsibilities. |
[288.34 --> 294.90] And so I started looking for something that looked like Sinatra, because Sinatra was as |
[294.90 --> 300.42] concise as I could think of for developing web apps or APIs. |
[301.24 --> 307.30] And so there was a proof of concept at the time, which had just been renamed to Scala. |
[307.48 --> 308.74] And so I started contributing. |
[309.34 --> 314.34] And after a while, I was one of the main contributors on that open source project. |
[314.34 --> 316.18] It was fairly successful. |
[316.74 --> 319.34] But Scala itself has problems. |
[320.02 --> 320.92] The language is good. |
[321.48 --> 323.54] The community is very divided. |
[325.70 --> 333.80] And if you work with it on a team, it's not very conducive, in my opinion, |
[334.40 --> 339.66] to have people with very different backgrounds come together and get up to speed very quickly. |
[339.66 --> 343.70] And so I started looking at Go to find out. |
[344.66 --> 349.82] Or I wanted to know if Go would actually deliver on that promise, that you can have a team, |
[349.92 --> 351.94] you can get your team to expand fairly quickly. |
[353.22 --> 360.30] And people shouldn't have to have weeks of ramp-up time just to learn how to leverage the language |
[360.30 --> 361.16] to their advantage. |
[362.00 --> 363.90] And so far, it's been delivering. |
[363.90 --> 366.68] And so that got me here. |
[367.66 --> 372.22] In the meantime, through Scala, I got into Swagger because we have to document APIs. |
[372.76 --> 376.14] The company that invented Swagger, they hired me. |
[376.28 --> 381.18] And so that's how I got deeper and deeper into that entire Swagger and open API story. |
[383.08 --> 385.60] And when I switched to Go, there was nothing there. |
[385.60 --> 390.74] And so I figured people in Go also write lots of APIs. |
[390.98 --> 396.32] So they should have a way to document them and use them so that other people can generate |
[396.32 --> 398.22] clients for it in whatever language. |
[398.94 --> 400.70] And so that's how I got to write in Go Swagger. |
[401.16 --> 404.22] So let's back up just a second, too. |
[404.34 --> 410.48] And let's give a little bit of a rundown on what Swagger is for anybody who may not have |
[410.48 --> 411.66] used it or familiar with it. |
[411.66 --> 420.82] So Swagger is currently known as OpenAPI, I guess, but it started its name as Swagger. |
[421.72 --> 427.16] The reason it was named Swagger, because the only alternative we had was something that |
[427.16 --> 429.76] is the acronym of WADL. |
[429.90 --> 433.06] So in the office, people would go, why Waddle if you can Swagger? |
[433.50 --> 435.22] And that's how the name came to be. |
[435.22 --> 446.80] So from there, everybody who writes an API ends up having the same problems, right? |
[446.86 --> 452.24] So now you have a bunch of clients who are talking to your API. |
[452.74 --> 455.44] You still want to be able to evolve your API over time. |
[456.08 --> 457.78] You bring new people on board. |
[458.60 --> 460.28] They don't know how to use your API. |
[460.28 --> 464.00] They don't know what the inputs are, what the outputs are, especially if you're writing |
[464.00 --> 467.60] a dynamic language kind of API. |
[468.70 --> 475.46] So to formalize those expectations between the boundaries that existed within our teams, |
[476.06 --> 482.94] we came up, and many people like us have come up with a format to describe what goes into |
[482.94 --> 483.38] the API. |
[483.38 --> 489.42] So essentially, it's just a schema for your input and output parameters that captures |
[489.42 --> 493.06] what some people look at as a contract for your API. |
[493.96 --> 499.60] Once you have a machine-readable version of something like that, you can take it in many |
[499.60 --> 500.44] different forms. |
[500.68 --> 506.92] So the very first thing that we then did was make a UI for it, because now you have this |
[506.92 --> 507.26] API. |
[507.66 --> 512.90] If you run the UI, you point it to this description, which is hosted with your API. |
[513.38 --> 521.04] So you can show nice documentation, especially if you add some markdown or some richer form |
[521.04 --> 525.04] of documentation, and that documentation lives with your code. |
[525.70 --> 532.56] So that's important, so that for every version of your code, you actually have a complete form |
[532.56 --> 536.26] of documentation for the API that that application exposes. |
[536.26 --> 544.80] From there, obviously, machine-readable makes it also that it's easy to generate clients for |
[544.80 --> 549.76] your API, because you now know exactly what goes in and out of the API, so you can generate |
[549.76 --> 550.52] a client for it. |
[551.16 --> 556.92] If you then take that a little bit further, and you make the API specification easy to define, |
[556.92 --> 564.70] from there, you could also look at it, oh, now, why don't I do contract first, and I start |
[564.70 --> 565.68] generating a server? |
[566.66 --> 573.10] And here it goes particularly strong, because it allows for these broken up definitions in |
[573.10 --> 574.40] many files and so on. |
[575.10 --> 581.34] So I took this from what we've tried with Scala, take an API specification, and just generate |
[581.34 --> 583.82] servers for it that implement the entire specification. |
[583.82 --> 590.94] So you don't have to really think about all of the ceremony, but just start writing about |
[590.94 --> 595.90] the things you care about, the things that happen after all of the common code. |
[596.78 --> 599.76] And so that's a rundown of what Swagger is. |
[600.26 --> 605.94] Of course, there are marketplaces now where you can look at all of the APIs other companies |
[605.94 --> 606.50] expose. |
[607.06 --> 613.68] And so the bigger dream here is if every API exposes a Swagger spec, then you never have to |
[613.68 --> 615.38] download a client SDK anymore. |
[615.76 --> 617.44] You can just always generate one. |
[618.46 --> 624.64] Yeah, one of my favorite things, too, is whenever you use a new API for something, you're always |
[624.64 --> 627.14] kind of poking around at it and trying things out. |
[627.30 --> 633.38] And the fact that you can just go into the Swagger UI and kind of play with the example requests |
[633.38 --> 637.80] and submit them and see how they return and things like that is extremely valuable. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.