How To Write Production Character Code?
We often hither the term "production lineament code" , simply about times inwards interview where interviewee asked to write production lineament code for a particular function,sometimes give-and-take betwixt developers as well as programmers as well as sometimes during code review. I know most of y'all familiar amongst the term but for those who wonder what is production lineament code inwards uncomplicated damage its code which tin give notice comport the evidence of fourth dimension inwards a production environment.
We all prepare code inwards development, hence evidence inwards QA as well as lastly it gets released inwards production. But at that spot are a lot of departure betwixt evidence as well as prod as well as if y'all lead maintain non coded taking prod environs inwards heed most probable code volition neglect inwards prod or resultant inwards exceptions.So what makes production environs dissimilar than evolution environment? Here are few things which I noted:
1) Production is all virtually load which volition disclose concurrency issues, charge issues, retentiveness as well as CPU issues.
2) You volition instruct a lot many scenarios inwards production that y'all mightiness lead maintain idea inwards development. If mean value through procedure is non applied than most probable those scenario has non handled inwards production.
3) Different data input or wrong data, 1 of the classic problems inwards production is the information which gets input to your program, live it from the upstream organization or whatever other house y'all volition instruct all form of information as well as if your programme doesn't handgrip those real probable it volition suffer.
4) Boundary conditions, this is simply about what related to inwards a higher house bespeak information as well as scenarios but most of the boundary status e.g. null, empty etc exposed inwards production.
So if a code is written all these things as well as potentially domain specific things as well as tin give notice sustain evidence of production than it called a production lineament code and believe me it takes a lot of experience, science as well as mean value through procedure to write production lineament code non simply inwards get-go fourth dimension fifty-fifty afterward ii or 3 iteration but every bit a developer nosotros should ever strive for writing production lineament code inwards the get-go attempt.
Now let's encounter how nosotros tin give notice do that, what are the things nosotros should locomote past times on inwards mind:
1) Get your requirements right, sympathise the work , beak to user or work concern somebody every bit much every bit possible this volition attention y'all to honor dissimilar scenario every bit early on every bit possible. Many times work concern or user does non tell y'all everything it's non their error but it doesn't come upwardly inwards heed right through. So if y'all are often speaking, discussing as well as presenting solution to them most probable they volition inquire questions, give feedback which eventually disclose to a greater extent than scenario as well as subtle details. Here sense plays an of import role. More sense or domain cognition you, much ameliorate code y'all volition write.
2) Think through, Think through as well as Think through. There is no substitute of this, it is to a greater extent than of a science as well as fine art than scientific discipline but y'all volition instruct concord of this when y'all instruct to a greater extent than experience. For example, if a user says that y'all demand replay capability inwards your program. You should live able to mean value of all possible scenarios where y'all demand to replay as well as what could live required for that, what would live a side number of that. Does replay would live requested, what if the requesting organization went downward again, volition y'all live able to re replay etc.
3) Boundary condition, ever mean value that y'all volition instruct bad input , y'all volition instruct zero or empty, minor or real large numbers, the role may instruct called at the wrong fourth dimension etc. y'all tin give notice instruct rid of this past times writing the unit of measurement evidence for each boundary condition.
4) Concurrency, this is is the major culprit as well as large work which exposes itself inwards production when due to charge multiple threads gets triggered as well as access your programme concurrently. With the high-speed depression latency electronic trading organization as well as amongst many other coffee systems where its requirement to lead maintain a concurrent application this tin give notice entirely live addressed past times proper blueprint , if y'all instruct the blueprint right y'all volition prophylactic other wise y'all volition demand to comport the hurting of redesigning or rewriting code. You tin give notice every bit good disclose concurrency number past times doing charge testing inwards early on QA cycles.
5) Exception handling, this is the past times far most of import feature of production lineament code, it must live able to handgrip an particular scenario inwards clear cutting predefined way. The whole programme should never live crashed due to 1 unmarried bad input or scenario.
6) Recoverable, code should live able to recover itself inwards the instance of premature closing or crash.
Thank you.
Further Learning
How to write ameliorate comments field coding
Komentar
Posting Komentar