Toolmaking Predilection

So the day before yesterday I started working on Claire, it's something new in the programming world that should cause programmers to make less bugs, you can find more about it here.

Today, I started thinking about how I'm going to manage my time to work on both Claire and Deviyo, then only I realized that, the reason I got the idea in the first place is because I had problems with Deviyo, I started creating Claire to make developing Deviyo easier, suddenly, something I read in Dreaming in Code came to my mind, here it is:

In software management, coordination is not an afterthought or an ancillary matter; it is the heart of the work, and deciding what tools and methods to use can make or break a project. But getting sidetracked in managing those tools is a patent temptation. When the cry of "Let's build it ourselves!" arises, geeks are all too happy to rally and cheer. A celebrated (and perhaps apocryphal) bit of graffiti from MIT captures this: "I would rather write programs to help me write programs than write programs." Similarly, there is a saying attributed to Abraham Lincoln: "Give me six hours to chop down a tree, and I will spend the first four sharpening the axe." This principle, which found its way into the business advise manual The 7 Habits of Highly Effective People, appeals to every programmer's passion for toolmaking. But if it becomes an end in itself, it can drive the best-organized projects into a ditch.

I don't know what to say, that book is amazing! Everything it mentions seams to be true, I'm so happy I bought it, it's the only book I bought, usually I either borrow books or get free e-books from the Internet and print them.

Falling in Love with Programming

The other day I was reading Dreaming in Code, it's a book that talks about software development and why we still have bugs after more than half a decade since the invention of computers, when I found a saying by Jaron Lanier that I've been thinking about since I learned about OOP, here's what he said "We start off writing little programs--'Hello World,' or whatever it might be. Everyone has a wonderful experience. They start to love computers. They've done some little thing that's just marvelous. How do you get over that first love? It sets the course for the rest of your career. And yet, as you scale up, everything just degenerates."

It's true, I started programming when I was 8! I started with BASIC, just writing sentences that are executed one after the other from top to bottom. Then I was introduced to VB, I never knew about classes or anything then, I just dragged controls to the form, I set their properties, put code in events and voila! I have a working GUI application, which is probably why people recommend against it for beginners.

Then I moved to C, there were some features that I wasn't aware of (recursion, pointers, etc) but that wasn't hard to get used to.

Then came C++, I borrowed a book from the library and started reading it, I thought the only difference was just in the sentences and the libraries used (iostream, cout, cin, etc) but then I reached chapter 7, it started talking about OOP, it was complicated and I started thinking "Why on earth would I want to learn this?", so I just read it because I didn't want to skip anything, what made it worse is that chapter 9 (chapter 8 is about OOP too) was about programming for windows which is the main reason why I borrowed the book.

It wasn't until recently when I started using Flex and started planning for Deviyo that I realized that OOP is important.

All this time I've been in love with programming, I used to think it's the coolest thing on earth, I'm taking a course in IT, I'm convinced it's what I'll be doing for a living.

The result is? I fell in love with programming, it rejected me and I can't seam to get over it, but I'll keep fighting for it.