Earlier quoted context omitted.
I didn't listen to the whole thing nor do I care about any one individual thing, but they did talk about the co-founders as well from what I saw. That said, other than that I disagree with you. If someone wants to have their opinions taken seriously they have take other people's opinions seriously as well and can't get angry as soon as people disagree. Personally I think many of his essays aren't very good, but there…
I don't think there's been any "getting angry as soon as people disagree" - he's substantially edited essays in response to critiques. It's pedantry and the presumption of malice that were probably the hard things to deal with, and he just realised that his time and energy would be better spent being an attentive father and partner. Good for him.
A Conversation with Paul Graham [video]
81–90 of 159 posts
Re: A Conversation with Paul Graham [video]
#82For the people on the go like me, here's a podcast feed link with the video: Overcast: https://overcast.fm/+OcWu1RUwE Feed: https://podsync.net/pH3E-Qhxn
Re: A Conversation with Paul Graham [video]
#83Earlier quoted context omitted.
It’s easy, but leaky in terms of fees and delays as compared to US-to-US transfers. When I send money to EU hobbyists, it’s often 3 days and ~10% eaten up by fees.
There are gateways like PayPal (which is why it skyrocketed in the first place). So you send $100 PayPal and he gets $100. He then goes and spend his full money to buy something online without any other fees.
Re: A Conversation with Paul Graham [video]
#84“The mistake you will most likely make as a startup founder is coming up with your own vision of what your product should be instead of getting feedback from actual users.”
I mean, I get it, you have to make customers happy in order to have a business. But this seems like something different. It seems like saying your goal should be to make money a priori and that defining vision based on feedback is a good way to do that.
But what if that’s not your goal? What if your goal is to create a company that embodies a specific mission, like say related to environmentalism or furthering cryonics or actually paying all the taxes you should pay as a civic virtue instead of offshoring to skirt your duty to help others that form the foundation of society that enables your business to exist in the first place.
Doing things like this often requires telling customers “no” or declining business all together, in order to impose the vision because you believe the vision is more valuable than short term pivots to satisfy short term client feedback.
Another thread of this that I don’t like is that client feedback is often wildly inconsistent and incoherent, not based on realistic understanding of what’s possible.
It sounds glib to say listen to feedback, but what does that mean? Which feedback is good? When is it actually going to payoff according to your true goal?
Re: A Conversation with Paul Graham [video]
#85Earlier quoted context omitted.
You have to be a user of your own product to really make it good. Look at Apple. Most of how they got where they are is by Jobs, Ive et al. making what they wanted to see, and nitpicking at everything until they were satisfied. Also: "people don't know what they want until you show it to them." Of course you have to address customers' frustrations, but relying on just "data" and marketing feedback all the time often…
This sentiment really bothers me. It's frequently used to disadvantage candidates from positions because they're not users of the service or product. It's just not generally true, but it's often repeated as though it were. It's demonstrably not true that you must be a user of a product to build a good product. To pick a random example: I doubt all pacemaker firmware developers have heart conditions that require pacem…
Sometimes people at work give me crap for this. But they know my engineering contributions are among the best in the company, so what can they say?
It’s foolish to disqualify people for this. Imagine saying men cannot ever work for a team that delivers feminine hygiene products, or a woman can never work for a product team that makes male health products.
Re: A Conversation with Paul Graham [video]
#86Re: A Conversation with Paul Graham [video]
#87Re: A Conversation with Paul Graham [video]
#88Step 1) collect seven pounds of weapons grade plutonium
Step 1 of a great startup is an amazing idea. Unless you have step one I think the advice is pretty non applicable. Sure, I get the whole camp “ideas are a dime a dozen”, but, a bad idea can fall apart with millions of VC ran by MIT grads and an amazing idea can come to life with a few hundred bucks with a high school kid.
Re: A Conversation with Paul Graham [video]
#89Re: A Conversation with Paul Graham [video]
#90Earlier quoted context omitted.
Writing software on windows is like using chopsticks with mittens. You can do it, it’s not pretty, and it’s not the use case the mitten sewer had in mind during development. Read the Unix Programming Environment to see the exact opposite mindset for OS design.
What a load of nonsense. C#'s a great language and their dev tool, Visual Studio, is second to none.
Creating a "solution" (who came up with that word?) is absolutely horrible compared to just opening a file in vi/emacs.
There does not appear to be a command line debugger -- while the debugger is good, graphical debuggers are a pain to use.