As developers, we’re naturally obsessed with details, conventions, and semantics. There are only a few professions that I know of that will take the time to avoid moderate compromises like using conditional comment hacks or failing W3C’s auto-validation services; we’re in league with stalwart saints and by-the-books building inspectors.
If you don’t deal with bad feedback it can disrupt, slowly corrode, and in the end, kill your creativity. If you’ve ever said "Yes, I can change that" and know deep down inside of you a little bit of your creative soul died, then this article is for you. We’ll tackle negative feedback and learn how to combat it. You’ll discover the 12 ways to manage feedback and keep your creativity alive.
There are many services out on the web for online collaboration, but there’s no doubt that Google Docs is rapidly becoming one of the more popular brands. Google Docs is free, web based (i.e. cross platform), and quite simple to use. But that doesn’t mean it lacks features.
Whether you’re a regular user or have just been thinking about trying it out, here are the top 6 tips and tricks to help you get the most out of Google Docs.
1. Chatting in Google Docs
Everyone needs a website made, but not everyone can talk “tech” like we can. From the farm owner in Indiana to the brain surgeon in Malaysia, we quickly see that employers can come from all walks of life. Learning how to carry on a compelling conversation about web development is a paramount skill that all web developers should possess if you want to keep the checks coming in. Maintaining your audience’s interest and gaining an accurate picture of what they truly need to get done can prove to be a challenging part of any web development project, but here’s a few tips that might help a bit.
Feature creep, also known as scope or requirement creep, refers to unforeseen requests for additions and changes that are outside the project scope. It typically happens due to inadequate requirements gathering, poor initial planning, and an unclear protocol for change implementation, among other things.
In this article, I’d like to discuss eight tips and suggestions, based mostly on my experience, to help minimize and manage the effects of feature creep in your own projects.
Being at an age where I’m just beginning to carve my path in the real world, I tend to have many peers and co-workers who constantly think about making an income besides sitting in front of the computer eight to ten hours a day in a windowless room.
I’ve had thousands of conversations about initiating startup companies, selling IT products or services online, creating profit-generating web applications (like a derivative facebook site), and putting up blogs. Eventually, I began to see characteristics that I feel are needed in order for your own project to succeed, and I present them here.