This link has been bookmarked by 12 people . It was first bookmarked on 13 Jul 2007, by idukes.
-
18 Feb 16
-
23 Sep 15
Donna Hay"The key is to restate any hard problem that requires a lot of software into a simple problem that requires much less. You may not be solving exactly the same problem but that's alright. Solving 80% of the original problem for 20% of the effort is a major win. The original problem is almost never so bad that it's worth five times the effort to solve it."
-
09 Nov 11
-
Encourage programmers to make counteroffers.
You want to hear: "The way you suggested will take 12 hours. But there's a way I can do it that will only take one hour. It won't do x but it will do y." Let the software push back. Tell programmers to fight for what they think is the best way. -
For every feature that makes it into your app, ask yourself: Is there a way this can be added that won't require as much software? Write just the code you need and no more. Your app will be leaner and healthier as a result.
-
-
01 Oct 11
-
Don't be afraid to say no to feature requests that are hard to do. Unless they're absolutely essential, save time/effort/confusion by leaving them out.
-
Slow down too. Don't take action on an idea for a week and see if it still seems like a great idea after the initial buzz wears off. The extra marinating time will often help your brain come up with an easier solution.
-
-
23 Jun 10
-
Keep your code as simple as possible
-
each time you increase the amount of code, your software grows exponentially more complicated.
-
Keep adding code recklessly and, before you know it, you'll have created the dreaded Big Ball of Mud.
-
Less software means less features, less code, less waste.
-
The key is to restate any hard problem that requires a lot of software into a simple problem that requires much less.
-
Solving 80% of the original problem for 20% of the effort is a major win. The original problem is almost never so bad that it's worth five times the effort to solve it.
-
Instead of trying to predict future problems, you deal only with the problems of today. Why? Fears you have about tomorrow often never come to fruition. Don't bog yourself down trying to solve these phantom issues.
-
reduces your codebase
-
happier staff
-
lowers your cost of change
-
fewer bugs
-
less support
-
Which features you choose to include or omit have a lot to do with less software too. Don't be afraid to say no to feature requests that are hard to do.
-
save time/effort/confusion
-
Don't take action on an idea for a week and see if it still seems like a great idea after the initial buzz wears off.
-
The extra marinating time will often help your brain come up with an easier solution.
-
Let the software push back. Tell programmers to fight for what they think is the best way.
-
suggests an alternate route to customers that doesn't require a change in the software model
-
For every feature that makes it into your app, ask yourself: Is there a way this can be added that won't require as much software?
-
-
12 Feb 10
-
Instead of trying to predict future problems, you deal only with the problems of today. Why? Fears you have about tomorrow often never come to fruition.
-
Don't take action on an idea for a week and see if it still seems like a great idea after the initial buzz wears off.
-
Tell programmers to fight for what they think is the best way.
-
There is No CODE That is More Flexible Than NO Code!
-
-
12 Aug 08
-
Solving 80% of the original problem for 20% of the effort is a major win. The original problem is almost never so bad that it's worth five times the effort to solve it
-
-
13 Jul 07
-
The key is to restate any hard problem that requires a lot of software into a simple problem that requires much less. You may not be solving exactly the same problem but that's alright. Solving 80% of the original problem for 20% of the effort is a major win. The original problem is almost never so bad that it's worth five times the effort to solve it.
-
Encourage programmers to make counteroffers.
You want to hear: "The way you suggested will take 12 hours. But there's a way I can do it that will only take one hour. It won't do x but it will do y." Let the software push back. Tell programmers to fight for what they think is the best way.
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.