You're technical enough to use Docs-as-Code
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfBQHswpnpEVf5A1G-bOTivn-pBYE6khZxl9a6IpMUADm9hyR6P1FQsn6n_xdir0j95cD-0gGPpdL874MUyRPOPyUONaOmnF4Y_j9Wexw2a7d1PQ1GNQgQ7uuqQrKpu2BDhvQM3ZKxWp7SMFrdHXS0J-kzKbG9LO00GuS6TPE0dU0kK-TWvbwwSnrB9H0/s320/brain_sides.png)
During my interview for my last Technical Writer position, I was asked, “Do you have any experience with Docs-as-Code ?” The company used it as its documentation solution, so it would’ve been nice if I had used it before. I had not. In fact, I had never heard of it. Apparently, I was charming enough to get the gig anyway, but I was nervous about my ability to learn the workflow quickly despite having been a Technical Writer for two years at that point. It turned out my concerns were unfounded, and not only did I flourish using Docs-as-Code, but for the past year and a half, I have made it my preferred documentation option. If you find yourself unsure of having enough technical prowess to wrap your head around Docs-as-Code, I will reassure you with this: if you’re the type of person who would peruse a page on this subject, you’re more than qualified to use Docs-as-Code. You’re inherently somewhat technical Chances are, since you’re here, you have some interest in what’s discussed on thi...