theory - Engineering impossible bugs? -


how engineer impossible bug? possible?

take simple example: bob needs add commenting functionality popular internet blog. gets millions of visitors month , has thousands of posts. how implement feature if hired you?

you add form @ end of page responsible rendering posts, right? common sense. (forget security sake of simplicity)

however, solution assumes way how bob's blog works.

let's person made bob's blog hated bob. wanted make system no new features implemented without rewriting scratch.

how create system if 1 hated bob? aren't limited specific language, framework, operating system, server software, architecture, or anything. need provide working blog pages clients connect server.

also assume bob whatever tell him to. if has send in new hand-written blog posts carrier pigeon offshore processing center, it.

and before asks, no, not asking question because want screw on client. think of exercise. we're used engineering code isn't supposed break, how engineering code isn't supposed work? bugs inevitable, solutions equally inevitable? hard create inverted code write regular code? if can create code can't fixed, mean can create code can't broken?

because blog platform expendable, think sort of bug irreversibly cripples bob's web-presence have bug targeted @ either content, or @ bob himself. examples of placing terminal allows bob post in cage full of lions, or convincing internet ddos every blog written on same topic bob's blog.

that said, long bob citizen of free world free internet access in public cafes , libraries abounds, don't think ever possible introduce bug terrible bob's blog cannot published.


Comments

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

asp.net - Razor Page Hosted on IIS 6 Fails Every Morning -

c++ - wxwidget compiling on windows command prompt -