|
|
| | Ask HN: How to avoid passive use of AI? | | 7 points by uscnep-hn 3 months ago | hide | past | favorite | 16 comments | | It seems that productivity expectations are increasing with AI, but at a cost to our brains (as many studies have found). So I’m concerned about how we can use AI in a proactive and critical-thinking way, rather than passively, both in coding and in everyday life. And is it possible to maintain the same productivity expectations? For example, I'm currently working on a toy project, and I'm much slower without AI. rather than create a small MVP with Claude and then refine it. |
|

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
|
Why would you use a car? studies show walking is better. Why would you use a calculator? studies show mental math sharpens your brain. Why would you type on a computer? studies show writing on a physical paper is better for you.
Fundamentally people tend to use AI to get a result and then just use it instead of critically thinking over it. It makes sense, we take the path of least resistance. Why care about how something works when it just works? This leads to cognitive decline.
Rather I propose that you use AI as one of the greatest search engines ever invented. Think of AI (LLMs) as a dataset of fixed knowledge that can talk back to you and actually help you find the information you want.
When I was looking into making selenium scripts, that I had to write for work, more robust, I came up with a solution to create an object for each page and use that object to navigate and interact with the page. I then had a conversation with gemini pro regarding this where it told me that, what I am trying to achieve is technically just Page Object Model (POM), a pre-existing concept in the world of test automation. This lead to a deep dive into the advantages/disadvantages and I then pitched it as a change to better write selenium code and it was accepted at work.
Likewise, you should not use AI to vomit you code but as a rubber duck that quacks back at you [0]
[0] https://en.wikipedia.org/wiki/Rubber_duck_debugging