#devTO Did Social Media Week

As we’ve mentioned before: we were doing Toronto’s Edition of Social Media Week. Several technology and community focused events for its’ cause. And of course, we had to say something. Yeah – #devTO. 10 successful social media events in meant that we did have the know-how to setting up a successful, casual, beneficial, and always fun event.

We gave out some secrets. We spilled some beans. We had to: it’s to assist in the growth of the scene. Also, it’s to help people slap that bull when it comes to making a community. There were several takeaways. Especially one being that regardless of setbacks, mishaps, missteps, and team debauchery, we were able to stick it out for 10 months. Long enough to count it as a success. And also, more consistency not just with the Monday meets, but also with content to aim it at the constructors of the code.

And yes… I brought my stein.

Well, even though we’re done for the week, Social Media Week Toronto is still on! Definitely worth a looksee. :)

And thanks for coming out to all of you! See you on March 26th!

Stuff You Missed Sunday – Sitcom Timing

Well, from the looks of it, Sunday’s about to start or probably already has for the most part. What’s really going is that I decided to act upon some advice from a local gentleman PR guy, Michael Nus, about producing content for blogs.

“Got 30 mins?”

The answer intrigued me. 30 minutes? Seriously?! That’s it? Yeah, I was shocked, but at the same time, I saw where it was coming from. Consistency will help get those “perfect blog posts” out. Agonizing about them before hand does probably not so much as expected. So I got myself together and started to get back on the wagon. Surprisingly, bringing back 365 blogging vet Casey Palmer on to task. With all the hecticness going about, why would I need to be doing this? Let’s see how this works out.

Last Week on kevinvs.html:

 

And of course, if you were lucky to get into our Social Media Week Toronto Origin of #devTO Story talk that does NOT start with this one time at bandcamp: kudos to you. We’ll see you tomorrow.

Bring questions.

Make Code Things Make Sense

Constructors. That’s literally what seems to be associated with our titles as web professionals. Mine, also – if anything.

And as such, we’re meant to build things. On the outside, the clients love seeing things planted and blossom. Yet if we, the developers, rip it apart: the fighter pilot/poker snub/veterans come out. We comment, ridicule, suggestions, praise, and everything in the form of communication. The critique. Especially when the project is at a toss off stage.

Even before then, the developers are meant to make the very barebones make sense, irregardless of whatever level or standard. Clear naming conventions. Well indented code. Things like that. It’s really important to make meaningful comments and other items of note inorder to keep balance and sense within the realm of the code because of
random occurrences, such as updates that need to be done. These little steps here will help us make a little bit more sense with our coding.

Proper Use Of Indentation
Just a good way to organize your condition statements and other gangs of functions, conditional statements, and other items of note. It just helps keep the code clean and reading won’t be such a problem. Won’t kill you to doing so.


Use proper naming conventions:
This pretty much goes without saying. Better to have a .article_div than a .big_center_thing anytime. Especially in both CSS and Javascript. In JS, I’m usually the..

[itemtype]_[whatitis]

…just to make sure that I remember what goes in. It’s also useful for debugging. Leave the mysterious names for your social aliases.  For instance:

var array_choices = [];

I’ll have a list of choices to make in the item. Has to be done this way because I’ll be using an array to iterate through several decisions to use for a user to choose from.

Proper Commenting
Always leave proper comments during your coding in anything that you do. There’s no telling what could happen down the line. Better to prepare for the worst than expect the best. Be descriptive as possible. One line should do it.

/* This is where I’ll be making an alert */
alert();

Sure it’s a dirty job to make things that make sense, but with these tips, there will be LESS confusion on the follow through. Who knows? you might EVEN save lives and not pull off dangerous maneuvers, Maverick.

 

 

Make Things Make Sense

Proto App Test Drive or The Day I Got Shout Out By Adobe (Review)

 

 

After Adobe’s recent moves to take the Flash out of mobile and acquired Phone Gap, seeing them in the App game is excitement within itself. Especially with a wireframe builder. Yes – an App that produces Information Architecture like it’s stuck at your desk, creating the site/app groundwork to alternative music and Redbull!

Adobe has produced an app called Adobe Proto for the Android 3.2.  And of course, I had to try it. The app is great and does alot of things right. Gesture created elements, various media aspect support. You can even do 960px layouts! There’s exporting also, which also you to create an HTML representation of what was produced. The other drawback? well, if you save that and upload it to Adobe’s creative barn, it may not be editable again. Even with the Creative Cloud link. That there is a drawback that needs to be addressed.

Outside of that… well, …

Test driving @adobe #proto with a real wireframe that I built... on Twitpic

 

And of course, I got a shout-out during my dental waiting game usage.

 

Yes, it felt great for just a second! :D As for Adobe Proto, I do like the current system build minus those small things. Still, a great idea to use this for a tablet build. Definitely worth the $10 purchase for anyone into the site planning game hands down.

Best used when you’re sitting down for a long period of time. :D

 

 

Stuff You Missed Sunday Sprt. I – The First Step Is Admitting.

 

Don't Drink And Code

Developers Don't Drink And Code... unless it's at #devTO


First off: Wished I was more consistent here. TOTALLY DO. I must have only threw up one or two posts since this year has started. One of them goes out to @maricelarivera.   Before I get into that, let me tell you about this whole Stuff You Missed Sunday thing. Really, Stuff You Missed Sunday encompasses posts from both my blog and of course, when I drop down and do a tumblr for that week. Just a recap of crap you DID miss because we all know that we’ve got better things to do than skip posts in RSS Readers.

  • HTML and How The Heck Do You Start is pretty much that ONE post that I procured all week long. I really thought that this needed to be said. As stated, I’ll probably make a part two or elaborate on the basis of the HTML journey. Too bad, I didn’t have this sort of post when I started coding about ’99 or so.
  • UI/UX Developer Darcy Clarke’s blog did get something very crucial out this week. Something that alot of people need to read. Thanks for this post, friend. I can relate completely. Usually, with me – my posts/ideas/concepts don’t even leave my brain. Something that I would like to stop doing, also.
  • And of course, #devTO is back! As Chris stated: developers don’t take holidays. #devTO is no exception. We’re getting into Silverlight Pivotal and client relations from three of our mainstays!  And you thought that December was nuts! Sprint IX has several new surprises, including our BRAND NEW SPACE! …but you’ll need to check out the post to see how Harth we get up to. January 30th is the date. Looking forward to it!
  • The Toronto Android Users Group is starting up on January 22nd. After a reboot, and installing some of the Android SDKs, I have to say that I’ll definitely be ready to get into it! :) If you’re coming, make sure you’ve got the Android 3.2(or Honeycomb) installed. As… I’m doing… right… NOW!
As for going forward, I have a few posts up for throwing up, in the works. I cleaned up my PC, so we’ll see if I can wow the crowd better this week!