Saturday, December 27, 2014


After going back over my planning documents area and making a few changes bring things to where they should be, I think that I have gone as far as I can go with my company documentation.  At least for now.  I know that there are some research specific documents that I can add to my strategy area, but since I'm still a ways away from being a competitive force in the market, most of these things are probably going to change by the time I'm there.  This is a good area to have made note of and to keep watching.  For the immediate future I will continue to read publications to see what areas I might have forgotten about or skimmed over.  Aside from that, my focus needs to be thinking of new ideas, learning technologies that are going to make my products more competitive, and actually implementing my marketing strategies.

Sunday, December 14, 2014

Archive Maintenance

At first I thought this was going to be a bit of a useless task, but I found today to be fairly interesting.  I spent some time going over and organizing my reference material.  To be honest, I'm not really sure why I would think that this wouldn't be an important thing to do.  Most to all of what I do is based on my ability to access my reference material in a useful way.  I guess my point is, I've been taking some online classes that are in the form of videos they've posted.  I was trying to go back over the material looking for some specific information and didn't really know where to start since I watched the videos a while ago.  Then I remembered that they posted all their slides from the presentations.  So I went through and downloaded all the slides and found that they were pretty quick to browse and an informative overview of what the videos went over.  I found it so helpful that I went back to all of the videos and downloaded any slides that had been posted.  Now I have a pretty neat online/video reference area.

Wednesday, December 3, 2014

First Steps: Building a Portal

The corporate site has officially been started.  I decided to go with a peer recommendation for the compiler.  This was a pretty tense decision for a while until I changed my mind at the last minute based on what someone said.  I am surprisingly happy with my decision.  The interface is easy to read and I like how it works so far.  After getting past this hurdle, I've gotten some things done that I think will be good for my overall motivation.  What I have so far is pretty much placeholders and some tech demos.  Since this is just the first actual day of development, I think that's ok.  I can see a lot of things in the future that I'm not going to enjoy doing, but will definitely benefit me and my company in the long run.  I want this site to go well because if it's done right, it could be not only something that most of the general public sees when evaluating my work, but also what my employees will become familiar with.  There could be a lot at stake here, so I hope that things will continue to go well.

Wednesday, August 6, 2014

Research Efficiency

Learning a new technology is not an efficient business practice.  I think this is bothering me because I have a project in mind that I want to use this technology for.  Having a use in mind does help you learn the material, but new technology just can not be depended on for something that you need or what to have on any sort of timeline.  If anything, it might be helping me to learn too quickly.  All I want to do is get through the material, and find more material and get through that.  I'm not sure if this is obvious or not, but it's probably not the best idea to be thinking that far ahead while you're trying to learn something.  Unfortunately for me, I'm in too deep and I can't turn back now.  I probably could, but then I'd have to do the same thing somewhere else and that's just going to be a big waste a time.  So, when I say something isn't efficient, I guess it's a little about context.

Friday, August 1, 2014

Site Redesign

The redesign of the corporate website was a huge success.  Previously I had been using an image that I created just as sort of a visual device for seeing what my company could look like.  It actually still works pretty well as a menu page for the different areas of the company, it has a interesting presentation.  The new layout has a much more traditional feel, which I think people are going to respond to.  I think that I'll let the more progressive aspects at least start closer to the products themselves.  In addition to that, I think that the new layout will be a very interesting platform for a few technologies that I'd like to have available.  I have a few other ideas that could theoretically implement these things, but this is going to require the least amount of thought and new work.  I already have everything that I need and it will just be a matter of putting it together.  From there I can start to expand.

Monday, July 21, 2014

Time Waster

I found a new time waster today.  Scripting levels for games.  Yeah, obviously this is a fairly serious and important part of game development because that's how levels generally work.  But, once you get a few levels down and pretty much know where to go with things, you don't really need to think about having a full single player experience until your close to launch.  That's pretty much when I start thinking about other things and unfortunately, forget that I only have a fairly short single player game.  It was a pretty interesting discovery to remember that I could spend a little bit of time randomly scripting levels that I may or may not want to use in the final version of the product.  This is something that I can pretty much keep going back to since I don't have to use any of the levels that I think of and I already know how to make them.  All that I really have to do is think of a few new parts for what I've already created.

Tuesday, July 15, 2014

Staying Grounded

Sometimes when you're doing things that interest you it's very important to keep yourself grounded.  This means that when you find something new and exciting, you can't just start assuming that it's even useable.  I look at it this way, when I'm trying out something new, or unfamiliar in any way, I have to have an urgent business need for it.  Anything other than that is what I have to consider a fun hobby or an extremely risky investment.  This way, whenever you're working in a new area, you can keep in mind exactly what you want it for.  Assuming that you've labeled your business need correctly, this should be narrow enough to focus your attention to how you're going to benefit from what it is that you are doing.  As a sort of lucky side effect of this, you'll also have an extremely grounded view of whether you're going in the right direction or not and how likely it is that things are actually going to work out.  Without this, there's a pretty good chance you just might start to drift into an unnecessary journey through technical documents and lectures.

Tuesday, July 1, 2014

Business Need

I've determined a business need for learning new technology.  To be fair, it's not totally new technology, but I've needed for a long time to sit and and make sure that I'm doing things the right way.  At least the way that people who are successful do things.  It's one of those things where I can do all the basics and if I really tried hard enough, I could put something out there that works.  But this is sort of the point.  I don't want something that simply works, I want something that is going to seem both familiar and friendly to anyone that happens to stumble onto my site, or sites.  The working idea is that I'm going to create a sort of sales placeholder where I can advertise a product and try to generate interest.  When I decide to officially release something, it would also be where people can actually buy or gain access to my product.  Of course, if things go well, I will also be able to leverage my skills in who knows what other ways.

Thursday, June 26, 2014

Too Much News

I had a realization a little while back that I'm still kind of struggling with.  Sometimes it's ok to not read the news.  I'm still not comfortable with it, so I've been coming up with reasons as to why I can justify not reading the news every day (although I still read my subscriptions, that's not good).  I think that the real epiphany that I had is that the news is kinda similar.  I'm not leaving the industry.  I know a lot of things that are happening.  I do not need to know all the things that are happening.  Some stuff isn't even that important.  I know what the industry is generally like.  In some rare instances, I can even stay informed by merely skimming what my favorite news sources have to say.  I'm completely sure about any of this, but I've noticed that there are some benefits.  I have more time to think of new ideas.  More time to take classes and learn new technologies.  And of course, more time to market my work.

Friday, June 20, 2014

Clear Message

I have officially discovered the next needed avenue for my business to take, which happens to be actual sales of my product.  This means that I need to go out and find businesses that would be potential customers and sell them my product.  This sounds both at the same time fairly obvious and out of the ordinary.  Businesses today seem to consist of marketing campaigns that are so far removed from reality that they can be just a logo and name.  Unfortunately, things like take a lot of money and some sort of established presence.  I know that I have not only a product, but a series of products that people might not just want to buy, but to be a part of the development and marketing cycle.  The problem is that they do not yet know this.  It is my responsibility to inform them that they want to be a part of what I am doing through personal involvement and a clear, informative message.

Tuesday, June 17, 2014

Useful Things

Sometimes you use technology all the time without even realizing why.  I find it surprising sometimes when I find uses for things that I might not have exactly thought about, but wouldn't have done if they weren't there.  I think this happens a lot with the speed that things advance at.  This is sort of what I'm hoping will be one of my business strategies to work around.  Letting my ideas find their place in the world.  Obviously this isn't my only business strategy since I feel like I have a lot of fresh ideas and ways of doing things.  Yet, as you watch other, more successful companies release new products at a much quicker rate than a small company ever could, you can't help but getting a bit nervous about where you fit in.  And sure, just because you make something doesn't mean people will want it, but it's nice to have hope that you can try to find usefulness.

Tuesday, June 10, 2014

Required Progress

The marketing and management area of my company is a real job that needs to be done.  I have to say this because I'm an engineer and I've spent most to all of my time so far thinking of and creating products that my company could sell without actually selling any of them.  Sure, this could be considered part of my business strategy, or what I like to do.  The reality is that I have about one business document for each full product that I create.  This might be a bit of an exaggeration, but logically this just doesn't work.  So my new task for myself is to create a more real, specific set of tasks that can and will be accomplished.  This doesn't mean that I'm going to actually accomplish them, but I have to start moving my company forward.  I am not going to ever make any progress if I don't even try.  These are facts.

Wednesday, June 4, 2014


Confidence is the word of the day today.  I almost feel like this should be part of my business plan, but it is in no way effective at actually running a business.  I can't really expect to have to train employees from the very beginning.  Confidence to be proud of what you are doing.  To have faith in yourself and what you see as the right way to do things.  This does not mean being inflexible, this does not mean doing things that people don't like or want.  But it is going to be difficult to start anything.  To stay where you are.  That's why you can't change your way of doing things because you get nervous or you get some fancy idea.  Things may actually not work out sometimes, but if you position yourself properly, confidently, that shouldn't be devastating.  That way, when or if things do work out, you will be ready as well, having worked hard to get there.

Wednesday, May 28, 2014


The unofficial end to my strategy series was a document about avoiding distractions.  This reaches all of the major points that I noted as wanted to cover as part of the area, but does not mean that the work in the area is "completed".  Obviously, all of the documents can be expanded, added to, and in general, most of the topics can have more info, and specific, researched info.  As sort of an interesting coincidence, the last section was left pretty open ended.  It's simply a list of a few things that I could think of right away.  There's a good chance that if I maintain these documents that over time I will add (possibly) a fair amount to this list since the topic is pretty vague.  I think it will be interesting to see if I actually go back to this area or just sort of leave things where they are.  For now, this rounds out my strategy topic very nicely.  Collectively, these documents should give anyone that is interested a good idea about how my business sense has lead me to where I am.

Wednesday, May 21, 2014

Staying There

Another day, another entry into my "strategy" area.  This entry was all about how to get there and how to stay there.  The topic is surprisingly helpful.  I got the idea from an article I read online about business management.  When I started doing the guide (framework?) I thought that it was going to be fairly redundant.  I already have several documents about marketing and general business and product related issues.  I thought that this was a fairly unique work because it was a little more thought related than most of the other documents that I have.  This is kind of what strategy is actually about.  I'm not making a solid plan that's going to be followed immediately, this is more like my company motto area.  This is how I want my business to operate and the strange part is that I didn't even realize it until I was almost done.  Not to be misleading, I'm definitely not writing blog posts or anything, these are still factual technical documents, which I think adds to their impact.

Friday, May 16, 2014

Business Reality

So, I'm still pretty worried about not having a lot to do, but I think that I've come up with something that to help with that.  I think the harder I try to sort of "create" stuff to do that I'm not interested in, the more I'm going to be worried in general.  I know that those kinds of things aren't going to last.  I need to be honest with myself about the possibility that I may not be able to keep busy in terms of engineering work.  I am starting a business.  It's a little back and forth since I feel better about things when I'm doing the stuff that I actually like to do and feel good about doing.  Obviously this isn't a strict rule since the goal is going to be to make money.  But sometimes you aren't always so lucky to get what you want right away, so you have to be happy with doing things that will support what you enjoy.

Tuesday, May 13, 2014

Hard Work

Starting a business is a choice that I have made.  In order for me to have not simply wasted my time doing this, I need to understand what it will mean for me to be in business for an extended period of time.  I am not trying to win the lottery.  This is something that is going to be a part of my life for a very long time.  I have started working on having a process where instead of panicking when I come across a problem, I identify what it is and research all of the parts involved.  This is not so much a process, but how one would do pretty much anything worth doing.  I think that the real test is being able to stay calm long enough to know that the problem can be researched with the right mindset and approach.

Friday, May 9, 2014

Looking Ahead

You have to be honest with yourself as to what you want to get out of things when you're trying to start a business.  Even when things are going at their very best, I probably won't really be doing full-time coding.  I suppose that it would be possible to sort of create a position for myself that would consist of me coding all day long.  The reality of the situation is that I'm going to mostly be watching the market, working on new ideas, and managing my resources.  The resources would include both human and financial assets (since good employees are going to do good work).  This situation is going to require a lot of patience, especially since you sort of think about the technically details when you start a business, but have to consider the financial side in order to keep things going.

Tuesday, May 6, 2014


Time is something that I don't really need to think too much about, but I kind of need to be aware of to make sure I keep making good decisions.  I've seen a lot of references to the average age people are when they create a startup.  I don't have a lot of information about how much work people usually do to prepare for starting their company.  I'd say that my reasonable guess would be that I'm both younger than I should be and have less work put in than most people.  All this really tells me is that I need to be prepared to wait for possibly a long time while I get to where I need to be.  Since I don't know if it's even possible to reach this point, there are a lot of factors that go into my long-term planning.  I need to be realistic, but I don't need to be rash about anything either.  I enjoy what I do.

Thursday, May 1, 2014


I'm not going to talk about fund-raising, but it is essential.  There are many steps to go from learning how to design and create a product to having a large amount of money to support yourself and a way to keep supporting yourself through sales.  This is something that most people may or may not think of when they first come up with an idea for a business.  A bit of a hint, you may need to have a lot of bake-sales in order to get there.  Really, there are a lot of factors that one has to consider, both legally and physically.  There are only so many ways that you can make money when you intent to leave shortly.  In addition to that, there are only so many hours in the day to accomplish all of the things that you need to get done.  Good luck from here.

Tuesday, April 29, 2014

Trial and Error

With my current design and layout artistic ability, there is only so much that I can do at the moment in terms of interface presentation and my ability to create something that is technically modern-looking.  While trying to think of new product ideas, I have been spending more time looking at some of my complex projects and thinking about what that means in terms of functionality.  Until I learn more about how to better design a product, I am focused mainly on the tech demo aspects of the functionality and what that means for building a new idea.  This will largely give me more time to think of ideas and learn more at the moment.  If I create enough to know that I have the ability to make something work, I can focus more on the things that I need to work on like expanding my (eventual) market presence.

Tuesday, April 22, 2014

Design Hurdles

Thinking too much can be a serious problem when you're involved with design-related pursuits.  You make a design that you like and you can second guess yourself a million times.  In reality, it's part of the design process itself.  What if people won't buy my product?  What if it's too complicated?  What if somebody else has something that's just plain better than mine.  These are questions that need to be asked, but you have to keep making progress.  It's one of those things that can technically help you, but only to a point.  If you have any idea where that point is, or could be, then fortunately for you, you probably won't get there.  A good way to deal with these sort of mental hurdles is to keep telling yourself that you like what you have done.  It's difficult to ever place any sort of finality on a coding project, but you don't want to work harder than is reasonable.  Arbitrary goals and deadlines can be a big help to let you call something completed, even if it isn't perfect yet.

Tuesday, April 15, 2014

Technology Space

I have to decide where I want to stand on new technology as a method for actually expanding my business.  I know that new technology is going to be a part of my long-term plan, and to some extent it's going to be a part of my short term plan (especially with things like free libraries).  I think that I can implement what could be a fairly important new technology in several ways, but I have yet to consider if this is going to negatively impact my overall progress in any way.  The basics look like something that I would be able to do, but I haven't done any research into the surrounding ideology or implementation techniques.  This means that I may know how to get things to work, but I may not have a full understanding.  I think that I'm just going to do it anyway and see what happens.  I can always fix things later.

Friday, April 11, 2014

Professional Improvements

With the work that I'm getting to do for my new project I have also been fortunate enough to expand my vocabulary a bit.  Surprisingly, you don't really learn too many new areas or features very often.  When you're working, there are usually a fairly regular set of things that you use and major deviations from that are unlikely (mostly because you are more likely to plan projects with the features you are used to).  Just reading through manuals is not as productive as you might think because if it were included there, you would have learned it in the first place.  In addition to all this, I have several projects that I think could benefit from a slight vocab expansion.  And of course, who could forget the most important part of having a new feature set as part of my code base.  Hopefully I'm not making a bit deal over something that isn't much, but I have enjoyed being able to improve myself as a professional.

Tuesday, April 8, 2014

Slow Progress

Work is being done again.  I have a new idea that's outlined and everything.  So far, my initial progress has lead me to the conclusion that I could make this part last a lot longer if I put more work into planning things.  My actual plan consisted of about four sentences before I started writing code.  I should have books filled with my planning documents.  I should know every piece of the project, every potential problem area before I even begin to write code.  Writing code is not meant to be something you just race into without giving it much thought.  That's how you end up with products that lack features, how you run into dead-ends that you can't figure out, and a lot of other unforeseen problems.

Friday, April 4, 2014

Identify Competition

I wrote the outline for the competition guide today.  It's a document that outlines how you would go about researching the competition for any product.  This was actually fairly discouraging because I finally realized where my real work is going to be.  I need to have a competition document for each and every product that I make.  These documents will need to be updated.  I need to know something about how my products on an individual basis, fit into the market.  The market changes on a regular basis which means that the research will need to be maintained in order to even know that we are producing something that is going to do well, that is wanted, that will be around for a while.  There should be at least one person in my company that knows these things.  This is not advanced stuff.

Monday, March 31, 2014

Finding Customers: The Doc

The newest entry in my series of strategy-related documents is about how to find our customers.  Established companies have the luxury of being able to focus on their existing customers, while newer companies don't have that base to work from.  I can see finding customers as one of my first challenges towards being profitable.  I haven't actually gone over the specifics of how customers are going to be found, but created an outline for what would need to be done to reach them.  Again, since this is one of my goals for the strategy area, specifics can be added later to improve this process.  Things like, what works well, what doesn't work well.  For now, this should be a starting place to begin generating some ideas and at some point to get things started.  Every customer is going to help, whether they decide to return or not.

Tuesday, March 25, 2014

Considering How Customers Could Be Found

The newest entry in my series of strategy-related documents is about how to find our customers.  Established companies don't always need to worry as much about actually finding customers as much as having something that they appreciate.  I can see finding customers as one of my first challenges towards being profitable.  I haven't actually gone over the specifics of how customers are going to be found, but created an outline for what would need to be done to reach them.  Again, since this is one of my goals for the strategy area, specifics can be added later to improve this process.  Things like, what works well, what doesn't work well.  For now, this should be a starting place to start generating some ideas and at some point to get things started.

Friday, March 21, 2014

Customer Doc

Who my customers are is not a very complicated subject, not yet anyway.  I created a very quick document to go over a few basic concepts.  All of my products will at some point be sold to one of two very different groups.  These groups are almost opposites in every way and the products that will be sold to them will pretty much be opposite in every way.  Just doing some light brainstorming, I can see how there will be no overlap, even if a product is sold to both groups because of their opposite interests.  Right now, this isn't a very useful document.  I can see a lot of information being added to it to help make certain ideas and concepts more clear.  The document doesn't need any additional information, but I will be looking at it again.  One can never underestimate the usefulness of a good template.

Tuesday, March 18, 2014

Market Trends

I starting going over market trends as my first entry into my strategy area.  I didn't actually go over any market specifics, like companies that are doing well or products that are popular.  I think that this would be a very helpful companion piece(that I should work on soon), but I made more of a template that would probably not change a whole lot over time.  Eventually all of the products and companies that I would list in a market trends document are going to change.  Instead of going over what is popular or not at the moment, I focused more on what is popular in general.  What types of things get people noticed, what loses people's attention, and from there you can pretty much see how what you are working on is going to fit into the market.  Obviously you would have to use a bit of your own research to bridge the template gap, but that could be a goal of the companion document.

Wednesday, March 12, 2014

Stretegy Area

Strategy is my new official subsection of the business_documents area.  Strategy is probably the most obvious omission from a business perspective that I have left out of my company so far.  Obviously in simpler terms you make a product and you sell it.  That's pretty much the only way to make money.  If you're going to take what you do seriously, there might be some risk involved at some point.  A strategy is going to help you stay focused and be prepared for some sort of long term investment in yourself.  It is possible in the technology industry to not have things to do or new ideas to sell.  A lot depends on the product you are making, interest, and your strategy going forward.  So far, I have a list of goals that should help guide the documents for the strategy area.  With any luck, this should help me and customers to feel better about my company.

Friday, March 7, 2014

Launch Doc

I made a document about my product launches for the first time today.  It's important to think about what a customer is going to see when they want to have some part in your company.  I took some general notes about what's going well and what isn't when someone actually tries to use an application for the first time.  I also wrote down a few thoughts about how these products are going to be profitable.  I have scattered down in a lot of various places other thoughts about pricing, but it's pretty repetitive and not very useful.  I've thought about the best way to actually deploy a product before since my build area has a few things aimed towards that, but I think it's going to be a lot more useful to have all my related thoughts and procedures in one place.

Monday, March 3, 2014

Release Schedule

I created my first product release schedule today.  It is not anything like what one might expect out of a product release schedule since it does not include any exact dates and it focuses on a lot more information than you might expect.  Typically you would think of one product release at a time, where this schedule goes over the general grouping that I would expect to release all of the products that I have been working on.  The main idea here is to kind of see what I will look like(hopefully) as things start to actually develop.  There are a few places where you can see how things will look good, and other places where the releases are lacking a little bit.  This may or may not help with generating new ideas, but it does look good as a way to get people interested in my company.

Tuesday, February 25, 2014

Main Site Sketches

After some quick consideration about the corporate site, I decided to do a quick follow-up.  Just browsing through my company materials I found a pretty rough sketch of what the main site page could look like and a product list that is broken up into the appropriate sectors that each product will be a part of.  The main corporate page isn't much to look at, a title, logo, then company titles and logos for each of the companies that will represent my product sectors.  The product list I've been maintaining for a while actually gives some pretty interesting insights into how the products could start to come together into their various sectors.  Look for good things from the product list.

Wednesday, February 19, 2014

Thinking About A Corporate Site

The corporate website is something that is going to need a lot of attention.  After making a fairly brief layout doc (since it's mostly notes without a lot of description) I realized that almost everything that I currently refer to as my company will be part of my corporate site.  I made the important distinction that there will have to be both a publicly visible aspect and a private aspect.  This would mean that there's going to be a site that will just be for customers who want to buy our products and there will be a site for employees that are trying to build and sell the products.  Overall, the site is going to be fairly large in order to cover all of the necessary information.  This is only the minimum amount of information that can be included, since I don't have any design specifics, graphics, layout considerations, or any other technical details.

Thursday, February 13, 2014

Things I Need To Do

Spent some time going over my whole company today.  Well, everything except for the actual products since I spend enough time with them.  I managed to make a few improvements to my promotional area, noted a few projects that aren't there yet.  I went over my todo list already and added some rather minor changes.  I think that it was hard to not notice that I have a lot more time and effort invested in actually working on my products and not a whole lot of effort towards trying to get them to be profitable.  I think that as I start to spend more time going over my non-technical documents I'll start to get a feel for where I am, or could be financially.  Obviously I could just sit in a corner and design all the time, but that doesn't mean it will ever be profitable.

Tuesday, February 4, 2014


I started a new section in the internal documents part of my company.  Right now this is sort of a general purpose area for documentation that I don't want the general public to see but doesn't really fit into the typical engineering requirements.  I added a new section to the area that I'm calling "planning_documentation".  As the name suggests this is just for documents that relate to the general planning of the company.  Since I already have a "business_documents" folder, that sort of implies that it's mostly for engineering planning.  This could be confused with my "todo" list area which is about specific tasks and functionality.  I think that the purpose should be obvious by default, but so far all of the documents are about how to use products, what way engineering could go with them in general, and sort of where the company might go in a general engineering direction.

Tuesday, January 28, 2014

Misc Research

I'm not sure how well this will actually apply to what I've been doing, but I did some thought research about stores that have nothing to do with my industry.  There were a lot of obvious differences besides the topic of the store.  To start with, most of the products take significantly less time to obtain, whether that's crafting it or buying.  So, here I had to do some vague ratio-based math to estimate things.  I thought that my overall variety was doing fairly well according to my calculations.  Obviously my visibility and location were horrible compared to the places I visited.  I thought though that the biggest difference was the sort of niche items.  These would be things that someone would want to pick up and hold when they first walk in.  These often entertain children while their parents look at other things.  This seems like a direction I should consider.

Friday, January 24, 2014

Marketing Needs

The final part of my marketing documentation mini series is going to finally go all the way into the actual marketing aspect of documentation possibilities.  Now, keep in mind I have only done the functional uses and templates for one product so far, so most of this is about advantages of going in this direction.  When I start to have pamphlets, flyers, and advertisements that tell people exactly what they need, why they need it, and in a fair amount of cases, what it is that I'm trying to accomplish, that's when I'm going to start to turn the corner and be able to be taken seriously.  People want to spend their money on things they need or feel will make their lives better.  Creating something that the average, apathetic consumer wants to view is much different from even writing technical documentation that engineers need to read.

Wednesday, January 22, 2014

More Doc Needed

After what I feel is the success of my previous post, I think that it's appropriate to elaborate a bit more about the benefits that I could see by creating more documentation around the marketing and useability of my products.  As a fairly general statement I could start with the fact that code by definition can pretty much be moved around, combined, and reshaped within reason.  This general area has not even been noted (although I think I mentioned somewhere that I could do this).  Actual ideas are going to lead to thinks being accomplished.  Even having the idea out there is going to make things like generating interest possible and it will keep the idea fresh in my mind to consider.  Look for more about marketing focused ideas in my next post.

Thursday, January 16, 2014

Creative Functionality Expansion

Today I did a bit of documentation that was primarily for marketing purposes.  This is something that I don't really waste my time doing since if you have something like a necklace, you pretty much just need to show a picture of it to sell it.  With some of my stuff having a help section or rules, directions, that sort of thing would be informative.  In this particular case, I actually got to explain a few technical aspects of the product that could actually be completely overlooked without something explaining them.  This not only makes my product more attractive, but it actually makes it more functional.  Overall, I'm pretty proud of the new feature to my product.  I think that functionally, it's something that's going to go a long way and if popular could see some fairly significant new areas that could build up around it.

Monday, January 13, 2014

Need Ideas

I have another new idea based on things that I do with my computer while I'm programming.  Now, I know this is a fairly specific, narrowly focused field since I am the only person that I know that would find this useful.  I think that even if there isn't going to be a large market for my ideas, the technical accomplishments will be worth going after anyway.  I have to assume to some extent that some of the things that I make just won't be popular.  When I'm able to combine useful technical features along with something that may or may not do well, then I can use these skills to improve all of my other products.  Obviously many of these improvements would be implemented anyway when enough  customers can try out my product.  Some of the most obscure features might simply be overlooked by people that don't really consider things like that anyway.

Friday, January 10, 2014

Company Sizing Guide

After going over the company career guide I decided that it would be a good idea to have a companion sizing guide.  I was doing a lot of thinking about how my products relate to my company and how this is going to affect the overall direction of what I do with my life and decided it would be a good idea to put this into some neat formulas.  I think that there's going to be a lot more stuff that I need to do that's very similar to this.  I tend to focus mainly on the technical aspects of my work, but if I'm ever going to have a successful company I have to consider all of the possible aspects of the business.  At some point it might even be possible to have a business need for the technical work that I do.

Tuesday, January 7, 2014


While following the theme of not really getting a whole lot done, I did some broader company re-organization work.  Basically, I was starting to accumulate a lot of projects that didn't really fall under my "People" sector or my "Security" sector, so I was generally just adding them to the "Security" sector anyway.  I took all of the out of place projects and started a new sector called "Enterprise".  This term is actually general enough to pretty much work for all of the projects that I've been accumulating.  In one way or another the goal of all the projects is to somehow be sold to a business.  This could protect their interests, it could be a tool for creating products to sell, or it could improve their general corporate experience.  I think that the best part of knowing the general area that products belong to is that when you're thinking of new ideas you can more clearly see what you already have and where might be a good area to focus on.