August 1st, 2009 by admin
I have discovered that many software engineers can develop working programs, but do almost no real engineering design. I have also encountered a preponderance of cryptically written functions, clutzy software abstractions and strange spaghetti code. In the early years of computing, folk were forced to draft out their software designs, contemplating many small details before they ever sat down in front of the PC. However, when such design-as-you-go software development becomes standard practice, then you’ve got the makings of complete chaos. Have loads more information on . Here are eleven tips to practice that may help you to feel strong and authentic, and will help you be understood as a person of authority and trust : one. Before you give your speech, get a comical tale from your audience.
“Folks, I looked at the bowling scores from your event yesterday. In part, this problem is also rooted in the malleable nature of PC software. No self-respecting civil engineer would design a bridge by slapping girders together till he has something that works ; after all, if the bridge falls down, it might take lots of time to reconstruct it. Because of this, I suspect that hi-tech firms need to give software engineering the status that it merits. They need to develop a true culture of methodical software design, rather than just settling for “whatever works.
No tags for this post.
Related posts