Home
Shrutarshi Basu's Library tagged → View Popular
Semantic Versioning
"In systems with many dependencies, releasing new package versions can quickly become a nightmare. If the dependency specifications are too tight, you are in danger of version lock (the inability to upgrade a package without having to release new versions of every dependent package). If dependencies are specified too loosely, you will inevitably be bitten by version promiscuity (assuming compatibility with more future versions than is reasonable). Dependency hell is where you are when version lock and/or version promiscuity prevent you from easily and safely moving your project forward."
Word Processors: Stupid and Inefficient
"The word processor is a stupid and grossly inefficient tool for preparing text for communication with others. That is the claim I shall defend below. It will probably strike you as bizarre at first sight. If I am against word processors, what do I propose: that we write in longhand, or use a mechanical typewriter? No. While there are things to be said in favor of these modes of text preparation I take it for granted that most readers of this essay will do most of their writing using a computer, as I do. My claim is that there are much better ways of preparing text, using a computer, than the word processor. "
Less is Better | UX Magazine
"Creators of Basecamp, Campfire, Highrise, and Backpack, and authors of the widely read Signal vs. Noise blog, 37signals is an advocate for all things simple and beautiful. We are delighted to share this interview with David about a range of topics—from software development to the productivity gains associated with making people happy."
HOWTO: Be more productive (Aaron Swartz's Raw Thought)
"“With all the time you spend watching TV,” he tells me, “you could have written a novel by now.” It’s hard to disagree with the sentiment — writing a novel is undoubtedly a better use of time than watching TV — but what about the hidden assumption? Such comments imply that time is “fungible” — that time spent watching TV can just as easily be spent writing a novel. And sadly, that’s just not the case."
The Problem with Design and Implementation
"I've been developing software for quite a few years. One of the issues that seems to come up again and again in my work is this concept of design and implementation. I recall it being a significant part of my education at the University of Waterloo's Computer Engineering program as well. The message was always the same. Never write code first. First you must design software by writing a design document, flow charts, pseudo-code, timing charts... then it's merely a trivial matter of implementing it. Make note of the attitude here given towards implementing. The real work is in the design, and it's just a trivial matter of implementing it. It sounds so simple doesn't it? Now, how often does this work out in real life? "
The Way I Work, annotated — Matt Mullenweg
"I was fortunate enough to be featured in the July issue of Inc. magazine’s “The Way I Work” column. (Page 114, the one with Paul Graham on the cover.) The article is great and the photography very flattering, but it’s a little misleading. All TWIW articles are written in the first person, but not directly authored by the subjects, and we’re not allowed to see them before they’re published. These bizarre rules have some unexpected outcomes, and I’ve taken the liberty of rewriting the article in my own words and with lots of extra links."
25 Tips for Intermediate Git Users : Andy Jeffries : Ruby on Rails, MySQL and jQuery Developer
"I’ve been using git for about 18 months now and thought I knew it pretty well. Then we had Scott Chacon from GitHub over to do some training at LVS, a supplier/developer of betting/gaming software (where I’m currently contracting) and I learnt a ton in the first day.
As someone who’s always felt fairly comfortable in Git, I thought sharing some of the nuggets I learnt with the community might help someone to find an answer without needing to do lots of research."
scottberkun.com » #46 – Why software sucks
No one makes bad software on purpose. No benevolent programmer has ever sat down, planning out weeks of work, with the intention of frustrating people and making them cry. Bad software, or bad anything, happens because making things is hard, making good things doubly so.
Study Hacks » Blog Archive » The Pyramid Method: A Simple Strategy For Becoming Exceptionally Good
Becoming exceptional requires an exceptional amount of work. Trust me, you can’t avoid this. But not all work is made equal. And the Pyramid Method focuses your attention exactly where it needs to be.
Learn Emacs in Ten Years — Edward O’Connor
The short answer is, you should learn Emacs by using it for about a decade. That’s a pretty lame non-answer, so let me try to elaborate.
Agile is Dead | Agile Software Development
The revolution is over. The establishment has struck back, as it usually does, using the strategy it always chooses – assimilation, dilution, extermination.
The Benefits of a Classical Education - O'Reilly Radar
As some of you may know, I got my undergraduate degree in Greek and Latin Classics. So when Forbes asked me to do an interview on the subject of how my Classical education had affected my business career, I agreed. The result, part of a special report cal
Start a New Branch on your Remote Git Repository
An easy to follow tutorial with a shell script at the end. Sweetness.
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in producti...
-
GTD
Items: 40 | Visits: 295
Created by: Michael Kohli
-
gmail
Items: 180 | Visits: 189
Created by: ken meece
-
Unserstanding developers
The myths and truths about ...
Items: 26 | Visits: 1702
Created by: Joel Liu
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo