Let's say you want to build something, a birdbath, a computer, like maybe your own freaking house, because you're live in Vancouver and you're sick of a ten thousand percent markup on real estate. Sorry, I got distracted there. Anyway, you wouldn't build any of that stuff without the proper tools, right? I mean, you can't exactly stack a bunch of lumber together and hope to live in it. Well, the same concept is true in software development. I mean, sure, it is possible to completely write your own code from scratch, but it would be an incredibly tedious and time-consuming process for developers to do this every time they came up with a new idea. I mean, imagine having to plant, grow, and harvest your own wheat every time you wanted a delicious slice of raisin toast. So, in a previous episode, we covered APIs, which are pieces of software that one program uses to interface with another, making programming a heck of a lot easier. But what about the front-end interface, the tools that developers actually sit down and use? Well, these often come in the form of a software development kit or SDK. Think of it as a virtual tool, but instead of pliers and a hammer, you'll typically find files called libraries, which are essentially pieces of code that help a program play nicely with whatever platform it's on, such as the libraries in the Windows SDK, which allow programs to make calls to the operating system to get certain functions easily without having to tediously code them manually. Other common SDK tools include visual editors, so that a developer can design and layout graphical elements like buttons and text easily, with tutorials and sample code so that a developer can become familiar with the platform that they're...
Award-winning PDF software
Video instructions and help with filling out and completing Will Form 2220 Developments
