Streamlining communication
You often hear about companies or people that don't communicate enough. This is frustrating because not enough information is flowing back and forth between key roles, and when information is needed it simply is not there. There is a point in which too much communication can be just as costly or even more costly. The question is where do you draw the line to determine there is too much communication? Joe Spolsky from Inc. magazine asks how hard could it be to streamline communication?
When was the last time you scheduled a meeting and invited eight people instead of the three people who really needed to be there simply because you didn't want anyone to feel left out? When was the last time you got into a long discussion over the color palette for the new brochure with a programmer, who has nothing to do with the brochure but sure knows that he doesn't like orange?
Joe Spolsky believes these are symptoms of a common illness: too much communication.
Why Web developers must understand business too
I see and hear about it too often. The typical stereotype of a Web developer or software engineer is a pocket-protector, glasses, algorithms, socially awkward and tends to be an introvert. These individuals are generally portrayed as out-of-touch when it comes to how their work truly has an impact on the business of their company. The guy portrayed to the right still rings true in modern pop-culture on what a nerd, Web developer or software engineer is like.
During my tenure at Ball State University I primarily studied code, applications and databases. I was completely on my path to Nerd City (does not really exist...I think). I opted to also study Information Systems Management to get a better feel for how IT and software engineering really impacts business. I actually saw quite the dynamic between most engineers I was studying with and the students that took the Information Systems Management courses. The students in IS Management generally understood practical business applications of IT and software engineering more than those who did not study IS.
Why is this important? I am always trying to find ways for the work I do to have a positive impact or effect on my company and our clients. Understanding practical business elements of a project it harnesses my focus to deliver more reliable code in the end. Many times Web developers and software engineers can get so hammered by the details of classes, objects, third-party applications, algorithms and the question of "does it work" rather than "why does it need to work"?
If you are in Web development or software engineering try to take a moment on the next project and think why does this client need this feature? The answer will almost inevitably give you more focus and a better understanding of what you need to do. The steps will become more clear on how to get to the end result. The question of "does it work" is still important in the end as you don't want to deliver a product that simply fails, but the question of "why does it need to work" will expand your insight on a project to catch potential traps or better methods to deliver a better product.
Brushing the dust off on .NET development
I will be the first to admit that over the past four years since graduating from Ball State University my path in programming has steered me away from .NET. This wasn't necessarily a personal choice. My first position developed their proprietary CMS in ASP Classic VBScript which I took the time to learn how the code worked and ended up becoming quite proficient in it over the past several years. When I started my position at Fusework Studios I continued to write in ASP Classic because that's what I had become accustomed to, and at the time it seemed simpler to stay in that realm.
For some time that's where I became comfortable. It was definitely within my comfort zone. Over the past several years I have had only a handful of projects that would venture into the realms of PHP and .NET development. Each time that I dared to enter this unfamiliar or old territory doubt crept into my mind, but thankfully I have been able to be accomplished enough that I was able to develop and succeed on each project.
Recently on a project I have had to update my personal and work computers with the latest Microsoft Visual Studio 2008 package. I disassembled a compiled DLL file that I was not familiar with only to find that the modifications needed done to the site needed so much more than this DLL was structured to do. I had two choices:
- Modify the DLL extensively to get the end result.
- Take what I needed from the code in the DLL and write a new application to accomplish the client's goals for the site.
I opted for number 2, and it was invigorating to be able to brush the dust off a long-lost development approach after working with ASP Classic for so long. Mike Lacey, the other Web developer at Fusework Studios, is a big supporter of .NET development and kept telling me "welcome home." It felt good to take on a new challenge. To do something different. To create something new. After going through the motions for some time in ASP Classic it felt great to step out of my comfort zone and try something new. I think inherently that's all a programmer or engineer really wants to do at heart. We want to create. We want to create something new. Even now my mind is reeling over what I can try next. The great thing is...I can't wait.
Steps to moving domain name servers
I am currently working on an internal project to move hosted sites to a new server. In the process we are moving domain name servers to gain more control over what records are involved with the domains we are hosting. This takes considerable planning and forethought as we don't want our clients to experience any down time with email or their web site.
Here are some steps that need to be taken when moving domain name servers:
- Gather a list of domains you control you wish to move
- Obtain a list of all A, CNAME, MX and other records under each domain
- On your local or hosted DNS provider check and double-check the records as you enter them for each domain.
Assuming there were no typos, mistakes or missing records when you're done you should have no interruption of service even though DNS has moved. The new DNS will be pointing to the same locations for your sites as before, but you should now have more control over the DNS.
Fusework Studios’ agile approach to a web based strategy
As Fusework Studios shifts its focus to a digital agency primarily focused on a full-service partnership with its clients the need to reinvent its web based strategy became apparent. The web site has served its purpose over the years, but in order to branch into other areas of service for Fusework Studios' clients the web site needs to be changed.
There is more to this than meets the eye; however, Fusework Studios is implementing a full web based strategy with a focus on many different aspects of internet marketing. The web site is not the primary focus nor is it the most important goal for Fusework Studios.
More on Fusework Studios' goal will be revealed throughout the day as the entire staff comes together to implement and develop the web sites that are all a part of its internet marketing strategy. The concept is simple. Fusework Studios is determined to win search for specific keywords to create an edge on search engines with relevant content. All of the sites involved in this package will funnel the traffic to www.fuseworkstudios.com with points of conversions on each site as well.
I am excited to be a part of the team that is taking an agile approach to their internet marketing and web based strategy. I am confident that this will yield excellent results as we measure the analytical data in the near future. Tomorrow be a part of the process and learn more about the experience by following Fusework Studios on these sites:
The stuff you don't see when developing a web site
I am currently, as you may already know, building a new web site and personal blog at a different domain. I purchased hosting and downloaded the WordPress installation from WordPress.org. It may seem simple enough to download the files, upload them to the server and presto I have a web site but there's more to a site than meets the eye.
- Preparation. The most successful web sites are built with a purpose in mind. What's your goal? What's your target audience? How do I want to be found through search? What are my steps for search engine optimization?
- Strategy. Now that some of the core questions are answered the next step is how we achieve these goals. Developing a site map is a great starting point. You must determine how users will flow through your site. Choosing an analytical engine to measure data from your site is important. What are the conversion points through the site?
- Implementation. Now that the strategy has been laid out from start to finish it's time to implement. In the case of a WordPress site, I now know what types of plugins I will need and what should be in my side bar. This is usually what most people see on the site. This creates the common misconception that just anyone can build a web site and make it successful.
- Measure and adjust. The site's been live for an amount of time that you have determined through preparation and strategy. It's time to analyze the data. Find your strengths and weaknesses. Improve the site based on the information at hand.
Have my blog sent to you
Social Media Tools
Categories
- Blogging (13)
- Business (15)
- Career (22)
- Family and Life (44)
- Internet Browsers (1)
- Internet Marketing (16)
- Leadership (3)
- New Media (1)
- Parenthood (2)
- Politics (3)
- Search Engine Optimization (1)
- Social Media (22)
- Social Networking (19)
- Teamwork (1)
- Web Based Strategy (5)
- Web Development (6)
Archives
- March 2010 (3)
- February 2010 (8)
- January 2010 (6)
- December 2009 (4)
- November 2009 (4)
- October 2009 (7)
- September 2009 (26)
- August 2009 (14)
- July 2009 (3)
- June 2009 (3)
- May 2009 (5)
- April 2009 (7)
- March 2009 (7)
- February 2009 (4)
- January 2009 (4)