I didn’t plan to build search features, especially with the Google Books API for my Books & Banter Rails project, but…laziness.
Laziness is a mother of invention—along with her sister, necessity, of course.
Why conjure up a bunch of book data to build a library, when you can just harvest it from Google Books?
In a previous blog, I went over the basic setup for using the Google Books API . This time, I added a check to see if the data was valid before instantiating a new book instance:
books_array.map do |book_hash| book_assignment_hash =…
patients/edit.erbis built to show the patient’s current information when you open the edit form. (The
<input>field is set to show the current values saved in the database for the patient’s attributes before they’ve been edited and updated).
What API do you choose to work with if you spend all your time reading old books and looking for “scholarly references” online? The GoogleBooks API, of course!
For my first CLI project, I decided to look for books in my new field of interest, “Object-Oriented Programming”(rather than an old one).
With this program, I fetched the top 40 most relevant books (according to the Google search engine) on “Object-Oriented Computer Programming” from the Google Books API.
My background is in teaching people to read Classical Greek and Latin (hence the title).
There’s still a lot of work to be done in the digital humanities to make ancient texts available, and I’ve done some work in that area—but, I get really excited when I think about all of the new avenues for creative design that software engineering opens up. I’m particularly interested in designing applications that have real-world use. I also just really like learning new languages and talking about them with other people.
In short, I’m looking forward to moving into the 21st century and finding a new path (inveniens novam viam) in programming!
I’m very excited to start a new journey in programming. I already love Ruby—the language and infrastructure. I cannot wait to learn JS, React, and Redux.