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.
For much of this holiday weekend, Liz and I have been holed up in the apartment working on our respective projects. I’ve spent a great deal of time coding the past two days. Well… maybe not coding per se. I haven’t built a ton of new functionality just yet. Mostly, I spent a lot of time reading up on things (and also trying to get a few different technologies to play nice with one another).
In particular, I got a better handle on multiple cursors, how to select multiple items, and how to use the command palette (and reduce my use of the mouse). I also got introduced to a variety of helpful tools like Emmet,
Prefixr and Fetch. Although for my purposes, I think I need some more brushing up on the fundamentals, before I dive into shortcuts.
Near the Johnson Space Center in Clear Lake, Texas, a group of programmers enter line after line of near-perfect code for NASA. Known as the “on-board shuttle group,” these coders make the software that handles over $4 billion in equipment – where a miscalculation that’s 2/3 of a second off can put the space shuttle 3 miles off course. Charles…