The clean coder12/13/2023 ![]() ![]() You must understand what problem you are solving and understand how to solve that problem. Nothing will drive facts and values into your head faster and harder than having to communicate them to people you are responsible for.įirst, your code must work. During this remaining 20 hours you should be reading, practicing, learning, and otherwise enhancing your career. You should plan on working 60 hours a week. It is not your employer's responsibility to train you, or to send you to conferences, or to buy you books. It is not your employer's responsibility to make sure you are marketable. They should ask themselves how it happened and take steps to prevent it in the future. Releasing code that you don't know works is unprofessional.Įvery time QA finds something the development team should react in horror. This behaviour is just plain lazy and irresponsible. They send them code that they haven't thoroughly checked. It is your responsibility to get as close as possible to it. As you mature in your profession, your error rate should rapidly decrease towards zero. You cannot simply keep making the same errors over and over. Apologies are necessary, but insufficient. However, you must be accountable for errors even though errors are virtually certain. Software is too complex to create without bugs. ![]() Here are my highlights from The Clean Coder, a code of conduct for professional programmers. What does it mean to be a true software craftsman? ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |