Carlos Santos's Library tagged → View Popular
How To Write Hard To Test Code & What To Look For When Reviewing Other Peoples Hard To Test Code
"The ability to write hard to test code is innate in every developer form the moment we have built our first “Hello World” application. It is so automatic that we do not even know when we are doing it. On the other hand writing testable code requires that you un-learn this behavior. In this tutorial you will learn how to recognize the red flags in the code and what are the common solutions for them. We will look at sample code representing common development practices and look into subtleties why this code is hard to test and how to fix it. The goal of the tutorial is to arm you with knowledge of how to write code which can be tested using small focused tests."
Jay’s Not Here » Blog Archive » Expertise
S. Sonnentag. Expertise in professional software design: a process study. The Journal of applied psychology, 83(5):703–715, October 1998.
Google I/O - The Myth of the Genius Programmer
No wonder the SVN guys want to destroy the myth of the genius programmer :-)
11 Personal Programming Assumptions That Were Incorrect « While I Compile
Writing beautiful software as an act of craftsmanship
It’s taken a LONG time for me to get it through my head that it’s just another financial investment, where you want to get as much as possible while giving as little as possible. However, although I know it intellectually, I still don’t ‘get it’.
Contratos e Scrum: The Good, The Bad and The Ugly
Segundo mirwox, tem algum material sobre previsão de desenvolvimento
The speed, size and dependability of programming languages
Nice comparison of programming languages (serious).
Philip Greenspun’s Weblog » Ruby on Rails and the importance of being stupid
My enthusiasm for this story has nothing to do with bashing Ruby or Rails. I like this story because (1) it shows the fallacy of credentialism; ... (2) it shows what happens when a programmer thinks that he is so smart he doesn’t need to draft design documents and have them reviewed by others before proceeding ... (3) it shows that fancy new tools cannot substitute for skimping on 200-year-old engineering practices and 40-year-old database programming practices, and (4) it shows the continued unwillingness of experienced procedural language programmers to learn SQL
The Third Bit » Blog Archive » Talk on Empirical Software Engineering and Scientific Computing
"The slides for the talk I’m giving today at the NRC on empirical software engineering and how scientists actually use computers are now up on SlideShare." snippet:"What Hurts? Lack of documentation was the #1 complaint for over 40% of respondents, and in the top three for almost 80% …but ranked second to last in list of where respondents spend their time"
-
The slides for the talk I’m giving today at the NRC on empirical software engineering and how scientists actually use computers are now up on SlideShare.
MOdeling LAnguages | The portal for software modelers
The main goal of this blog is to discuss how modeling can improve the productivity and quality of software development processes.
In particular, I'll use the blog to talk about how/where/when modeling should be used (and how/where/when NOT), announce modeling-related news, explain existing modeling techniques in a way that non-experts can understand (so that they can also evaluate the benefits those techniques may bring to their development team
SEED: Software Engineering Evidence Database
Welcome to SEED: Software Engineering Evidence Database
Select a topic on the left to see summaries of evidence-based software engineering studies.
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in Software...
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo
