The writer makes assumptions that strike me as completely arbitrary in this article and I feel the need to comment.
The writer quotes a "law" which states that in order for a computer system to be balanced the hertz of the CPU, the bytes of RAM, and the bps of IO should be the same. I shrugged it off to an old quote taking in assumptions of the time in which it was penned. I continued to read, expecting that he was illustrating a point. Then I see:
"So using GigE as our interconnect, a perfectly balanced system would have 1 GHz CPUs, and 1 GB of RAM for each core."
How can one assume that the clock of the CPU has anything at all to do with the amount of ram or network IO for a "balanced" configuration? Is it 32b or 64b processor? How wide and fast is the front side bus? Does it use a minimal instruction set or a full featured IA style set. How long is the pipeline? In effect, how much work does it do per unit time? Is this not the real question?
Also, how much data can you store and read from RAM per unit time? This information seems at least equally as important for an evaluation of balance as the total amount of RAM available. And finally, what is the workload? Will the parameters of the computing workload not completely determine the optimal "balance" of hardware capabilities?
I am commenting here as a reality check on my own thoughts about this article. Am I missing something or is this guy totally off the mark with this "law" and computing balance equation?
It's totally off the mark in terms of absolute numbers, especially when you take into account the huge variety of uses for a machine... my machine, for instance, isn't really bottlenecked by a 52mbps network connection (not to mention 4mbps internet), but I'd still like more than 3ghz dual core. A whitebox in a Google render farm probably WOULD be noticebly slower with 100 megabit compared to 1 gigabit on a MapReduce.
The thing is, though, the 'law' was created in the 60s, and it's stayed mostly order of magnitude correct since... so that's quite impressive in itself.
Yep, the stories are already much more interesting. I just blew an hour when I only sat down to check my email. Great. Guess I'm going to have to call in hacker to work.
I have noticed the same thing. I set news.yc as my home page months ago and love the way that there is always something to read that leaves me better then it found me. There has been much less volume lately (2-3 weeks?).
They are general purpose game building frameworks. I am currently working with it in MMO form, all implementation code in Python. It is a mature package for interactive 3D over the web if I ever saw one.
Hmm.. there may be something to that.... hey thanks! :)
Wow, what a response. I am excited by the prospect that at some point in the near future I can dive into lisp with a clear goal in mind and the resources to make it happen. I have been hearing for years about how lisp is really the ultimate programmers language. I respect this lisp-lover's oppinion and experience ultimately, and put him right in the list with Paul and Carl. So, 3 elite programmers who sing the graces of lisp. One was enough for me to want to learn to think in lisp. 3 in support should be a point to ponder.
The problem I have always encountered with trying to build a solution in lisp is the lack of resources. It sounds like lisp is inching closer and closer to the critical mass where tools and libraries will finally be available for more then a few uses.
This lisper I know said "Don't hold your breath." when I suggested that lisp may be coming close to getting its due. I know that there are alot of people out there like me. We will start using lisp when the great advantages of the language finally outweigh the disadvantages of implementation. I think its just a matter of time until lisp is a clear win, as long as the tools come.
I've never written a line of lisp. I want to save my lisp cherry for a time when I can have more "Yay" then "Doh" while I learn and use it. I think it will be worth the wait.
"Even the founders who fail don't seem to have such a bad time."
I was a founder in a startup that died late last year. It was the hardest I have ever worked, and one of the most challenging things I have ever done. It was frustrating in so many ways and there was amazing amounts of strife involved. In the end the project ran out of money and the products of my labor and imagination are now gathering dust in storage. After all that, without any monetary reward, I would do it all again in a second. The challenge of following my senses through completely unknown territory and the reward of seeing my idea come to life was more then enough to make the whole thing worth it. It was the challenge that drove me. In the end it was the challenge itself that rewarded me even though the company didn't fly.
"A lot of people think they're too young to start a startup. Many are right. The median age worldwide is about 27..."
I do agree completely with the idea that adulthood is a state of mind and not an age. I remember my dad asking me "What do you want?" when i was somewhere between 18 and 21. My reply at that time was "I just want to be comfortable." I remember it quite distinctly. He then told me "I expect that will change some day, given your creed." He was right, and I realized it while in the midst of working my tail off on a project. All I wanted to do was work on my ideas, see them come to life. The discomfort didn't slow me down at all, it was the challenge that I wanted.
"You need a lot of determination to succeed as a startup founder. It's probably the single best predictor of success."
A founder without determination is not going to succeed, but their drive can't cause them to loose perspective. One can dig with a singular purpose and make a big hole, but if it is in the wrong place it does the project no good.
"You don't need to know anything about business to start a startup."
True, but eventually the business skills will be required if the project is to continue. My experiences have taught me that while a viable product is most of the battle, a lack of resources on the business end of a project can stop it in it's tracks. Weather it is the founders themselfs that learn the skills, or outside resources are brought in to help - the skills must be obtained. The lesson I learned is pick the right people to depend on, or depend on yourself. Implementing your ideas is great all in itself, but it is much better if there is someone interesting there to see it when you finish.
"If you don't have a co founder, what should you do? Get one."
Be careful! Going into business with someone in the startup environment is a commitment. You will spend allot of time with them and you will have to depend on them constantly. It is almost like a marriage, choose wisely. Good friends do not always make good business partners.
"In a sense, it's not a problem if you don't have a good idea..."
I believe that a person's ability to learn, gain skills, and adapt is the most important thing period. You find someone with a carrot, you've just got a carrot. Even if you need a carrot, their value is limited once they give it to you. Find a gardener and you can grow anything you need. Reminds me of some proverb about choosing a fishing pole or a fish.
"This one is real. I wouldn't advise anyone with a family to start a startup."
I agree with this 100%. I did it, and I would not advise it for someone with a choice. My family is amazing and supportive and more then anything else they KNOW me. I have founder pumping through my veins. The startup world is home to me, there is no question that I will be a serial entrepreneur. Good ideas give me goosebumps, unsolved problems give me insomnia. My family supports who I am, so I am able to do what makes me happy. Successfully pouring your soul into a project and being a member of a family at the same time is a learned skill. Play it safe unless you know what you are getting into, or just can't change who you are.
"Start another company? Are you crazy?"
See above.
"Be aware, though, that if you get a regular job, you'll probably end up working there for as long as a startup would take, and you'll find you have much less spare time than you might expect."
Working a regular job instead of chasing dreams is still a commitment. Yes, you can work a regular job without thinking about it all the time. You can go to work 8 hours a day 5 days a week and not have it take over the rest of your personal time. Having said that, is it really worth it? Why do something all day that you don't care about? Sounds flawed to me.
"Each person should just do what they need to without anyone telling them."
This throws back to the "pick carefully" comment. Your choice in business partners is paramount. There are many many people who will just stand there on the field with the ball looking confused. Within the constraints of a startup you may not have time to figure it out after the fact. Make sure you know they can work, and that they can work with you.
"If you go to work for Microsoft, you can predict fairly accurately what the next few years will be likeÃÂall too accurately, in fact. If you start a startup, anything might happen."
This is part of what attracts me to the role of a founder. Clicking send on an important proposal and not knowing what will happen is like jumping off a bridge for me (with cord of course). I love not knowing, I love the process of finding out. I love the risks you have to take and the rewards you can reap. Anything can happen, and that resonates with me.
"A significant number of would-be startup founders are probably dissuaded from doing it by their parents."
This is a problem I never had. My dad tells a story about having a booth across the aisle from Oracle WAY back when they were both small. He was lead developer on a similar DB app called RDM which was a far more mature and fully featured product at the time. His business leaders thought conservatively, Oracle shot for the stars. The rest is history. My father will never discourage me from chasing my ideas, and my mom just loves to see me glow. He was there, at the time and the place; he chose the steady paycheck.
"Imagine being sad on Sunday afternoons because the weekend was almost over, and tomorrow you'd have to get up and go to work. How did they stand it?"
What, as apposed to kicking back - stretching out - and wondering what day it is on Sunday afternoon? Never.. operating by the seat of your pants and living your ideas is the only way to go. Its the best feeling in the world, and the bad times only make the good ones better.
