And there are some programmers that approach being brilliant within the
tunnel-visioned silo of their project’s *end* goal, but have never had
experience with the big picture on how EVERYTHING needs to play nice
together, and may not care or ever learn.

 

Kind of like one developer years ago that wrote what appeared to the
business managers as a fantastic point of sale system, but it kept a local
journal/file with ALL transactional data to facilitate returns and credits.
This was before the OLTP on a central database, stores were polled twice
weekly for sales data.  All POS stations would share their journal with
others in the same store, and this proved a 100% solution to handling the
returns and credits issue.  But never did develop in a way to automatically
truncate the journal/log after a reasonable time ( 3 to 7 days, refund
period ) and proved a HUGE security risk of customer credit card information
as months of data would accumulate on the hard drive before anyone ran a
manual database maintenance routine.  Simple security procedure to implement
into the code but was never considered as the developer was never concerned
with anything outside of his silo, and it wasn’t within his manager’s silo
either …  sad reality of the real world.

 

Erik Goldoff

IT  Consultant

Systems, Networks, & Security 

'  Security is an ongoing process, not a one time event ! '

From: Andrew S. Baker [mailto:asbz...@gmail.com] 
Sent: Monday, May 31, 2010 12:45 PM
To: NT System Admin Issues
Subject: Re: Applicability of the OSI model (was: Big Changes)

 

Not likely.  

Besides, have you not noticed a downward trend in skill levels across the
board?  We're just not making IT professionals like we used to...

-ASB: http://XeeSM.com/AndrewBaker


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to