Typical Deliverables

No matter what type of project you are looking to have completed the basics of what you should receive before calling it done are basically the same. Typically I ask for a zip file or DVD with the contents on it.

• Finished Artwork — whatever the desired end result is should have been accomplished and stored in one or more files or folders.
• Raw Artwork — this is typically a layered PSD graphics file or an EPS Vector Graphic. These are needed in case you ever want to change something and you use a different designer it won’t cost you money to pick up where it you left off.
• Fonts — There are thousands of fonts in existence and even though something like Helvetica is a standard font, doesn’t mean the Helvetica used is the same as the one installed on your machine. So ask them to include the fonts used to make sure you will be able to edit the text on the document in the future. This is also very important when dealing with a printed piece.
• Supporting artwork — If photos or illustrations where used in the making of the piece the original largest sized version of the stock photos should be included in case some major alterations need to be made to the design and maybe part of the photo is clipped off.

Logos.

When designing a logo you want to make sure you get a vector graphic of your logo, those are EPS, AI (adobe illustrator), SVG, and some pdf files. A vector graphic is one where the design is made up of mathematical formulas and vectors that define the image. These can be scaled as big or small as needed without losing quality. So for instance if some day you want a billboard with your logo on it, this will probably cause you to have your logo redone. A pixel graphic like a PSD, JPG, PNG, or GIF store a series of dots for whatever sized document. They do not scale well and you will notice a blocky effect known as pixelation when you try to make one bigger. This will pose a problem in the future. Some PDF files simple include a pixel graphic rather then a Vector graphic.

Anymore no many designers seem to do logo cookie sheets and band guidelines. If you find someone that does you are in luck and probably have a good designer, however I recommend you ask for one. A cookie sheet/ Brand guideline document describes how the logo should be used in different background colors, sizes, etc. For instance what does it look like in black and white, color on black, color on white. When it gets really small does part of the logo disappear? Typically the cookie sheet portion is all the typically sizes needed, already setup and ready to go.

Web Site Design

Typically you will need a PSD file as one of the deliverables. If the designer is not going to provide an html file for the design/template you will need the PSD file to aid your developer in cutting graphics. This is a process where the image is broken up into small pieces to minimize download time.

Business Cards/Print work

You will want 2 version of the finished artwork. You need a print ready version, and an editable version. In Photoshop or with PSDs you will want to make sure the text layers are converted to rasterized layers, the DPI is 300. In Adobe illustrator select the text objects and select “Convert to Outlines.” Make sure the bleeds and gutters are setup to the spec your printer requires.

These are the basics for what you need to ask for when getting a graphics designer to take on your project. If you have any questions please post them below and I will be glad to answer them.

SEO is one of the most powerful ways to get your site out there, through content creation you create a lot of hooks on the internet that help catch internet searchers. But you need to use good keywords inside your content to make this effective.

One industry standard product I’ve found extremely useful is Market Samurai. I’ve used it extensively for all my web projects and content. It has made it easy with one dashboard per project to see my current seo rank, do keyword research, analyse my competition’s seo, find places to promote my site and products to sell and monetize the site.

The most valuable piece being the keyword researching followed up by the rank tracker. I can easily generate keyword ideas and have them analyzed to find good long tail keywords to target and make a list, then add them to my rank tracker and monitor how my efforts are going and see a graph of improvements. Click on this link to Market Samurai and try it free if you like it and buy it within 7 days of trying it you will save $50.

This is a great tool to start your internet marketing and keyword research with.

If you have never tried to develop a video game let me put this into prospective. A game is a culmination of every discipline within programming you have the following aspects that companys have teams just to handle any one of these…

• Graphics
• Game Theory/Logic
• Sound
• Music
• Physics
• Object collision
• AI
• User Interface
• Data Storage
• Performance Tweaking

To build a game you need to incorporate all this into one application. On top of that if you go after a real time first person shooter not only will you have to do all that, but you will have to do it faster. You will need to be good with memory management, drawing buffers, and soo much more. Most developers still use C++ because it’s a very lean programming language and gives you direct control of your memory management allowing them to better clean up memory then say the JAVA Garbage collector can.

A lot of people don’t respect the work that goes into a game or the minds behind it. To me a video game developer is the most elite developer there is. Games have become so complicated that the lone game developer is very rare even for something like Bejeweled.

While business software is very lucrative of a profession it generally fails to test your skill anywhere near what games will. Sometime stop and think about a game and how you would go about implementing it. If you have never done one try making a really simple little game, think old school Atari or Nintendo and see if you can build a clone. This is a great challenge for those who are looking to test their might.

In the end it’s a judgement call based on your particular factors and software needs. Here are some of the thought provoking questions you need to answer to know if building or buying is the right choice.

1. Is the component a critical piece of your application or a secondary function. Critical pieces are a more likely to be something you build rather then buy.  When your software’s core functionality depends on the module you don’t want to trust that piece to an open source project that may not survive time.
2. What happens if the component were to stop being developed could you swap something else in and continue on? Software is a fluid thing people loose interest or something else surpasses it. I’ve seen many Java and PHP Frameworks and Modules die off online that had great potential and value. If you rely on these pieces that means whatever bugs, security issues, or lack of functionality will be their indefinitely until you spend money switch components and move on,  maybe even build your own.
3. Was the component meant to do exactly what you need or would you be hacking it to work outside of how it was intended? Sometimes a component may do what you want as a side function or through Jerry rigging the thing to do it. This may use the module in a way the developer didn’t intent. If you rely on this functionality there is a good chance that this functionality will not always work as the developers won’t make conscious effort to support it. For instance using base64 encoding in the Sun’s JAVA packages, you can use it but they don’t intent you to so if they stop offering it in an update those functions will break.
4. Will it increase the costs of your software? What happens if they start charging? Paying for a component is actually a good thing, their is a higher chance it will continue to be developed and move forward if people are making money from it, where as open source the people have to be insanely passionate about it for the piece to survive time. However if you are going to have to take on  royalties or other costs you need to make sure the price point of your software after that fact is something the market will bear and leave you margins to make money. For instance the cost of scaling a Microsoft .NET application compared to a JAVA application.
5. How secure does the software component appear to be? When you use another piece of software you inhereit their security flaws and bugs. Many hackers start by trying to identify commonly used components of web sites or software get a copy of that component and try to exploit it. Typically, no random hacker is going to waste their time hacking a single site (unless they have malice towards the site), but if their is an exploit in a module and your site or app has it then you are more likely to be hacked because it’s easy. So their flaws become your flaws, and your customers will expect them to be fixed even if you have no control over it.
6. Does the module do something your teams doesn’t feel confident or competent enough to do themselves? One of the biggest factors you need to make a decision on, is if your team can manage that code on top of the rest of the code. Sometimes having an open source piece is good because other people are developing it for you. If you don’t have the talent or the time to handle that piece then you will either need to staff up or buy a piece. For instance you want to integrate Paypal or accounting with your site, you are probably better getting a prebuilt library out there to handle it then doing it yourself.
7. How much time will the component save, or cost to add? Buying a component to save time and money is in many cases a fallacy. Yes it can shave time off upfront but it doesn’t mean there is no time involved, or add time later on. You can’t for instance buy a quickbooks module and expect it to know exactly how to translate your accounting data into the way Quickbooks wants it, someone still has to code a translation, all they can do is provide a different means of talking to Quickbooks. You are better off in most cases just using the APIs Quickbooks provides directly so you know the bridge protocol will be supported in the future. And yes Quickbooks integration is going to be hell, long undocumented tedious hell. But this way you only one layer of hellish APIs instead of 2.
8. Did the makers of the component think the same way about the task as you do and your needs? The reason there are so many different software titles that do the same thing is each one does it differently. When it comes to components that can be a big deal. You may have a component that was designed to draw graphs but wasn’t designed to draw animated graphs for fractional numbers. A small difference between what you need it to do and what it does can make it unusable and a waste of time or money.

Software is a very fluid concept. No correct answer will stay correct over the software lifecycle. If you buy it, it may work great for you for 5 years, your preconditions change and you hit a wall and need to swap components. If you build it, you start with one idea in mind then the market tells you another idea is needed and you have to rework or rebuild it.

The question is really a judgement call of which one is going to be the best for your project for the longest time and least cost. Building it means you will have to maintain it, you will have to design it, and ultimately all issues are on you to resolve. Buying it means you will have to connect it, wait for someone else to maintain it if they care to, and ultimately have little control over it.

I’m more likely to build the core of the application and use 3rd party for communication protocols, or secondary functionality and stick to the fundamental language features for the core as much as possible. that way if the core needs to change significantly to meet the market needs then the software can too.

Work = 10 Hours * 5 days * 52 week = 2600 hours = 108 days
Sleep = 8 hours * 365 days = 2920 hours = 122 days
Dinner = 1 hour * 365 days = 365 hours = 15 days
Drive to/from work = 45 min * 5 days * 52 weeks = 195 hours = 8.2 days
Getting ready for work = 30 min * 5 days * 52 weeks = 130 hours = 5.5 days

Total = 6210 hours = 258.75 days = 106.25 days remaining per year

So over 2/3 of your life is gone just by basic human needs and work. When you then factor in other conditions such as family time, etc the time gets even shorter.

Now imagine you watch 2 hours of tv or movies a night…that’s 730 hours or 30 days of your year.thus cutting you down to 76.25 days left.

Time is a very precious thing, infact it’s the only thing we truely have and the one thing we trade freely. We assign a price to it every hour we work but its limited to 70 maybe 80 years. So it’s important to try and find ways to reduce the hours being worked above to increase the time you can spend with people and things you care about. Maybe it’s time to go out on your own, if you are already there try to cut your work hours down to 4 a day and see what happens, or 4 a week. Be Productive but Enjoy Life, you only have 1 go around and you don’t know when it stops.

In medieval times burning the ships was a way to say “No surrender, No Retreat.” For some this is a way of motivating themselves to do what must be done. I recommend finding another way.

Recently I am trying to help a couple people get back on their feet, mentally, physically and financially. For this article lets call the main person John Doe. In counselling John one thing that was evident to me was that he burned a bridge in their last employment. He was tired and burned out and didn’t act in an appropriate manner to move on. Instead he just walked, and after talking for a while with him about it and his job it sounded like it was one of the best jobs he had had in his industry. By the time he realized that it was too late. On top of that the company was a big name in town so having left there under those conditions did not do well for finding another job in his industry locally. So his only options are to look at other related industries, or move.

One thing I strived for through out my career is to build bridges not burn them. Right now the people I have worked with in through out my career have gone to work with almost every company in town and each one is a bridge of new opportunities.

1. Lemonade/Cool Aid Stand – This was a favorite of mine, you simply make up some Cool-aid and setup a table in the yard and sell cool-aid by the glass. This is a great way with how cheap cool-aid and sugar are. You need to watch it and not get too ambitious more and more stories pop up of cops ticketing kids doing cool-aid stands without a license. This typically only happens around big events

2. Mow Lawns — Try going door to door up and down your street and either put printed out flyers on the door of knock on the door and talk to the people. Offer to cut the their grass for $20, they take care of gas and mower, or if your parents let you use your mower do for $30 your mower. If you find my house I’ll be your first customer

3. Shovel driveways — When it starts to snow the last thing most adults what to do is shovel the driveway, unlike kids we ache a lot more, and have to bend over to shovel. Shoveling a driveway for $20 is another great idea. Eventually you can invest in a snow blower and do more faster.

4. Paper route — There is a strong correlation to kids who had a paper route and those who were successful, warren buffet use to have a paper route for instance. This is a great learning platform since you have to wake up early deliver the papers, collect the money and such. So while other kids are getting a couple more hours of sleep your hustling.

5. Umpire local baseball games – This was something I did when I was a kid. I umpire the local youth boosters league. The pay was $10-15 a game. Best of all to me it didn’t seem like work since I loved baseball.

6. Babysitting — at a later age babysitting is another classic job for teenagers.

7. Pet Walking – put flyers on people’s door with your picture on it, letting them know how old you are and that you will walk their pet for $10.

The most important thing is to be creative. That’s the most important thing for an entrepreneur. Think of things you can either do or do better then adults. Think of things people need done and would rather not apply their time to. For me my time is worth more then $20 an hour so I would gladly pay a kid to maintain my yard rather then do it myself. Creativity is the most important skill you can work on in life find workers to do something is easy, finding the next great idea is not.

Here are some small business ideas that can be a great beginner.

Start a Bulk Candy Vending Business — You see the candy machines in stores all over, did you know you can make 50% profit of every turn? The typical machine  cost 80-100 used on ebay and generated anywhere from $30-150 a month. The trick to this business is to reinvest your profits into additional machines and grow a larger route. It’s a very low effort business that borderlines passive income. You simply refill the machines and collect money. With 100 machines you can be earning 3000-15000 a month. Not to shabby.

Selling on eBay and Craigslist — Hit up your local thrift stores, garage sales, trash picking or business liquidators and snag some quick bargains. Then turn them around on eBay and make profit. This takes a little more effort you need to snap pictures research items and ship things. You can also learn to drop ship items to avoid shipping and having items hanging around. remember that with this business the money is made when you buy at a low price not when you sell. Things won’t necessarily go up in value so you have to get a good deal off the bat.

Snow Plow/Blower — When winter comes around and the neighborhood is covered in snow grab your snow blower and take it around to other houses ask if they want their place plowed for $20-30. Many people are willing to pay knowing how much time effort and pain it can be. With the snow blower you can finish it up in 10-15 minutes… That’s $80-120 an hour.

Network Marketing — Look at places like Amway and Avon. You help them sell their products and you get a commission. It’s pretty simple and gives you good skills with marketing and networking.

For more Business ideas check out this post.

Object oriented came to the mainstream in C++, there were other object oriented languages before it but none had been significantly embraced. In that system you were a hybrid of procedural and object oriented. It wasn’t really until Java that you say strict object oriented development.  What object oriented programming did was allow programmers to become storytellers and put the world on a sphere. When you do object oriented design it’s more like writing a play then a program. You look at all the actors in the play, their attributes, abilities, and interactions. Now the lonely add function becomes something more, you create a calculator object, and say the calculator object can add, subtract, multiply and divide. Now code can more realistically mimics life. One of the most classic programming examples is checking your mail, typically most books will think about the logic used in shift your mail..

if Bill do this,  if Letter do this,  else junk mail and trash

That’s fine and good and has it’s place in the person’s interaction with mail, however there are more fascinating way to look at it and other actors here  over looked. You have a mail box that holds mail, you have people yourself and a mail man  the people interact with the mail box.

So let’s define the mail box and how it is interacted with.

Actions: Open, Close, Add piece of Mail, add all mail, remove all Mail, remove piece of mail, check it’s full, check it’s empty, get fill status, set mode, check mode

States: Has Mail, % full, quantity of mail, open/closed, Mode:pickup/delivery

so when the mail man comes to the mail box he looks to see what mode the box is in, delivery or pickup, opens it sees if there is mail inside, if it’s pickup mode he retrieves the mail and then adds mail to the mail box if it’s not full and there is some to be added. then closes the mail box and drives away.

Then you come out open then the mail box, and if not empty you retrieve the mail, and close the box.

What’s interesting about object oriented overall is just the way of thinking. It become more interesting, you start seeing the interactions of elements of the system rather then just the end results. Like an engine in a car you build it out of little parts each having a role to play and when working together as intended energy is created and everything works. I believe once a person can learn to see the world in the object and relationships around them it becomes a more fascinating place to live and it’s much easier to learn then you would expect.

If you have ever been wrangled into this position before you may learn one of a few things pretty quick.

1. the person is an idiot, the computer error is user ignorance
2. they are the reason that pop ups and spam still exist on the internet
3. they just need to reboot.

While 95% of issues with a computer can be attributed to user error, or spyware the other 5% are legitimate bugs. However most bugs are nevercaused by something that you have control over like your code. Typically it’s more to do with other components on the computer interacting with each other, and what’s the answer to fix it? say it with me… REBOOT….

To the user it seems stupid like you are making fun of them but to those who have been under the hood it’s a little easier to understand why rebooting is the most common solution to every computer problem. So lets look at why. Since the computer isn’t a single application type of environment you have a lot of components that interfere with each other, for instance your anti-virus is looking at every action that happens on your computer and making a decision on if that action is safe and allowed. This means for every single task you now have a double task. Maybe it blocks a single routine because it’s questionable and that software is no longer working the way that developer intended. Maybe a developer was lazy and didn’t clean up their C++ memory handles correctly and a slow memory leak is in place. or maybe the younger 2.0 version of .net framework and the more mature 3.0 verison are both installed and get along like Hatfields and McCoys.

Fact is the potential causes of the machine going to pot are endless. In many cases you can’t figure them out, however when you reboot you start fresh and all is forgotten. So from the outside looking in it seems like a cop out. But from the techie’s perspective it’s a matter of determining if it’s worth looking into. A single issue can take hours to find, so if a reboot fixes it and it doesn’t come back for a month or two then it’s not worth looking into. However if it’s something the user has to deal with every day or minute it’s time to dig deeper.

Here is how the techie is thinking through the issue…
With computer repair and tech support you have to be able to replicate the error consistently in order to find the specific reason, and with so many variables that becomes difficult. If the issue comes up every month or year I don’t want to wait a month or year to see if something fixes it or changes the error. Figuring out what’s wrong is really a practice in the scientific method, you make observations about the way the error is acting to give you clues about where to look for the error, then you try to reduce the variables that are in play to see if removing a variable impacts the error and thus establishes a correlation. Once you find a few variables that correlate you start to test alternate states of those variables to see if the error goes away and try to establish causation. Typically once you find a few observations or corrilations you hit Google and search for other people having the issue and their solutions. After a period of looking and trying suggestions you may come to a dead end. You either run out of ideas on what to try, or you feel it’s not worth further investigation. While you might be able to reinstall their entire computer to fix the issue it’s not worth it, so a reboot seems like a good try. If the reboot happens and the error crops up again quickly you keep digging. If it goes away you let it be, until you have multiple instances to compare and contrast as to what is going wrong. After doing this hundreds of times in your career you learn to pick your battles knowing what are more likely to be solved. So sometime a reboot is the most economical solution.

It pains a techie to not know “why?” , so don’t think we take the reboot lightly. With everyone in the neighborhood calling us to help with their computer we can’t spend all day fixing just yours. So you have to understand, sometimes a reboot is all it needs.