This guy has always been like this, going all the way back to ios hacking days or even wii hacking days.
I personally don't see AI getting anywhere any time soon. Just look at some of the really funny images some of the best AI available generates[0]. Subtle things like this show you that AI is really a UX around a piece of software that attempts to understand what you're asking for with less input than having enough buttons to generate EXACTLY what you're asking for (I'm thinking of photoshop in the case of text -> image).
Some things in AI do impress me, but the fact its not far more pervasive in our every day (there are people who use voice assistants sure, but its not EVERY household doing it) lives tells me we still have a long way to go.
[0]: https://www.reddit.com/r/technicallythetruth/comments/y26t6x...
The joke I heard was that AI only refers to technology in the future, and not the past. We use plenty of machine learning models every day:
- Every time you use dictation
- Every time you use biometrics, like face scanning, to unlock your phone
- Every time you use any sort of search engine, news feed, or see an ad
- It is an integral part of the field of computer vision now, so anything to do with scanning documents, using AR, taking photos, etc uses AI
It’s only getting better and more integral to more fields over time.
This is actually known as the AI effect.
> We don't use AI anywhere today
> But here in X places we do use AI
> Yeah, but not for Y
once Y is using AI
> We don't use AI anywhere today
> But here we're using AI for Y
> Yeah, but not for Z
And so on :)
From Wikipedia:
> Author Pamela McCorduck writes: "It's part of the history of the field of artificial intelligence that every time somebody figured out how to make a computer do something—play good checkers, solve simple but relatively informal problems—there was a chorus of critics to say, 'that's not thinking'." Researcher Rodney Brooks complains: "Every time we figure out a piece of it, it stops being magical; we say, 'Oh, that's just a computation.'"
> "The AI effect" tries to redefine AI to mean: AI is anything that has not been done yet.
> Some people think that as soon as AI successfully solves a problem, the problem is no longer a part of AI.
In my eyes, AI is something that could pass the Turing test without fail, ever because it knows how to communicate how we do, and think like we do.
GPT-3 and image generators that have somewhat of a world-model are, imo, closer.
It's moving the goal post simply. As it is the same with Google's Chatbot that "fooled," their own engineer. Thus it becomes a chicken and egg situation as to when AI truly passes the turing test. In the same way putting on a VR headset and being fooled you are someplace else the first few times. Then once you are used to it, it becomes as if you are changing your reality just like putting on new glasses.
Human beings have a hard time with exponential. And my guess will be next year that we have AI generated video that is indistinguishable from a human production. It's just software sure, but so are we.
I don't agree. You can take pride in what you've accomplished, and you should do that, but you can be humble at the same time. Accepting there will be better individuals than you or better solutions than yours is both sobering and motivating to be and do better.
When you accept that you're very smart, but not the smartest, you unlock the potential to be one of the the 10x-100x engineers others aspire.
I'm a very motivated individual, and did some pretty impressive things back in the day, and I'm still capable of doing these things. However, I'm not the best, or won't be the best for long. This is how the world works.
Being able to say thanks, and being able to say sorry goes a long way, and takes you beyond where unabashed arrogance takes you.
Lastly, arrogance makes you fragile. Fragility is not good under stress, and under real world circumstances.
There are plenty of times in my career where I wish I were more arrogant. I’d probably be in a completely different place altogether if I were even slightly more arrogant and that lack of it has held me back in some ways.
For hard tasks like engineering, you need a balance of ego (I can do this) and humility (this is hard, I need to work as a team and study the problem). Too much of either results in negative outcomes.
Lack of humility can lead to the wrong limbs being amputated. The parallels to understanding your personal limits and knowing when to trust other people directly applies here. Confidence != arrogance.
But huge majority of the problems require whole teams of people to solve, especially in the commercial world. Senior engineer who can 2x team of 10 people is better than a single engineer who is 10x himself.
As a programmer, I have never once believed that. I just believe that the problems I am being presented with are novel enough (usually because of the context and constraints surrounding it) to have not been encountered before and solved.
Just like you never cross the same river twice, I don't think you ever solve the same problem twice.
I think the core skill engineering requires is persistence: the belief that you can find a workable solution even when the problem itself gives you absolutely no positive feedback during the process.
Totally, like there's no way an AI company could hit $80M revenue in <2 years [0], or power the recommendations systems for billions of dollars worth of online commerce.
Also there's no way that it could generate audio/image/video/text that would trick the average person that this was generated by an AI.
That's why "lol it's just spreadsheets and if-statements," is kind of funny: there's a grain of truth to it.
Then there's the kind where the talented musician in the band announces their departure and solo album. And starts talking about finding God and becoming a modern day Prometheus.
I can't put my finger on when the transition happened but it was somewhere just before the Lex interview for me.
I don't think so. I know at least a couple of great engineers who were not so sure of themselves. They were just eager to try, over and over again. Both of them developed novel 3D engines. One formed a company over his engine, the other one taken on one of the best liquid simulation teams, head on, and gave them a good run for their money by being equal to the whole team by himself and his wife.
I'm also on the same bandwagon. I'm not sure that I'll come up with a great solution before touching the keyboard. I'll only say it's a good solution after finishing it and comparing it with other available solutions (if there are any) or similar ones.
I did great things, and I failed miserably too. In every case being not sure about myself allowed me to have a level head, and see through my solutions' shortcomings and iterate over them.
The only thing I'm sure about myself is, I can give a shot, and iterate over it as time and my abilities allow. That's all.
They are better than average technically, but their social skills fail them. Which in a paid employment situation carries a lot of weight.
I feel sorry for these guys
Just don't get yourself in such a situation and you'll do fine :)
I've only been an employee at the start of my adult life for 3 years at a small software outsourcing agency. Been gaining a steady 20x the median salary for my city for the past 12 years since I've abandoned "employment". Can't say I'm particulary smart. I'm closer to Dumb and Dumber than Rainman. I just ignore opinions of other people or entities and go my own way.
Who is you? Not a comedian?
Nonsense. John Carmack is the most obvious counterexample. But pretty much anyone that works in gaming.
While the stories of resentment of specific employers abound — your general thesis is nonsense.
Game dev is packed full of young people and regret, burnout, resentment, and depression are perennial reasons that people state when they leave the industry in their late twenties and early thirties. Game dev is the canonical example supporting this thesis.
Yes, there are certainly exceptions, but as a broad comment, it aligns very strongly with what I've seen among many many programmers both in games and out. It's very hard to make the kind of sacrifices that lead one to spend insane hours programming. Some people do that because they just straight up love it so much. But most also have mixed with that some other harmful psychological motivations: a need to prove themselves, compulsive perfectionism, escapism, feeling that they are only worth as much as they produce, etc. If you just give into those instead of addressing them, the end result is often, well, deep regret, burnout, resentment, and depression.
Well, agreed, but my point is that many go through that ringer without regrets. It’s not even close to all - though yes those that end up burned out are a large minority compared to less competitive industries. Those happy with the status quo are not nearly as vocal. Medicine is similar.
The intersection of the sets of developers who:
A) make it to their 40s and are still IC's
B) still work > 40hrs/wk on a startup for little-to-no-pay
C) are still happy and enjoying themselves
Is small. It's not empty though!
But I do think there are many people who think this is the ideal way to live or something they ought to strive for. And the set of people who try and realize later in life that was not what they should have been working towards do tend to burnout and have regrets.
It happens a lot to people who want to be famous. They don't think about what they would have to give up to get it: some measure of your health in later life (hello carpal tunnel, frequent recurring hemorrhoids, type-2 diabetes, heart disease, poor vision, etc), friends and relationships (read enough biographies and loneliness is a recurring theme) -- things they might take for granted. There are stories from people who did make it and became famous and wish they hadn't. There are more of those than the, "I wouldn't have given this up for the world," types I think.
Grass is always greener on the other side, as they say.
It stands for, Individual Contributor, and means "a programmer whose only responsibility is to contribute to the code."
https://www.youtube.com/watch?v=kNWTculMsTY "motivation and intelligence"
> Competitors
> People who have done well at math competitions (USAMO, IMO, PUTNAM), competition programming (ACM, USACO, codejam, topcoder), science fairs (ISEF, STS), or capture the flag (DEFCON, secuinside, GITS). Those competitions don't just select for ability, they also select for quickness. We are in a very competitive space.
I feel like this is a false dichotomy that bad engineers tell themselves to justify not working hard at being a good engineer and instead screwing off.
Believe it or not, you can actually be a world class engineer and have a healthy life, who would have known? Weird.
If you want to make it to your 40s and still be an effective IC you need to learn how to regulate yourself and follow a disciplined approach to work. Cognitive performance from chronic sleep deprivation takes years to show up.
> geohot
Well that and his belief, while at comma, that how fast you can code is the most important metric when assessing software engineers.
Competition programming is fun to watch but a poor indicator of maturity or success. In many systems it doesn't matter how fast you arrive at an answer. Increasingly it becomes important to arrive at something close to the right answer and to be able to show your work and prove to others why it sufficient and suitable.
Still good for a hot take though. I hope time off will help him cool down a bit.
Programming all night in a do-or-die mode is fun and all until you get a bit older. For many people who lived this life they realize only too late that they didn't spend enough time making friends and building a community around themselves of genuine relationships.
Update: I should also say that despite the weird god stuff and what-not; a decision to leave a company because it has changed and you're no longer a good fit is a HUGE decision and one that is often not made by founders. Massive props for that.