- Most Recent | Since 2004
- List View
- Archive
- March 12, 2016
Super Accidental Creative Business Brainstorming Day (GHD040)
March 12, 2016Read moreI have been feeling jittery for the past several days, feeling the desire to work on projects while simultaneously turned-off by the complicated and time-consuming rkaequirements for starting them. I also have been spending too much time in front of the computer, and decided I needed time away from all things computery AND also my own looping thoughts. What do normal people do to get away from from their own thoughts? Or do normal people not have this problem? Musings and some nifty insights follow! (more…)
- March 12, 2016
Music And Friends Day (GHD039)
March 12, 2016Read more
Friday was a rest and recovery day, starting with a Korean food expedition and culminating with Piano Karaoke in the evening. As far as my Groundhog Day Resolution goals are concerned, it was a day for reflection on the music composition goal with music-oriented people. Good times were had, and new foods were consumed! (more…)
- March 11, 2016
Porting Code Finale! (GHD038)
March 11, 2016Read moreAfter Wednesday’s megabinge on coding, I took Thursday slowly after waking up quite late. I ported the old game demo code from Project 1401 (my video game test code) to the new Engine 1401A1 organization. It was a matter of copy/pasting directories and then updating some references. The net result is that the game is exactly in the same place as it was before I started all this stuff. The only thing new is the build system and the directory organization. While I might be tempted to grumble about this, the big takeaway is that I think I’ve leveled-up in my understanding of these tools, and that will help me be a better developer! So…yay for me!
Stuff Learned and GHDR Points Earned
I didn’t do much today. But I posted some more working code to GitHub, though it’s the same working code as before. On the plus side, I’ve improved the Github repository organization a bit too, so it’s easier to browse online and get a sense of how the project fits together.
PTS DESCRIPTION 10 posted working code to GitHub (sorta a stretch) 10 fulfills a current wish, makes future results more possible, packaged results and made it available! 3 Tried a bunch of stuff I didn’t know would work. 2 Posted words on this website! 1 Researched a lot of code-related stuff Let’s call it 26 points, not bad. Tomorrow I need to switch gears and do something else for the weekend. There’s piano karaoke tomorrow night, and I’m having lunch with a music composer friend in the area…hopefully something unexpected will happen!
About this Article Series
For my 2016 Groundhog Day Resolutions, I'm challenging myself to make something goal-related every day from February 2nd through December 12. All the related posts (and more!) are gathered on the Challenge Page.
- March 10, 2016
Rebuilding Code for Engine 1401A1 (GHD037)
March 10, 2016Read moreWednesday was an even longer day than Tuesday. I just finished a 20-hour programming push to rebuild my Javascript development process and tools. The next stage of my project work, as I have mentioned before, is closely related to my own game project goal. One of my general development goals are to have an expressive, self-documenting code base that’s super-easy to understand, supported by tools that adhere to the same philosophy. One of the key tools is a so-called “task runner”, which gathers up the hundreds of separate files that comprise a modern web application and arranges them into a runnable project. I’d been using one called Mimosa, which was one of the better-documented task runners back in 2014, but I had found that some recent features I wanted (an up-to-date Typescript transpiler, for example) were unavailable unless I wanted to write an extension. After looking at that, I got a huge headache and was encourage to roll-up my own task runner using Gulp. To do this, I had to reconstruct a new build system around the technologies I wanted to keep using, which meant a lot of LEARNING ON THE FLY. (more…)
- March 9, 2016
Javascript Code Sprints and Broken Printers (GHD036)
March 9, 2016Read moreTuesday was a very long day of kicking off a major coding sprint; I’m just wrapping it up at 4AM on Wednesday, in fact! I spent a good chunk of the day reviewing our research code base to look for problems and opportunities for improvement in the next phase of the project. A lot of this work is relevant to my game project goal, but it is also the kind of work that is not very exciting to show off because it is mostly text. In this post I’ll just quickly recap the kind of things I’m looking at as a report. (more…)
