Software Engineering
Get flash to fully experience Pearltrees
If ever there was an irresistible programmer’s platitude, it is that code-reuse is invariably a good thing.
The Framework Myth
Technical debt (also known as design debt or code debt ) is a neologistic metaphor referring to the eventual consequences of poor software architecture and software development within a codebase . The debt can be thought of as work that needs to be done before a particular job can be considered complete. As a change is started on a codebase, there is often the need to make other coordinated changes at the same time in other parts of the codebase or documentation. The other required, but uncompleted changes, are considered debt that must be paid at some point in the future. Common causes of technical debt include (a combination of): Business pressures , where the business considers getting something released sooner before all of the necessary changes are complete, builds up technical debt comprising those uncompleted changes
Technical debt - Wikipedia, the free encyclopedia
managing software debt
Every work day Facebook is safely updated with hundreds of changes including bug fixes, new features, and product improvements.
How Facebook pushes updates
7 Myths of Entrepreneurship and Programming
See, Pivotal Labs quietly helps dozens of the fastest-growing tech companies in the world, including freight trains like Groupon and Twitter. If your start-up needs to get good coding done quickly, as in lightning fast — or if new hires need to get good at coding quickly — top venture capitalists are likely to look over their shoulder and confide: “Call Pivotal Labs.”Release Management Done Right - The Daily WTF
I was having lunch with a colleague the other day when his phone rang with the distinctive office ringtone.