Bend Blogs » dopeblend news

dopeblend news

• March 14, 2010
• 22:01

  CLASS ACT

   » ‎ dopeblend news

  Tags:    [edit]

  

  I recently finished a javascript project for a web based service that connects students with tutors in their area. It was my first project using regular expressions and creating browser cookies. I encountered many new javascript methods that I had never used before such as 'replace()', 'match()', 'substring()' and 'split()' to name a few. It was a fun and challenging project with one major goal that I set for myself. Write it using Object Oriented design techniques. Up until this point, I have been writing just a bunch of functions. I finally felt up to the challenge to create my first set of objects. I appropriately named them 'Validate' and 'Cookie' to reflect their purpose. Converting the functions to methods was pretty straight forward and I eventually figured out how to create attributes using 'this'. The final result was two shiny new javascript objects. I then got to thinking about how I could redesign my website so that it too was object oriented. No problem I thought, until I had a good look at the challenge ahead of me. Sure I could convert all of those functions into objects in no time flat, but what really is the purpose of OO design? OO designed code can be reused, maintained and extended much easier than functions. If I am going to do this for the rest of my life, I might as well make life easier for myself. I think I read once that javascript is like a 'snap together' language. OO design offers a class model for creating software systems. Objects in the computer world are like objects in the real world. They have their own set of attributes and behaviors and can interact with other objects. There can even be subclasses of objects that inherit the main classes attributes and behaviors in addition to having their own unique set. Hey, what a novel idea! When I created my website, I had a basic idea of how I wanted it to do but I never really sat down and designed it. Its time to take a look at the bigger picture. I have a lot more coding to do before I become proficient in the language but now I see a method to the madness. I think I will devote a little more time designing my app before jumping into the code.
• 22:01

  NO EXPERIENCE NECESSARY...

   » ‎ dopeblend news

  Tags:    [edit]

  

  Blogging intimidates me. Give me an XML response from a HTTP request and I'll extract the text, give me a database project and I'll develop a schema with key constraints, ask me to write about my myself and my interests...well, you might as well ask me plan the next mission to mars. Expressing myself through writing has always been a challenge for me. I'm envious of people who do it so easily. My writing has about as much appeal as a grocery list. I needed help. Fortunately, my wife Tara is one of those naturals. She maintains her own blog and sells on Etsy. A couple of words of wisdom have stuck and seem to be helping me out so far. Write in you natural voice. I understood that as "write as if you were speaking." This made life so much easier for me. Writing always conjured up painful memories of grammar class and learning how to write 'correctly'. I could rewrite a sentence five times before I thought it adhered to these standards and it would still suck. Don't sweat the details, just get it on paper and worry about the rest later. Follow other writers. This step I have yet to follow but I'm going to start today. After my first post I found myself already starved for ideas. You might be thinking to yourself "really?" Yup, Nada, zip, zilch. Tara wrote the note to give me some ideas to tide me over. Ideas are born from other ideas and Tara has a dozen or more blogs that she follows for inspiration. Also, it doesn't hurt to drop your two-cents on someone else's blog. It makes them happy and gives you a chance wax poetic...it might even increase traffic to your blog. Let your reader know who you are. This is what separates a blog from say...an article out of the Journal of Medicine. Whether it is how you write, the music you listen to or the clothing you like to wear, the best blogs have a real personal feel about them. And for all those camera shy folks, pictures of yourself are a good thing. Lets face it, people are interested in other people. So this is my blog about blogging. If you have some blogging tips for this newbie, by all means let me know. In the meantime, I'm gonna coast on the ideas that Tara gave me and see what develops. Check out my Tara's blog at: [elanvitalanthology.blogspot.com] and her Etsy shop at: [www.etsy.com] Thanks for reading, Jeff
• 22:01

  IF I COULD DO IT, SO CAN YOU!

   » ‎ dopeblend news

  Tags:    [edit]

  

  If you have never written any code in your life and want to learn how to develop websites, you have to pick up the Head First book series. Yes, five months ago I had never written a single piece of code in my life. I had no idea what an html tag was, how a javascript function was made, how to query a database and much, much more. I know this is sounding like one of those testimonials(it is), but seriously these books are worth every penny(and if you buy them on Amazon you will spend less pennies). I think what makes these books so great is their approach to teaching the material. They really get into the mind of someone with no coding experience whatsoever. The first book I picked up was Head First HTML. This is where you need to begin your journey. The book is well written, with easy to understand exercises that build upon each other. You will look forward to learning every time you open the book and should be a black belt in the subject by the end. Next I moved on to Head First Javascript. Javascript is kind of like chess; you can learn the basic moves quickly but it will take time to master the game. This book may be a buzz kill after completing Head First HTML, but in reality you can not even compare the two. I picked up other books on the subject but found this one to be the best for understanding the basic concepts. The good news is that once you begin to understand how javascript works, a whole new world will open up for you. Many of the other scripting languages you will encounter share similar syntax and follow similar logic. As an added bonus, the final exercise introduces you to AJAX. I did not pick up this book next, but it might be a more logical progression from the javascript book. Head First Ajax delves deeper into how to create dynamic websites. I'm not going to say that the days of the complete page refresh are over, but Ajax coding is seductive in how quickly and efficiently it retrieves only the data you need. Head First PHP & MySQL is a must have. After you have done battle with javascript, you will be relieved after you discover PHP's similarities. Yes, you will have to create variables and functions, but it will be old hat for you by them. If you are an organizational freak like me, databases will be your best friend. If you are a business, databases are essential. In my opinion, knowing how to create, store and retrieve information from databases will give you the edge. As great as these books are, you will still find yourself searching for answers to issues on internet forums, calls to friends or what have you. You will pull the occasional all nighter(or if you are like me the twice a week all nighter). You will curse at your computer, pull your hair out get in a fetal position and cry sometimes. But in the end, you will figure out how to solve that problem and have your scripts work in all browsers(even IE!). This is all just a part of it. Trust me, you'll feel great when your site is up and running. P.S. The only side effects are that you will occasionally geek out on your partner after learning something new. If they love you they will smile and say "Wow, that's great!"
• 22:01

  HINDSIGHT IS 20/20

   » ‎ dopeblend news

  Tags:    [edit]

  

  Today I had my very first job interview for an HTML and CSS coding position. I didn't get the job, but I did gain valuable insight into where I need improvement. I want to share my experience in the hopes that someone else learns from my mistakes. The day before the interview, I did a drive by of where the business was located. I have heard horror stories of people being late to or missing interviews because they made a wrong turn or just could not find the place. I wasn't about to make this mistake. Comfortable that I knew where it was, I next went to buy my interview outfit. I made some calls to friends who work in the tech industry to get a feel for how I should dress. Button down shirt, yes. Jacket, no. Tie, optional(sign of respect). It took me a while to find clothing that was appropiate, that I felt comfortable wearing, and that I could afford(My first stop was Banana Republic; when I saw that a tie cost a minimum of $50 dollars, I fled. I ended up buying three ties from Ross for $10 bucks a piece). Once that was settled, I went home, took care of my daughter until she fell asleep and then went to my computer to do a little company research. The company I was about to interview with works with insurance agents/agencies to aid them in direct marketing and offer them business tools that facilitate their business. It seems to me a facinating niche market. Interview day. I was woken up by my daughter around 7am with her morning chant "bottle, bottle, down, down, play?" Took care of her till 8:30 and then got dressed. I was painfully reminded of how long it had been since I last tried to tie a tie. Getting it on my third try, I finished whatever else I needed to do and was out the door by 9:30. I turned on the radio; OPB was broadcasting an interview about some depressing topic. I switched the channel to some sort of techno, drum & bass. That was more like it. I decided to blast the heat to warm up my hand which always get cold when I am nervous. I over shot one of the traffic circles, but realized the mistake soon enough to get back on track. I arrived to the interview on-time and ready. I told the receptionist that I was here for a meeting with so and so and shortly there after was greeted by my interviewer. We went to a conference room down the hall to begin. As far as I could tell the interview went smoothly. He asked me about my experience level and I gave the most honest answers that I could. Advice that I was given, which seems like common sense now is to be as honest as possible. I guess there is nothing worse then saying you know about something, or know how to do something, and have it discovered later not to be the case. We next went on an office tour and I had the chance to meet some of the employees from the different departments. This is where things went bad. I failed to mention that before the interview concluded, I was told that I was to be tested on my coding skills. All of a sudden a crack appeared in the shiny suit of confidence that I was wearing. In the test, I was asked to design a logo in photoshop and change some CSS on a website in the works. I can do this, I can do this. Then I was sat before a Mac. I don't know how to operate a Mac OS since I have been working on Windows up until this point. Also I have been using Dreamweaver to create my sites. No Dreamweaver to be found on the premises. He was using Coda to edit HTML and CSS. I had never used this tool before. Let me take a moment to say that when you get nervous, you can lose focus and not hear things because your mind is racing. "How long do you think this will take you?" "Ah, um, twenty minutes." I responded. He left me so that I could work. I won't go into much more detail except to say that it took me longer than twenty minutes to complete the project. After what felt like an eternity of pain, I completed the project and got feedback. My design skills are lacking. I should think about taking courses, and then the dreaded, "We will contact you about our decision"(translation: Sorry buddy, you didn't get the job). I collected what was left of my self-esteem and thanked my interviewer for his time(He was very nice during the entire process). I waited the rest of the day for a call that never came. Instead of beating myself up over the experience, I tried to look at the positive side of things. 1) I got an interview: It takes a lot just to get into the door. 2) I got positive feed-back about what areas I could use improvement: Not only do I need to improve my design skills, but I realized that I need to improve my semantic coding practices. It also wouldn't hurt to learn Mac OS. 3) I got insight into what I might expect the next time I interview: This is priceless. Next time around I'll be better prepared. Looking at it from this perspective, I can lick my wounds and face the new day, armed with a little more knowledge than I had the day before. Good Luck! Jeff
• March 13, 2010
• 0:01

  HINDSIGHT IS 20/20

   » ‎ dopeblend news

  Tags:    [edit]

  

  Today I had my very first job interview for an HTML and CSS coding position. I didn't get the job, but I did gain valuable insight into where I need improvement. I want to share my experience in the hopes that someone else learns from my mistakes. The day before the interview, I did a drive by of where the business was located. I have heard horror stories of people being late to or missing interviews because they made a wrong turn or just could not find the place. I wasn't about to make this mistake. Comfortable that I knew where it was, I next went to buy my interview outfit. I made some calls to friends who work in the tech industry to get a feel for how I should dress. Button down shirt, yes. Jacket, no. Tie, optional(sign of respect). It took me a while to find clothing that was appropiate, that I felt comfortable wearing, and that I could afford(My first stop was Banana Republic; when I saw that a tie cost a minimum of $50 dollars, I fled. I ended up buying three ties from Ross for $10 bucks a piece). Once that was settled, I went home, took care of my daughter until she fell asleep and then went to my computer to do a little company research. The company I was about to interview with works with insurance agents/agencies to aid them in direct marketing and offer them business tools that facilitate their business. It seems to me a facinating niche market. Interview day. I was woken up by my daughter around 7am with her morning chant "bottle, bottle, down, down, play?" Took care of her till 8:30 and then got dressed. I was painfully reminded of how long it had been since I last tried to tie a tie. Getting it on my third try, I finished whatever else I needed to do and was out the door by 9:30. I turned on the radio; OPB was broadcasting an interview about some depressing topic. I switched the channel to some sort of techno, drum & bass. That was more like it. I decided to blast the heat to warm up my hand which always get cold when I am nervous. I over shot one of the traffic circles, but realized the mistake soon enough to get back on track. I arrived to the interview on-time and ready. I told the receptionist that I was here for a meeting with so and so and shortly there after was greeted by my interviewer. We went to a conference room down the hall to begin. As far as I could tell the interview went smoothly. He asked me about my experience level and I gave the most honest answers that I could. Advice that I was given, which seems like common sense now is to be as honest as possible. I guess there is nothing worse then saying you know about something, or know how to do something, and have it discovered later not to be the case. We next went on an office tour and I had the chance to meet some of the employees from the different departments. This is where things went bad. I failed to mention that before the interview concluded, I was told that I was to be tested on my coding skills. All of a sudden a crack appeared in the shiny suit of confidence that I was wearing. In the test, I was asked to design a logo in photoshop and change some CSS on a website in the works. I can do this, I can do this. Then I was sat before a Mac. I don't know how to operate a Mac OS since I have been working on Windows up until this point. Also I have been using Dreamweaver to create my sites. No Dreamweaver to be found on the premises. He was using Coda to edit HTML and CSS. I had never used this tool before. Let me take a moment to say that when you get nervous, you can lose focus and not hear things because your mind is racing. "How long do you think this will take you?" "Ah, um, twenty minutes." I responded. He left me so that I could work. I won't go into much more detail except to say that it took me longer than twenty minutes to complete the project. After what felt like an eternity of pain, I completed the project and got feedback. My design skills are lacking. I should think about taking courses, and then the dreaded, "We will contact you about our decision"(translation: Sorry buddy, you didn't get the job). I collected what was left of my self-esteem and thanked my interviewer for his time(He was very nice during the entire process). I waited the rest of the day for a call that never came. Instead of beating myself up over the experience, I tried to look at the positive side of things. 1) I got an interview: It takes a lot just to get into the door. 2) I got positive feed-back about what areas I could use improvement: Not only do I need to improve my design skills, but I realized that I need to improve my semantic coding practices. It also wouldn't hurt to learn Mac OS. 3) I got insight into what I might expect the next time I interview: This is priceless. Next time around I'll be better prepared. Looking at it from this perspective, I can lick my wounds and face the new day, armed with a little more knowledge than I had the day before. Good Luck! Jeff
• March 11, 2010
• 21:30

  CLASS ACT

   » ‎ dopeblend news

  Tags:    [edit]

  

  I recently finished a javascript project for a web based service that connects students with tutors in their area. It was my first project using regular expressions and creating browser cookies. I encountered many new javascript methods that I had never used before such as 'replace()', 'match()', 'substring()' and 'split()' to name a few. It was a fun and challenging project with one major goal that I set for myself. Write it using Object Oriented design techniques. Up until this point, I have been writing just a bunch of functions. I finally felt up to the challenge to create my first set of objects. I appropriately named them 'Validate' and 'Cookie' to reflect their purpose. Converting the functions to methods was pretty straight forward and I eventually figured out how to create attributes using 'this'. The final result was two shiny new javascript objects. I then got to thinking about how I could redesign my website so that it too was object oriented. No problem I thought, until I had a good look at the challenge ahead of me. Sure I could convert all of those functions into objects in no time flat, but what really is the purpose of OO design? OO designed code can be reused, maintained and extended much easier than functions. If I am going to do this for the rest of my life, I might as well make life easier for myself. I think I read once that javascript is like a 'snap together' language. OO design offers a class model for creating software systems. Objects in the computer world are like objects in the real world. They have their own set of attributes and behaviors and can interact with other objects. There can even be subclasses of objects that inherit the main classes attributes and behaviors in addition to having their own unique set. Hey, what a novel idea! When I created my website, I had a basic idea of how I wanted it to do but I never really sat down and designed it. Its time to take a look at the bigger picture. I have a lot more coding to do before I become proficient in the language but now I see a method to the madness. I think I will devote a little more time designing my app before jumping into the code.
• 21:30

  NO EXPERIENCE NECESSARY...

   » ‎ dopeblend news

  Tags:    [edit]

  

  Blogging intimidates me. Give me an XML response from a HTTP request and I'll extract the text, give me a database project and I'll develop a schema with key constraints, ask me to write about my myself and my interests...well, you might as well ask me plan the next mission to mars. Expressing myself through writing has always been a challenge for me. I'm envious of people who do it so easily. My writing has about as much appeal as a grocery list. I needed help. Fortunately, my wife Tara is one of those naturals. She maintains her own blog and sells on Etsy. A couple of words of wisdom have stuck and seem to be helping me out so far. Write in you natural voice. I understood that as "write as if you were speaking." This made life so much easier for me. Writing always conjured up painful memories of grammar class and learning how to write 'correctly'. I could rewrite a sentence five times before I thought it adhered to these standards and it would still suck. Don't sweat the details, just get it on paper and worry about the rest later. Follow other writers. This step I have yet to follow but I'm going to start today. After my first post I found myself already starved for ideas. You might be thinking to yourself "really?" Yup, Nada, zip, zilch. Tara wrote the note to give me some ideas to tide me over. Ideas are born from other ideas and Tara has a dozen or more blogs that she follows for inspiration. Also, it doesn't hurt to drop your two-cents on someone else's blog. It makes them happy and gives you a chance wax poetic...it might even increase traffic to your blog. Let your reader know who you are. This is what separates a blog from say...an article out of the Journal of Medicine. Whether it is how you write, the music you listen to or the clothing you like to wear, the best blogs have a real personal feel about them. And for all those camera shy folks, pictures of yourself are a good thing. Lets face it, people are interested in other people. So this is my blog about blogging. If you have some blogging tips for this newbie, by all means let me know. In the meantime, I'm gonna coast on the ideas that Tara gave me and see what develops. Check out my Tara's blog at: [elanvitalanthology.blogspot.com] and her Etsy shop at: [www.etsy.com] Thanks for reading, Jeff
• 21:30

  IF I COULD DO IT, SO CAN YOU!

   » ‎ dopeblend news

  Tags:    [edit]

  

  If you have never written any code in your life and want to learn how to develop websites, you have to pick up the Head First book series. Yes, five months ago I had never written a single piece of code in my life. I had no idea what an html tag was, how a javascript function was made, how to query a database and much, much more. I know this is sounding like one of those testimonials(it is), but seriously these books are worth every penny(and if you buy them on Amazon you will spend less pennies). I think what makes these books so great is their approach to teaching the material. They really get into the mind of someone with no coding experience whatsoever. The first book I picked up was Head First HTML. This is where you need to begin your journey. The book is well written, with easy to understand exercises that build upon each other. You will look forward to learning every time you open the book and should be a black belt in the subject by the end. Next I moved on to Head First Javascript. Javascript is kind of like chess; you can learn the basic moves quickly but it will take time to master the game. This book may be a buzz kill after completing Head First HTML, but in reality you can not even compare the two. I picked up other books on the subject but found this one to be the best for understanding the basic concepts. The good news is that once you begin to understand how javascript works, a whole new world will open up for you. Many of the other scripting languages you will encounter share similar syntax and follow similar logic. As an added bonus, the final exercise introduces you to AJAX. I did not pick up this book next, but it might be a more logical progression from the javascript book. Head First Ajax delves deeper into how to create dynamic websites. I'm not going to say that the days of the complete page refresh are over, but Ajax coding is seductive in how quickly and efficiently it retrieves only the data you need. Head First PHP & MySQL is a must have. After you have done battle with javascript, you will be relieved after you discover PHP's similarities. Yes, you will have to create variables and functions, but it will be old hat for you by them. If you are an organizational freak like me, databases will be your best friend. If you are a business, databases are essential. In my opinion, knowing how to create, store and retrieve information from databases will give you the edge. As great as these books are, you will still find yourself searching for answers to issues on internet forums, calls to friends or what have you. You will pull the occasional all nighter(or if you are like me the twice a week all nighter). You will curse at your computer, pull your hair out get in a fetal position and cry sometimes. But in the end, you will figure out how to solve that problem and have your scripts work in all browsers(even IE!). This is all just a part of it. Trust me, you'll feel great when your site is up and running. P.S. The only side effects are that you will occasionally geek out on your partner after learning something new. If they love you they will smile and say "Wow, that's great!"