Xano is a no-code backend platform that allows you to construct methods with visible logic, APIs, and modular AI parts. Take a look at their tutorials on YouTube.
Join with Prakash on LinkedIn.
Consumer Bruno Bronosky is the winner of at the moment’s shoutout and a Stellar Reply badge for his or her reply to How do I parse command line arguments in Bash?.
TRANSCRIPT
[Intro Music]
Ryan Donovan: Hiya everybody, and welcome to the Stack Overflow Podcast, a spot to speak all issues software program and expertise. I am Ryan Donovan, and at the moment we’re speaking concerning the points that can come up with all these corporations making an attempt to give you this common front-end interface. And people points, in fact, shall be on the back-end. My visitor at the moment is Prakash Chandran, CEO and Co-Founding father of Xano, who shall be speaking about this. So, welcome to the present, Prakash.
Prakash Chandran: Ryan, it is nice to be right here. Thanks for having me.
Ryan Donovan: Yeah, in fact. Earlier than we get into our subject at the moment, I wish to get to know you slightly bit. How did you get into software program and expertise?
Prakash Chandran: Yeah. I’ve spent most of my life in expertise beginning as a Doom 2 participant earlier than actually the web existed, connecting over BBS. Certain. So, I’ve all the time type of been of that faculty, of constructing your personal pc, adjusting your modem bit fee, and all that type of stuff. However notably, I spent virtually a decade at Google. I used to be on the UX product aspect. I used to be on the design lead for Google Calendar, after which I led the design and analysis workforce for Google for enterprise and for training.
Ryan Donovan: It is fascinating. So, you spent a variety of time doing front-end work.
Prakash Chandran: Completely. Numerous time doing front-end work. And I additionally, after I left Google, I did a startup of my very own the place I mainly was, I suppose, the front-end engineer on the time. I used the Imply Stack. Stack Overflow performed a reasonably important half in me truly studying and understanding what the heck I used to be doing. And I additionally, all through all of it, I used to be with my greatest pal, who’s presently our Co-Founder CTO, who was on the back-end aspect, and he was the lead DevOps on Google Images. It truly began on with the server on his desk, and he labored on Borg earlier than it grew to become Kubernetes. So, I received publicity to that as properly, though I am extra of a UX and front-end man.
Ryan Donovan: So, in your time as a front-end UX engineer, did you ever write front-end UX checks that your back-end could not money?
Prakash Chandran: Sure, on a regular basis, truly. I really feel like that’s only a ceremony of passage for the front-end engineer. ‘Trigger I believe there’s this second the place you are like, ‘oh, I can simply do every thing on the front-end, and I can simply, you recognize, course of no matter workload I would like.’ And I believe that you simply run into partitions fairly shortly. And I believe that you simply even see corporations constructed on doing a variety of heavy processing on the front-end that begin to fall down below load, and you are like, ‘okay, that is what occurs once you let the front-end engineers free for too lengthy.’
Ryan Donovan: Proper, proper, proper. And clearly, I believe you talked about a variety of occasions the place the issue with a variety of that load is simply loading up the front-end with a variety of client-sized JavaScript.
Prakash Chandran: Yeah.
Ryan Donovan: Is there additionally a back-end downside with– everyone talks about Server-Facet Rendering as the way in which to resolve that downside. Does which have points too?
Prakash Chandran: Yeah. Within the Server-Facet Rendering world, 100%. I believe that the way in which that we have a look at it’s that the heaviest workload clearly must be delegated off to the back-end, and your whole heavy, your online business logic processing ought to occur there. And so, what we see typically is that, even with Server-Facet Rendering, if a variety of the workload is not handed in a, in an applicable approach to the back-end, that you simply’re inevitably nonetheless gonna hit partitions and issues, particularly once you begin to hit scale and go to manufacturing. And so, we type of see this quite a bit, even in some merchandise in manufacturing.
Ryan Donovan: Yeah. And the front-end dreamers within the generative AI world have give you this new thought of a common interface, proper? I’ve seen demos for it. I believe I noticed a Gemini demo the place the front-end is rendered on the fly, created on the fly, based mostly on what you wanted to do.
Prakash Chandran: Yeah.
Ryan Donovan: That looks as if it might have a pair issues.
Prakash Chandran: Yeah. You recognize, I believe this concept of ‘ephemeral interfaces’ and non permanent interfaces—do not get me mistaken—is admittedly fascinating and thrilling. I believe that with the velocity that AI can construct, it is solely pure to attract the conclusion that sure, that is the world we’re gonna go into. Possibly there’s gonna be purpose-built functions that an agent may construct. Nonetheless, I believe it’s a false impression to suppose that there is not a back-end element to that, and oftentimes, what’s being rendered is barely as highly effective because the back-end that’s serving to to render it, or the APIs. It isn’t that I do not suppose that we’ll get there. I simply suppose that this is not similar to a front-end developer operating off and simply creating one thing with out actually pondering by means of the complexities of what’s going to be introduced, who’s going to be consuming it, and the complexities across the tooling that shall be referred to as. After which there is a permissioning factor. There’s all of those totally different dynamics that they should suppose by means of on this ephemeral app creation world.
Ryan Donovan: Proper? Yeah. I bear in mind in a earlier job, [I] ended up working with a variety of client-side integrations, proper? And one of many product of us gave an API that wasn’t prepared for client-side integration. So, I ended up having to scramble, work out what was the load they might bear if everyone’s prepared for it. And I really feel like this common interface factor is like that, however for everyone. All people is now a sudden consumer of the APIs, proper?
Prakash Chandran: I additionally suppose that expectations from customers by way of time to worth have drastically shrunk. So, it is not sufficient to say we’ll simply put a loading indicator whereas this API finishes processing. You actually should suppose by means of, okay, relying on what’s being requested, they may very well be ready there some time, they usually might suppose that issues are simply basically damaged. And so, I think about, in your use case, that you simply in all probability bumped into that the place it was once more, writing a examine that the back-end cannot money; and I believe as we begin to open it up, particularly Chat-GPT apps, SDK, individuals experimenting with that, they’re gonna be taught in a short time that, okay, Chat-GPT and their workforce have optimized the front-end in such a approach to the place they’re making an attempt to get the consumer the reply they want as quick as potential. Even when it is non permanent to say, ‘ hey, pondering longer for a greater reply, however you possibly can click on to skip this.’ As different third-party apps get built-in into that platform ecosystem. They’ve to consider that very same expectation from that very same consumer that expects a response like this.
Ryan Donovan: Proper. It looks as if it is counting on a number of back-ends, proper? There’s the generative AI back-end that generates the UI, after which all of the items which may be taken from third-party APIs – this looks as if a nightmare to determine. The ready, such as you stated, the loading bar.
Prakash Chandran: 100%, and it is also simply [that] there’s so many unknowns. Even simply the quantity of load site visitors, what number of occasions an API may be referred to as, setting the proper expectation for the consumer, all of these issues. I believe coming down, once more, from my background, actually pondering by means of the consumer expertise a part of the way you manifest the front-end to the consumer in these new platforms goes to be in all probability crucial factor. It is not sufficient simply to type of current them one thing after which have them ready round. It’s a must to take into consideration, to your level, how are you going to orchestrate these totally different APIs to work collectively in a means that it serves the consumer in that new modality to that expectation of an prompt response.
Ryan Donovan: Yeah. Are there middleman methods we are able to do that as an alternative of absolutely producing a complete interface? Can we use it for on-the-fly display dimension rendering, or doing little items that generative AI might do higher?
Prakash Chandran: Yeah, I believe that is truly– I imply, you stated it greatest. It is like beginning extra on the atomic or componentized degree is 100% the proper approach to go. Like, actually take into consideration the enterprise worth that, on the finish of the day, software program is a mechanism to floor enterprise, or enterprise worth, to the shopper. So, what’s the atomic unit of that enterprise worth? If it’s the reserving.com instance, for instance, that was proven in that demo, the atomic unit is likely to be that card round, ‘ right here is the place we predict you must keep.’ You needn’t render a complete front-end expertise, like an online expertise that somebody may go to; it is simply the cardboard that you’ve got one of the best sense is the reply that they are in search of, after which give them pathways to say, ‘okay, from this atomic element, how do I then begin to scope out and be taught slightly bit extra?’ So, that’s the expertise piece that I am speaking to and also you’re referring to. Simply type of a modular means of constructing.
Ryan Donovan: Yeah, and it looks as if when you have these items already. Possibly rendering or creating them on the fly may not be the way in which. I’ve talked to a variety of of us speaking about componentizing micro front-ends, even like caching parts for generative AI.
Prakash Chandran: Sure, 100%. I believe earlier than we get to this world the place every thing is simply generated for you on the fly, it is extra going to be a really considerate experiment round: what are the atomic models of the front-end I wish to current? How is that going to interface with the APIs that energy them, and the way can, once more, from a efficiency standpoint, I cache and present them to the consumer shortly? And to be sincere, I do not actually know what the bridge seems to be like from that world to, hastily, every thing is simply being generated as you want it. It is simply, I believe the issue set of issues to resolve is only a lot larger than individuals truly understand.
Ryan Donovan: Proper, proper, proper. So, such as you stated, there may be already a form of downside set of the front-end directing with the back-end, proper? What’s the present issues with the front-end back-end connection that also should be solved?
Prakash Chandran: I believe that even at the moment, when individuals are constructing with Xano, for instance, simply understanding how one can get a full learn on all of what exists within the back-end, whether or not or not it’s leveraging an SDK, or a swagger specification. That is one piece, simply realizing what’s the world of issues that exist with a purpose to energy a front-end, however realizing how one can prioritize them, how one can organize them, which API must be used when for which element, is sort of a special downside. And so, the purpose I am saying is it is likely to be simple to generate, at the moment, a full-stack software, and the front-end understands what is feasible within the back-end, however doing so on this new world that we’re transferring into, I believe is one thing that is a matter that shall be exhausting to resolve.
Ryan Donovan: Yeah. I imply, discovery, I believe, continues to be a tough downside for microservices, after which all the opposite issues. And I believe it is solely gonna worsen as brokers get thrown within the combine. Proper?
Prakash Chandran: 100%. We have already got an observability downside with brokers as it’s. So, by way of okay, how are they processing this? How do I inflect and say, look, that is how try to be rendering issues throughout a extra advanced software, with extra advanced front-end dynamics? I believe that’s the reason it is like this componentized-level that we’re speaking about, combined with individuals are all speaking about spec-driven design, however the spec round that element which you can mainly co-collaborate, or you possibly can type of give intention to the agent to say, ‘ that is the way it’s meant to make use of, and the APIs, and the order, et cetera,’ might be gonna be the easiest way to method it.
Ryan Donovan: So, how do you see the back-end having the change to even method a few of this new downside area we’re speaking about?
Prakash Chandran: Yeah. I type of talked about the spec-driven design nature piece of it. I believe that particularly instruments like ours are gonna should be extra beholden to specs, and determining how we are able to type of make {that a} first-class citizen by way of the way in which that back-ends are constructed and created. And interface with the front-end, I believe that is an issue that we’re, proper now, a device the place you possibly can construct enterprise logic. You’ll be able to have AI help you to construct that enterprise logic. It creates the SDK, creates a swagger documentation, however that is not sufficient anymore. When you concentrate on the world that we’re transferring into the place it’s these modular componentized models and the state of the front-end, regardless of the Lovables, and Bolts, et cetera, it is being commoditized, and it’ll change. So, in that world, what’s the nature of your API? Is CRUD going to be sufficient? How do you mainly limit scope on what data will get handed, when it will get handed in a world the place context turns into essential? So, I believe it begins with the spec. And serving to customers suppose by means of, or the individuals which might be creating the back-end, suppose by means of how an agent may suppose and course of, after which rebuilding, and scoping, and narrowing your APIs accordingly.
Ryan Donovan: Proper. Is there an area for a world the place the back-end can be generated on the fly, or is that similar to taking part in with fireplace?
Prakash Chandran: I imply, it is taking place at the moment. Yeah. However I believe particularly with the back-end, until you’re an engineer with years and years of expertise, and you’ve got a robust tie and belief to the mannequin that you have skilled and prompted, and it remembers precisely the way you construct, you’re taking part in with fireplace. As a result of typically, when the AI creates one thing, individuals are like, ‘it really works.’ So, that is that. However for those who do not perceive it, you do not personal it. Proper? And I believe that, particularly with the back-end, having the ability to perceive it’s important as a result of not solely is it the engine for your online business worth, however there is a governance piece, there is a safety piece, there’s so many issues that whole corporations are constructed on to make it possible for your online business logic is safe, it is dependable, it is scalable, it is the entire issues. And so, having an AI simply generate it, possibly we get there. You recognize, possibly that is the case, however I believe we’re not in a world the place we are able to absolutely belief it. The front-end is slightly bit totally different to type out. And even then, you type of should, particularly on this componentized world that we’re speaking about, I believe you must be extra prescriptive and opinionated about how the front-end will get generated. However the back-end, particularly transferring into this agentic period, I believe, goes to be crucial to actually perceive and supervise.
Ryan Donovan: Yeah, yeah. They each have dangers, they usually each have totally different dangers. Just like the front-end, I really feel is, you recognize, a frustration, a model danger, proper?
Prakash Chandran: Sure.
Ryan Donovan: The back-end is sort of a information danger. I wrote one thing years in the past. Clearly, Stack Overflow has been doing firm copy and paste code for ages. And there was a narrative round probably the most copied and pasted piece of code moving into manufacturing methods, and enterprise corporations, and having huge safety flaws in it.
Prakash Chandran: Yeah.
Ryan Donovan: If you happen to do not perceive your code and also you’re implementing it, it is not your code, you are simply borrowing it.
Prakash Chandran: Completely. I believe the one praise I’ll give the Stack Overflow is, the factor I cherished about it on the time after I was speaking about it, is mostly there was a threaded dialogue. It all the time began with the issue you had been making an attempt to resolve. There was a threaded dialogue of experiments, and then you definitely received to the reply. So, I believe that there was naturally extra context that I had as a consumer, versus an AI simply spitting one thing out to me. Proper? So, that is simply the very first thing that I believe that Stack Overflow did very well. However now that is misplaced, and we get to that duplicate and paste code, you are proper. It is copying one thing that you simply simply do not perceive what the ramifications are, and particularly once you discuss concerning the software program growth lifecycle, and type of SRE-type issues going into manufacturing. AI is not skilled on production-grade stuff, you recognize? And due to that, you must be very cautious. Not every thing, in fact, that is being shipped must be inspected on this means. But when you’ll manufacturing and also you’re making an attempt to supply enterprise worth, you must perceive how AI got here up with the reply that it is providing you with. And you’ve got to have the ability to examine for those who count on it to carry out securely and scalably in manufacturing.
Ryan Donovan: Yeah. I believe, I fear that, you recognize, as AI is so quick at placing out code that human engineers shall be slightly overwhelmed, and I already see individuals developing with, you recognize, AI code evaluate instruments.
Prakash Chandran: How do you see that by way of you requested me the type of the black field AI producing the back-end? How do you see that entering into a world the place we are going to truly begin to undertake it?
Ryan Donovan: I imply, I believe within the subsequent couple years we’re gonna see some vital corporations eat some filth and be taught some classes, and people classes will propagate down. However with any new expertise, this can be a highly effective expertise. There’s gonna be some ache, proper?
Prakash Chandran: 100%. And I believe that is why you see this shift of all the thrill round all these vibe coding instruments, the artwork of the potential, the hype cycle round, ‘oh my gosh, engineers are useless.’ To the opposite aspect of the spectrum—the enterprise organizations being slightly bit extra cautious and measured as a result of there may be a lot in danger to introduce one thing. And I believe those that type of enter into it headfirst with out pondering by means of all of those dynamics, there’s gonna be a problem. Nevertheless it’s so exhausting with AI as a result of I really feel like you must be a pupil of the area, you must be experimenting, you must be making an attempt it, however you could have to take action in a measured means. The foundations round SRE, and kinda the production-grade software program ideas nonetheless stand. That is not gonna go away.
Ryan Donovan: Yeah. I get a good quantity of pushback from neighborhood members each time I discuss AI. You recognize, a variety of ’em say AI is being pushed too quick. It is being pushed too exhausting. Corporations are forcing engineers to make use of extra AI. As an organization who’s constructing AI into your product, do you agree with that, or do you could have a special take?
Prakash Chandran: I believe it is exhausting. I am gonna provide the sincere reality. I believe we’re transferring possibly slightly too gradual, however I believe we’re virtually transferring on the velocity that we must be. I do not know if that is smart, however I’ve seen my contemporaries go full bore, pressure their engineering groups to leverage AI, monitor their efficiencies, and type of get to the purpose the place, yeah, their productiveness goes up, however the understanding of the output goes down. And individuals are sacrificing ability growth for velocity. And I believe on the finish of the day, it’ll trigger extra heartache to return to audit, and to repair what you mainly simply sped as much as create. And so, we have now been very cautious with our personal engineers round how we’re adopting it for some issues, particularly inside instruments, which I believe is an effective place to begin, that is not so mission-critical. Yeah. Experiment away and transfer shortly. I believe in terms of the issues that we ship to manufacturing, we’re rather more measured. I believe it has been fantastic to have the ability to create, to point out the artwork of the potential, in a short time, just like the POC. However then our engineers type of take over, after which construct it in the way in which that the remainder of our code base has been constructed. So, I believe that is in all probability– I am not saying that is the proper method, I am simply saying that is our method.
Ryan Donovan: Yeah, simply cautious in direction of manufacturing. Are there different controls which you can placed on the AI code? Do you restrict the quantity or the function of AI code?
Prakash Chandran: Yeah, I believe once more, actually– so, there’s type of a limiter in that we have been utilizing it for extra inside instruments, or issues which might be type of much less enterprise important. So, simply by nature, we’re solely leveraging it for these varieties of issues. We are also having type of probably the most seasoned engineers use it, versus a junior engineer that may, you recognize, go slightly bit loopy and create an excessive amount of. So, the senior engineers, I believe, are capable of work or co-create with it in a way more opinionated means. We actually have not gotten to the half the place we’re creating brokers to do exams, and safety checks, and people issues. That’s one thing that is being mentioned internally. However for proper now, it is similar to, who’s utilizing it and what we’re utilizing it for are the filters that we have now on it.
Ryan Donovan: Yeah. Do you pressure your junior engineers to write down extra code?
Prakash Chandran: Sure. Yeah, as a result of I believe on the finish of the day, it is that ability growth velocity piece. Folks want to have the ability to be taught. And I believe that there is a fantastic function that AI performs in literacy. And you may assist sharpen your skills, however to have it simply generate for you blindly in a code that you have not written your self, I believe it is a hazard– once more, you possibly can’t perceive. If you happen to do not perceive it, you do not personal it. So, we’re forcing slightly bit extra of, ‘ hey, you should write this.’ Yeah, certain, use it for efficiencies for the boilerplate stuff that we all know you understand how to make use of. However exterior of that, I believe that is the proper approach to method it. Now, once more, that opinion isn’t shared by everybody. I believe lots of people are simply pushing it quite a bit tougher, quite a bit quicker, however we have nonetheless been capable of transfer fairly shortly, leveraging it for the components that I simply mentioned.
Ryan Donovan: Yeah, I typically discover that anyone who’s in an engineering function or engineering group has a extra cautious method to it. They’re like, ‘there’s cool stuff happening. Little distance.’ And we discovered that in our final survey that the extra that individuals use AI, the much less they type of belief it. Which I believe is an effective factor.
Prakash Chandran: Yeah. I imply, finally you must put your model on it. We had somebody internally that was in operations and would simply mainly be like, ‘okay, that is what ChatGPT stated.’ And she or he would say that over, and similar to copy and paste.
Ryan Donovan: Proper.
Prakash Chandran: And I used to be like, you recognize what? I do not like. I do not actually wanna know what ChatGPT says, proper? I employed you for you and your skills, and I would like you to be like, I do not thoughts that you simply use ChatGPT to assist sharpen and make clear your ideas, however I would like your ideas. Proper? And I believe that that is the chance that we have now round trusting it for an excessive amount of on the finish of the day. You’ve got gotta personal it. It will possibly aid you for certain, and it could aid you transfer quicker, however I believe that is, a minimum of as a CEO of the corporate, I would like the particular person, the person who I spent a variety of time recruiting, I would like their skills. Proper? And leverage AI to type of transfer quicker, however on the finish of the day, you gotta make it your personal.
Ryan Donovan: Proper. And I believe that is pathway ahead for individuals type of frightened about AI taking their jobs. It is you gotta use it as a device. It’s a must to deliver one thing your self.
Prakash Chandran: 100%. AI is admittedly only a device and I believe, look, it is clearly having impression the place it’ll take some issues like first-line assist, for certain. That is a type of issues that AI can deal with very well, get actually excessive CSAT scores. However the those who had been in these roles must be upskilling, proper? They need to be making themselves extra AI-native to deliver their very own persona, and skillset, and artistic problem-solving to then immediate and add worth someplace else within the group.
Ryan Donovan: I believe there’s additionally an fascinating comparability right here in the necessity to perceive it, personal it for the front-end engineers versus the back-end engineers, proper?
Prakash Chandran: Sure.
Ryan Donovan: If you happen to do not perceive how the back-end works, you are not gonna be pretty much as good of a front-end engineer.
Prakash Chandran: I’d undoubtedly agree with that. I believe that it goes again to– I believe you stated it very well to start with round writing checks that your back-end cannot money, and no pun meant there, however yeah. It is one in every of this stuff the place I believe front-end engineers must have a reasonably intimate understanding round… if they don’t seem to be those which might be, you recognize, clearly creating the back-end code, that is effective, however they should have a reasonably intimate understanding of the way it works, what they’ll count on out of it, and it must be collaborative with the engineers which might be writing it; as a result of that’s, holistically, I believe what’s going to create one of the best, on the finish of the day, we care concerning the consumer expertise. Proper? It is a means to an finish. So, how do you obtain that? The front-end builders are the guardians of that, proper? And with a purpose to produce the proper expertise, it is gotta be snappy. Proper? All this trickery that we’re doing within the back-end actually is to provide the consumer the reply like this, that is actually all we’re doing proper? And plenty of or tens of millions of customers concurrently. So, how will we try this? And that actually begins on the front-end.
Ryan Donovan: Yeah. So, for front-end builders nonetheless making their front-ends by hand, what would you suggest they do to grasp the back-end wants higher?
Prakash Chandran: I do know that is type of slightly shallow, however I will suggest you possibly can leverage a device like Xano, as a result of it’s a low-code back-end that abstracts away a variety of the syntax and will get into the primitives. Like, you perceive variables, loops, conditionals, et cetera. I believe that if you’re not conversant in the back-end, that it could aid you get extra acquainted simply in constructing your self, and visualizing the enterprise logic. Even exterior of a device like Xano, I believe now greater than ever, it is potential for a front-end engineer to change into back-end literate, proper? I believe with AI, with among the frameworks which might be on the market, I believe it is essential to begin constructing. And I believe much more importantly, begin to discuss to back-end engineers, or construct a relationship with them round what it means to construct to manufacturing grade and to scale. What are among the downside units that you should be eager about? How are you eager about constructing at scale? How do they consider constructing at scale? Study issues like, you recognize, caching, indexing, all of this stuff that I believe are essential ability units to have. Do not simply follow your little area of creating a widget on a web page. Actually perceive the total expertise and the total life cycle of the request.
Ryan Donovan: So, how are you and your workforce at Xano eager about evolving the instruments for the back-end for the long run?
Prakash Chandran: For us, we imagine the long run IDE or Canvas for back-end creation is combined, which means that we have now– vibe coding proper now could be thought of, ‘hey, this viewers of like experimenters,’ however actually it’s actually a modality round immediate response. And we predict the IDE, similar to a VS code, will all the time have a copilot element to get began. We imagine it ought to have a code element, clearly. We launched lately this DSL Xano script. And we additionally imagine that there must be a visible element, as a result of the visible a part of what AI generates is the easiest way to type of see what’s taking place, and the way methods are created, and how one can observe issues. So, this IDE of the long run, by way of back-end create– or just like the prettier management airplane, I will simply name it. That provides you extra of that management I believe is what we’re constructing in direction of. So, even if you’re constructing a full-stack software and also you need management, you do not have to grasp a cloud console. It must be extra accessible. There’s the Terraform piece, all the way in which to clicking buttons in your cloud console, however there’s someplace within the center, and I believe we wanna be that center for this subsequent technology of builders. You recognize, taking it again to the place we began round these new varieties of, I suppose, common interfaces, and the way forward for front-end growth, issues are altering, and issues will change. And the way in which that we as customers devour data – it is already modified, proper? So, as front-end builders and builders, actually once you suppose by means of these modalities of the way you current issues to customers, actually suppose by means of the total expertise, which suggests entrance to the again. And I believe you may need to suppose and alter your paradigm round the way you rearchitect the front-end to make it performant, to make it match into these new modalities that customers are looking for to have their experiences, and that clearly additionally comes with being very conscious of how the back-end is serving up all of that information that powers that have.
Ryan Donovan: All proper. It’s that point of the present the place we shoutout anyone who got here onto Stack Overflow, dropped slightly data, shared some curiosity, and earned themselves a badge. So, congrats at the moment to the stellar reply winner, Bruno Bronosky, who dropped a solution that was so good, it was saved by 100 customers. And so they dropped it on ‘How do I parse command line arguments in Bash?’ I am certain there are many individuals who have that problem. Prakash, you too.
Prakash Chandran: Sure. Good, Bruno. I will should look that up.
Ryan Donovan: Yeah. It will be within the present notes for those who’re curious.
Prakash Chandran: All proper. Incredible.
Ryan Donovan: I am Ryan Donovan. I host the podcast, edit the weblog right here at Stack Overflow. In case you have feedback, issues matters to cowl, please e-mail me at podcast@stackoverflow.com. And for those who wanna attain out to me straight, yow will discover me on LinkedIn.
Prakash Chandran: Ryan, actually completely happy to have been right here at the moment. Thanks a lot for taking the time. My identify’s Prakash. I’m the Co-Founder, CEO of Xano.com. You’ll be able to go to us@Xano.com. Additionally, examine us out on LinkedIn. We’ve a variety of tutorials on YouTube. Simply type of in every single place that you’d count on us to be. Stay up for seeing you on the market.
Ryan Donovan: All proper. Thanks for listening, everybody, and we’ll discuss to you subsequent time.
