You are here
Home > Programming > Programmer’s Survival Tips – #2

Programmer’s Survival Tips – #2

Fallback Image

Never commit to anything without doing proper research first

This is probably one of the most frustrating situations for me. I really dislike it when non-programmers tell me how to do my job. What makes it even more frustrating is when such behavior comes from a really likable person. You are almost tempted to agree with them. But don’t deviate from your game plan. This game plan is called research. So, you need to do the following (there are different procedures here, but I’ll list the basics)

  • Always define the addition or modification properly.
  • Clearly define the affected systems.
  • Identify possible risks.
  • Ensure that you clearly understand what change needs to be done.
  • Document this change or addition in a change document. (The client must sign this)

These basic steps will at the very least ensure that everybody is on the same page. And most importantly, that you make the change correctly, on time and within budget. And lastly, the golden rule to never forget is this… If you understand it, you can code it!

Dirk Strauss
Dirk is a Software Developer from South Africa. He loves all things Technology and is slightly addicted to Jimi Hendrix. Apart from writing code, he also enjoys authoring books and articles. "I love sharing knowledge and connecting with people from around the world. It's the diversity that makes life so beautiful." Dirk feels very strongly that pizza is simply not complete without Tabasco, that you can never have too much garlic, and that cooking the perfect steak is an art he has almost mastered.
https://dirkstrauss.com

Similar Articles

Top