3,476 karma · joined April 10, 2007
I first met Drew at MIT, and first saw Dropbox when he was showing off what he was hacking on on his Windows laptop in a coffee shop in Cambridge at the start of the summer. My user id is 88, haha. The batch was tiny by today’s standards (what was it, 20 companies? less?). YC invested $5k plus $5k per founder, for food and rent and servers for three months, in exchange for 2-10% of your company. You could have office hours with Paul every week if you wanted. At the end of the summer, a bunch of us moved out west and lived in Crystal Tower in SF. When Drew raised $1m from Sequoia, I was shocked! YC founders at the beginning of the summer were generally two guys with an idea (if that), so raising VC out of the gate was rare. AppJet was another favorite of the batch, and we raised $90k from several angels to keep going. YC had already had its first acquisitions, like Zenter (presentation software acquired by Google).
In those days, the entire YC community was smaller than one batch today.
It is amazing to me to see start-ups I remember from back then still going, and even become household names. AirBnB (2008). Weebly (2006) is even older than Dropbox.
Way to change the world, PG and Jessica. And of course Drew and Arash!
If you have poor posture and core support and a tight chest, I would say experiment with filling your lungs completely, and with engaging your abs very slightly on the _inhale_, to feel some of the sensations of full, supported breathing. Your core muscles create pressure that helps fully inflate your lungs.
Don’t listen to any admonishments about “breathing wrong” as your body will use them to create additional tension and restriction rather than relaxation and freedom.
So even if a design or detail is bad (according to me, or you, or most people, like a bad movie), a lot of thought went into it, and probably a lot of people will copy it! :)
Running a start-up can be a pretty good gig, too.
Nah, let’s just alternate between micromanaging and being totally absent; fret about lack of productivity or lack of progress; maybe institute a daily stand-up.
Generic reactions to negativity, saying there are two sides to every coin, do not really contribute to the discussion, IMO, so I disagree.
We are already a decade into neglecting native app technologies in favor of web app technologies, because web apps were much easier to write and deliver than cross-platform native apps (and largely still are). It’s to the point where even big companies with lots of resources are hiring web programmers and web designers to build their UIs.
It’s interesting to me that mobile changes the trade-offs. The quality gulf between web and native apps is greater. The web sucks more on mobile, and expectations for native apps (animations, touch, etc) are higher. Mobile OSes also make it much easier for users to install and manage native apps than it is on desktop (because of the app store, no custom installers, no users locked out of installing apps by their employers as far as I know). I’m excited about React Native for addressing the cross-platform part.
We’ve learned since Java that even if you don’t have “write once, run anywhere,” you can still have “learn once, write anywhere,” a la React. Also, we expect apps to come with their own systems of UI widgets these days, not necessarily “native look and feel.” It really changes the game.
I say the same thing to the comments about the irresponsible “UX” of Autopilot for not handling this case. It’s more about irresponsible marketing, capitalizing on the enthusiasm for self-driving cars, potentially lulling overzealous customers to trust a cruise control system or emergency braking system with their lives.
Ultimately, I want a profitable product to be a byproduct of my excellent engineering, not have my engineering be just a means to an end, of getting to a profitable product.
In other words, “I want to work for a company that values engineering excellence.” And the reply is something like, “you don’t understand how business works”? It’s true that an understanding of the concepts in the article will help you recognize a good business so that you don’t go to work for a company started by engineers with no understanding of business themselves, but you don’t want to work for someone that has a knee-jerk reaction to bringing up engineering quality as something important, either.
So your commute takes on properties of already being at your destination, and being at your destination takes on properties of your commute or taxi ride — being in a space-constrained vehicle in motion, consuming power, creating and experiencing traffic, etc, not just en route but all day or all night!
Treat it as breadcrumbs from someone farther along on the journey of growth and self-discovery.
The "function" in "functional programming" and the "function" in "avoidance or banning of functions with side-effects" are two different words, by the way! FP is named after the math word, not the programming language word, which means different things in different languages but usually means a kind of subroutine. FP means programming in a style that emphasizes composition of mathematical functions, and in an imperative language this generally amounts to writing your subroutines in a certain way. It just so happens that many imperative languages call subroutines "functions."
If you tend towards "constantly thinking about how everything you say might be misinterpreted," congratulations, you're neurotic, like me. It's just something you have to overcome enough to be comfortable expressing your own unique opinions. When you do this, you may find your controversial opinions are merely out of touch. Like you have an IQ of 180 and you've been reading scientific papers and you can prove there are only two genders... and now if you can't express this view over a beer in SOMA without getting some looks, you can't invent the self-driving car or something...?
I sometimes hear, from other engineers working on a complex React app, that the point of React’s components is that every component is written to be “reusable.” Every component. This is used as a justification for “going general” immediately when writing a component. In reality, there is real work to make a one-off component into a reusable component, and that work can only be done in the context of having (or at least realistically imagining, not dreaming up as an exercise) multiple use sites.
What React components actually provide are the same things that modules and functions provide: encapsulation; limited dependencies; a calling convention. When you write a function, you try to keep the arguments to a minimum; you might say it makes the function more “reusable,” but there is still a big difference between a library function that is designed to be used from anywhere, and a private helper function that is not. React components are “reusable” the way functions and modules are reusable. A better word might be “usable.” :) You can reason about the use, even if there is only one use.
Making something “reusable” means making it general, and we’ve all had the experience that the article points to of taking some code that was intended to be general, but in fact is used in only one place, and remaking it so that it’s actually possible to use in a second place.
That said, I have many times in programming succeeded in boiling something down to its essence in advance, and writing the general thing first, followed by the specific thing. I suspect this is actually more about simplicity than generality, however. I’m thinking of cases of “bottom-up” development where you write the primitives and then the higher-level parts in terms of the primitives. Actually, maybe it is about generality too, and when you are testing out your primitives in different combinations, you are doing the work required for good generality (seeing lots of different cases and basing your decisions on that).
Engineers engineer. They are highly trained professionals who are doing their job when they are figuring out how to build something, improve something, or fix something, often with the goal of being able to develop new features quickly without an inordinate number of bugs.
Your engineering team shouldn’t be running your business. Even if they have good ideas. And in practice, they will be overruled immediately, anyway, the moment someone with any real authority makes a roadmap or a key decision, because they are engineers. They aren’t answerable to the board. They haven’t studied the market and competitive landscape in depth. They can’t pivot the company.
There’s something perverse and The Office-like about diagnosing Jamie as a problem “but it’s not his fault.”
Engineer runs into boss’s office: “Sir, code quality is critically low. I suggest we begin paying down technical debt before it’s too late.” Boss, smiling to camera: “This is Jamie. When he started, he was a team player. He believed in the vision. He didn’t spend all day nit-picking about things like code quality. Look at him now! I don’t blame Jamie, though. I blame myself. If I had made Jamie feel like his big ideas and product insights were welcome here, early on, he wouldn’t have devolved into seeing himself as a mere code monkey.”
When you take the responsibility for building the right thing for the market, etc and smear it across all the engineers, some will step up and become informal managers, organically acquiring power in response to the responsibility put on them, while others who are too busy programming or not interested in taking on other jobs will realize they have responsibility that is out of line with their power.