I agree with your point but i think there are many cases in which its good. like if you're building something and get slowed down by topics you’re not familiar with, a summery of a topic is enough to remove the obstacle of not knowing how to continue. but yeah you can't call this "real" learning.
The risk of AI isn't making us lazy, but making "lazy" look productive
81–90 of 104 posts
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#82Earlier quoted context omitted.
Please tell me how is going to be “hacked”? A) The IAM role of the Lambda runtime it’s running in is least privileged and only has access read and write access to the required S3 bucket and other required AWS services and even those are tightly scoped. B) For authentication I used Amazon Cognito and ran a curl shell script against each endpoint for authentication vs non authenticated end points C) The database user h…
So you've made a read only wrapper around a database? That one person needs to access? There's no tentantization? You can't access more than one person's data? So there's zero chance one user can access someone else's data? If you answered NO to any question, refer to my previous post. If you answered YES, you could have just hooked your DB up to power BI or tableaux or whatever. Not exactly something to start boasti…
I see you didn’t say anything about the possible security issues if I was using AWS Cognito for auth, tightly scoped IAM privileges for the runtime environment and a tightly scoped database user.
BTW, with AWS you can also enforce DynamoDB, Postgres and Redshift (?) to only allows rows to be accessed based on the user (IAM or Cognito) so no matter what Claude did, as long as you validate your security boundary at the AWS and database level, there wouldn’t be an issue.
Why would I trust developers (or Claude) to write secure multi tenant code when I can enforce it on the database/AWS layer?
https://aws.amazon.com/blogs/database/multi-tenant-data-isol...
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_p...
1. I did say it’s an internal admin site and I mentioned AWS and S3. I didn’t say it was a reporting site only dealing with the database.
2. It’s B2B, every company pays 5-6 figures annually and they each have their own AWS account. No company can access any other company’s data because they each have their AWS account, user pool and database.
3. How am I “boasting” about doing “web dev” (poorly paid commodity work) when I specifically said I hadn’t done web development “since 2002” and talked about the UI was something from 2002?
4. I said it was an “Admin site”. I didn’tg say it was a reporting dashboard.
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#83Productivity can’t be faked. Productivity also mostly aligns with incentives in my opinion. You want someone to be productive then give them a reason to be.
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#84That sounds relatable, but there are ways through which we can avoid being lazy. As for myself, I occasionally try to debug and fix the code myself instead of relying on coding tools. That doesn't give superhuman feeling like writing a whole project by hand, but still that helps.
Can't say fortunately or unfortunately, but we have no other choice but to keep up this way.
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#85Earlier quoted context omitted.
> would you mind clarifying how you do learn? Practice > Everyone has different learning styles so I tend to take a different strokes for different folks attitude Okay but at the end of the day the only way to actually learn (and demonstrate that you've learned anything) is by actually doing it And I don't really consider "I got the AI to do it" as actually doing it, which is why I'm questioning what you've actually…
I guess I don't understand what about any aspect of what I explained gave you the impression that I might not have put what I learned into practice. This is going to sound like I'm fucking with you, but I'm deadly serious: if someone taught you how to do something and you later learned that that person was actually an LLM masquerading as a human, would you forget what you had learned? It's actually not impossible tha…
Of course it's traumatic. It is undermining the value of my knowledge and skills in a time when the economy is extremely rocky and I'm afraid for my future
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#86[flagged]
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#87Several weeks ago, I spent about a week fully reverse engineering a Stereomaker pedal. It accepts a mono signal and produces a stereo field using a 5-stage all-pass filter to mess with the phase without the use of delay (which sounds cheesy and creates a result that doesn't mix well back to mono). I've not really worked with audio circuits previously, and I'd been intimidated to approach the domain. My journey was ra…
Its not as simple as just being lazy, our brains are hardwired to take the path of least resistance. I believe someone industrious like you is the exception and not the rule which is why industrious people do well in life and a priased.
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#88> not treating it as your TikTok of pretend learning
Nah, YC has another website for that already...
/s
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#89Earlier quoted context omitted.
This is a phenomenal example of exactly what I am advocating. Notice you didn't ask the AI to 'just design a stereo pedal for me.' You interrogated it, reasoned about netlists, and forced the concepts into your brain through intense friction. That is pure deep work.
Throughout the reverse engineering process, the LLM and I both were expecting each op-amp stage to use the next ladder value capacitor. We'd talked ourselves into how and why that would make sense. At the end I was curious enough that I desoldered those five caps and realized that they were all 2.2nF except for the last stage which was 1nF. I brought that news back to the LLM and we realigned our understanding of how…
[dead]
Re: The risk of AI isn't making us lazy, but making "lazy" look productive
#90Earlier quoted context omitted.
This is a phenomenal example of exactly what I am advocating. Notice you didn't ask the AI to 'just design a stereo pedal for me.' You interrogated it, reasoned about netlists, and forced the concepts into your brain through intense friction. That is pure deep work.
Throughout the reverse engineering process, the LLM and I both were expecting each op-amp stage to use the next ladder value capacitor. We'd talked ourselves into how and why that would make sense. At the end I was curious enough that I desoldered those five caps and realized that they were all 2.2nF except for the last stage which was 1nF. I brought that news back to the LLM and we realigned our understanding of how…
[dead]