|
| Featured Contents |
| Question of the Day |
|
| The Voice of the DBA |
Daily Coping Tip Find a way to craft what you are doing to give it more meaning I also have a thread at SQLServerCentral dealing with coping mechanisms and resources. Feel free to participate. For many of you out there working in a new way, I'm including a thought of the day on how to cope in this challenging time from The Action for Happiness Coping Calendar. My items will be on my blog, feel free to share yours. |
Writing Before Reading Coding is one of the few (or maybe only) places where we learn to write a language before we learn to read it. Many of us get started in some way by working through exercises, looking at very small snippets of code and then starting to write our own. Perhaps that's because we experiment by changing the behavior of the computer, which naturally takes some writing work on our part. Perhaps we can do better, and should to better. Perhaps we would become less susceptible to the Not Invented Here (NIH) stance that so many developers seem to take. Not with major projects, but often with small sections of code or libraries, preferring to structure something new than re-used (and take the time to understand) what's already there. This isn't to imply that most developers need to write their own code or don't work to understand others, but often they prefer to rebuild something in a way that is more familiar. It's a form of the Mere-exposure effect, and it sometimes leads developers to prefer certain patterns, tools, platforms, and more. Perhaps it's the opposite of the shiny ball syndrome, which leads people to chase the newest thing available in their area. I know there are plenty of developers that copy and paste code from the Internet as well, which might seem to be a way of getting around NIH syndrome, but I think many people do this when they find code that solves a problem. Even if they don't understand how it works, they'll seek to reapply that same code to a new problem. I do think reading code is hard. In some sense, it sucks. I'd often prefer to understand the basic inputs and outputs, perhaps rewriting the code to work in a way that's more comfortable for me to understand. Maybe I better understand my own code, maybe I'm falling victim to the IKEA effect (I'd rather depend on my own software than someone else's), or maybe I'm just being lazy. There are plenty of articles on how to read other people's code, and I am trying to get better at this. I do try to debug and reason out how queries are written that solve problems in the forums. I may break apart queries and try to understand how someone has used a window function or a CROSS APPLY in a certain way. It helps build my skills, but it also helps me learn to better read other people's code and perhaps carry that skill into the future. Steve Jones - SSC Editor Join the debate, and respond to today's editorial on the forums |
|
| Featured Contents |
