91–100 of 108 posts
Earlier quoted context omitted.
Well, AI absolutely appeals to the type of bulkshitter which hates coding and wants to get away from it.
> bulkshitter With all due respect, this perspective baffles me. Some see it your way, others see so much opportunity.
Earlier quoted context omitted.
Maybe that’s because the AI pushers are compensating for already not being as good. What happens when other yous start using ai. I suspect they will obv outperform you just in sheer typing speed.
I don’t agree. There’s a “muscle” you train every time you think about problems and solve them, and I say muscle because it also atrophies.
Earlier quoted context omitted.
Surely you don't believe that there's a significant fraction of tech jobs that pay $500k?
No, not sure where you got that from.
> I just landed a mid 6-figures job _without_ grinding leetcode. They’re out there. This game everyone plays is an abomination.
Earlier quoted context omitted.
This is what I heard from many people online. I have tried beign specific, I have even gone as far as to feed its prompt with a full requirement document for a feature (1000+ words), and it did not seem to make any significant difference.
You are experiencing the Dunning-Kruger effect of using AI. You used it enough to think you understand it, but not enough to really know how to use it well. That's okay, since even if you try and ignore and avoid it for now, eventually you'll have enough experience to understand how to use it well. Like any tool, the better you understand it and the better you understand the problems you're trying to solve, the bette…
I'm finding the inverse correlation: programmers who are bullish on AI are actually just bad programmers. AI use is revealing their own lack of skill and taste.
Earlier quoted context omitted.
You are experiencing the Dunning-Kruger effect of using AI. You used it enough to think you understand it, but not enough to really know how to use it well. That's okay, since even if you try and ignore and avoid it for now, eventually you'll have enough experience to understand how to use it well. Like any tool, the better you understand it and the better you understand the problems you're trying to solve, the bette…
> Give an AI to a product manager and their code will be shit. Give it to a good programmer, and they're likely to ask the right questions and verify the code a little bit more so they get better results. I'm finding the inverse correlation: programmers who are bullish on AI are actually just bad programmers. AI use is revealing their own lack of skill and taste.
Earlier quoted context omitted.
No, not sure where you got that from.
Oh, I guess you were just sharing and this wasn't advice: > I just landed a mid 6-figures job _without_ grinding leetcode. They’re out there. This game everyone plays is an abomination.
I offered an anecdote.
Earlier quoted context omitted.
This is what I heard from many people online. I have tried beign specific, I have even gone as far as to feed its prompt with a full requirement document for a feature (1000+ words), and it did not seem to make any significant difference.
Need to use the Wittgenstein approach: “What can be shown cannot be said.” LLMs need you to show it what you want. Its model has seen nothing . Built up a library of examples. Humans also work better this way. Just good practice.
Author assumes we’re going to use AI more and more. I don’t agree. I regularly out perform the AI pushers on my team and I can talk about engineering in person too!
Earlier quoted context omitted.
It depends a lot on the specific business and company stage. E.g. CTOs at boutiques basically meet clients and put on a performance to instill trust. CTOs on product startups with little funding are more like "I'll hire a teammate that can put up with the mess I wrote". CTOs after the product startups have large investments are more like "I'll pretend I know what I'm doing and let the principal engineers actually run…
I was CTO from 2 to 100, over 6 years, and led the core tech development the entire time. Tech Co-Founders certainly can and do code. I was a Principal Engineer before and after. In a sense, you are right that the title is meaningless, and only means signature powers. And you are right that other principals rewrote legacy stuff. But I also participated at the same level. I just knew I was only above due to some marke…