https://github.com/technomancy/emacs-starter-kit
WARNING!!! The version in git is for Emacs 24. You will need to actually download the earlier version to use with Emacs 23.
364 karma · joined October 21, 2010
https://github.com/technomancy/emacs-starter-kit
WARNING!!! The version in git is for Emacs 24. You will need to actually download the earlier version to use with Emacs 23.
a) Find gold in California b) Become a rock star c) Win a lottery d) Strike it rich and famous as an 'entrepreneur' e) Achieve above average, long-term gains by trading tulips
Yet, the selection bias that promotes these dreams doesn't deter anyone who is going to go that route.
http://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_H...
If you are implementing something which is almost exactly like something you personally have implemented before, then your estimate will be almost exact because you should have tracked how much time you spent on the original ... and assuming that too was a re-implementation of something you'd already done the R&D on. IOW, this is at least your third time.
If you are implementing something for which you have references that are very close to what you are building (but you didn't build it) and you already understand them, then you can make a reasonable estimate of the time to implement. In this case the OP's advice works .... add some padding. The more granular your breakdown of the problem, the better you estimate will be.
But when there is R&D on the problem, you are not talking about 'padding', but 'factors'. If you are doing something that is new to you, but you think you have (or can find) decent references, then you can estimate based on how you hope it will go (based on your breakdown of the problem), and multiply by 2.
If you can't find references, then factors of 3 or 4 beyond your ideal development scenario will be more realistic.
It's worth noting that if you are in the last scenario, then you probably weren't a good choice for the project. Also, 'agile' pricing would be better, but either fixed pricing or giving clients some idea of what to budget is more typical.
Yes, and it is the kvetchers that are putting a black cloud over a language and community that has been evolving quite nicely otherwise.
Can't say I was ever classified as a 'dullard' but my grade school scores indicated that I was. Even when I went to college, after a stellar start, my performance deteriorated. After considerable time, I was able to go back to attend a world-class university and excelled, largely because I had learned what the goal actually was. When I was young, I mistook the 'traditional model of teaching' for learning, which was something I was quite good at. The goal of being the recipient of 'teaching' (ie, a student) is to achieve higher scores than everyone else. In fact, learning is potentially an impediment because it requires critical thinking, and you won't get far as a student with that. Some students understand the real goal and do quite well. And some may even learn at the same time. Many others are simply frustrated or turn off completely, as I did.
I suspect that the 'calculator age' has caused kids (and kids that have now grown up to be parents) and maybe educators to over-value an increase in significant digits in calculations. It's interesting that the method of multiplication illustrated in the article is referred to as 'new' since when you use a slide rule, you operate in this way anyway. And to echo Hans Bethe, this is often "good enough".
I have insurance and the insurance company (BCBS) will only pay what it thinks is appropriate for a service, not some negotiated rate. That is, if the doctor, hospital, or lab says that it costs $1,300, but the insurance company wants to pay $700, I'm stuck for the other $600. The result is that in order to meet the high deductible (at which point I no longer have to pay out of pocket like this), I pay way beyond the amount of the deductible since only the approved rates are applied. In practice, I end up paying out 175% or more of the deductible amount.
I suspect that our experience will soon become the norm, if its not already.
That is a profound way to put it and certainly accounts for a lot of the premium that clients are willing to pay.
Scale -- Bingo! The goal is to make the fixed overhead (incl employees) an increasingly smaller percentage of revenue. But to handle the increased revenue (ie, workload) you have to concentrate on increasing efficiency/productivity. This has a lot of influence on decisions about process. Obviously, the more routine those processes are, the cheaper (and more easily replaced) the labor can be. Also, if the work is done under a fixed price contract, you can achieve a greater effective hourly rate if you are efficient and manage risk well.
Charge more -- "charging more pushes away your existing client base". This is not such a bad thing if you have your eye on 'scaling' (ie bigger projects). Bigger clients have deeper pockets (although they also have more unique needs, which introduces more risk).
Build a product -- See Nassim Taleb's discussion about 'scalable work' in "The Black Swan". The odds aren't good that this will pay off.
1) Try to collect data and offer up suggestions 2) Try to get a good Facebook presence. (etsy.com). Your target market lives on Facebook now. 3) Can you email your registry?
Gotta go. Good luck
"I prefer minimum-length but maximum-information names, and then let the context fill in the rest. Globals, for instance, typically have little context when they are used, so their names need to be relatively evocative. Thus I say maxphysaddr (not MaximumPhysicalAddress) for a global variable, but np not NodePointer for a pointer locally defined and used. This is largely a matter of taste, but taste is relevant to clarity."
Also perhaps money market funds.
Several people have brought up HTDP, which is very much in the same SICP-inspired vein as these other books in the list. I personally find it to be different enough from SICP as to not be considered a precursor to SICP. YMMV.