6 Weeks Later
In my last post, I talked about deploying my first app, CrowdNotes, to Nodejitsu.
Since then, I have actually managed to get to where I wanted to be when I first talked about transitioning into web development!
I’m SUPER pumped to announce that I’m now a Junior Developer at Skookum Digital Works, the best web shop in Charlotte. 6 weeks ago, I started as an intern, learning the ropes and getting exposed to all the technology I’ve wanted to play with!
In 6 weeks, I have done the following:
- Built another Node app
- Done front-end work in HTML5 and CSS3
- Built a WordPress theme from scratch
- Learned about test- and behavior-driven development
- Manipulated the DOM using JQuery and Ender
- Played around with Knockout and Mocha
Earlier this week (Monday, to be exact), I started my first day as a full-timer. Gone are the days of being an intern – but here are the days of using technology to make things AWESOME!
I couldn’t be more pumped.
With my new-found knowledge, I’ll be updating my website (honestly, it looks terrible now…) and hopefully be blogging more often again.
Huzzah and thanks for the support!
Congratulations! I had no idea you were even interning there. Best of luck.
Hi there, I’ve been using this great model to work on an express app and I have a question for you:
my accessDB.js file is getting rather large. I’d like to segment it out further and I was wondering what sort of structure to use to do that. Would it work to have an accessDB.js file that looks like the routes.js file and points to sub-files for each section?
The problem I’m running into is that I have to create a variable for each include, so I’m doing things like db.section1.function1 and db.section2.function1 etc. I’d like to just have everything under db like it would be with just one huge file.
Any ideas?
Thanks again for the great model.
Hey Tom,
Do you have your code up somewhere on GitHub or something similar? I’d be happy to take a look at it!
Looking back on my original CrowdNotes implementation, I would actually change accessDB.js to not exist anymore. A popular way of organizing an app would be to use a traditional MVC model (Model, View, Controller). In the case of CrowdNotes, the models/ folder has the models, the views/ folder has the views, and the routes/ folder has the controllers. AccessDB.js is just an extraneous level of stuff that should actually be dispersed out into the models.
If I had time (I’ve been a bit busy lately, unfortunately, but life should be easing up sometime in November!), I would completely re-organize CrowdNotes to make a bit more sense.
In lieu of that, however, I’d be happy to help you out! Like I said, send me a code sample and I’ll be happy to show you a better way than the multi-level objects you mentioned
Hope that helps!
Thanks for the info, that helps a great deal!