Sorry, this is a cheap move. But it’s been busy lately, and ended up choosing to focus on code tonight at the expense of the blog.
Lately, I’ve been spending as much free time as I can working on a side project. Which – yay! I went through a spell there of a few weeks where I didn’t have any kind of side project. Which felt… weird.
I’ve never really been a fan of laptops, as I’ve always loved the tactile feel of a Mac keyboard. My hands are used to the sensation, and the whole muscle memory of it all. Typing on a laptop feels weird and alien to me, and it just doesn’t feel right.
A good portion, nearly 50%, seemed to cover Node (npm, Express, Swig) – which is actually great for me. I’ve long wanted to delve more into Express and Node development in general, so this is actually quite exciting.
Of the many mistakes I made as an early programmer, this was a huge moment: one equal sign when I was supposed to use two (assignment versus equality). I lost a lot of time troubleshooting an issue that turned out to be something simple.
With my approach now, I’m taking a lot of that initial work (searching, parsing) and letting that take place on the server. Instead of bundling it with the app, I’m using a Node server on Heroku, and also storing some database content via MongoDB.
Even now, writing this, I struggle with defining myself as a developer. I work with code, but I still don’t feel like I’ve earned the title developer yet. I still feel far away from that designation.
“Hopper invents a compiler in 1951, and it allows people who don’t have PhDs in Mathematics to start talking with these machines… to start programming these machines.”
“[…] looking for good software to count on has been a losing battle. Written by people with either no time or no money, most software gets shipped the moment it works well enough to let someone go home and see their family. What we get is mostly terrible.”
Earlier today, I saw a really neat article called Badassify Your Terminal and Shell, by Jilles Soeters. It’s a great walk-through, and I’m finding myself geeking out and looking at the command line in a whole new way.
This is a screenshot, showing my API usage for the project I’m working on currently. Can you spot where I started to really test the thing? And can you also spot where I ultimately optimized my code, so that it wasn’t making such heavy calls? Pretty proud of that second one.
Been trying to get up early these last few weeks, as I’m in the home stretch of launching a new project. I was hoping to launch this week, but I’ve got some more polish and tweaking to do yet. It’s been very exciting and fulfilling, and I’m really looking forward to sharing this one.
It’s been pretty good lately, on the coding front. At work, there’s been a push for us to start using Angular. And after a few sessions and tutorials, I’ve started to work on a personal/side project with Angular – building, practicing, and learning a lot in my off hours.
Spent a lot of today working on a personal project (while at the same time, getting some practice in with AngularJS). While it wasn’t a flurry of productivity, I do feel good after having put in a pretty solid number of hours.
One really awesome thing about Twitter is that you can follow people who are way smarter than you. And oftentimes they post up links to really awesome things that you would never have come across, without their help. Case in point: Wavespot, a really cool, live editor that will create an audio sample based on user input.