...is not a complaint at all. "It's too hot in here". Or "It might be more comfortable if we cranked the A/C".
Both say the same thing, but the latter presents a possible solution. Anyone can complain, but it takes self control and positive attitude to make a successful complaint.
It's 9.45am, Tuesday morning. You've just finished a second cup of your favorite roast and you're ready to make something happen. If you're anything like me, you're ready to put those fingers that do 85 words per minute to use and start firing away at Visual Studio. But, have you stopped to gather your thoughts on the story that you are writing? I was inspired by this post by Seth Godin (marketing type) to reflect on my habits as a software developer.
In software, understanding and groking the story is the most important part of the job. If you don't understand the story that your end user has to tell, then you had better get it before plunking away at the keys. It's not uncommon for your client to not understand their business. Just because a company has a process does not mean its documented and/or understood. Getting and understanding the story sometimes usually supercedes the challenges of writing code.
Push back on the demand to write code if you're not supplied the appropriate details. It's better to write no code, then to write bad code.
