HN user

sid_talks

19 karma
Posts0
Comments7
View on HN
No posts found.

Cannabis dependency really can sneak up on people, and for some it’s quite difficult to get off it, with real physical and emotional symptoms.

Throughout my university years, many of my peers smoked cannabis on a daily basis, often several times a day. Most of them seemed oblivious to the fact that they might have developed a dependence; whenever anyone tried to talk to them about it, they dismissed it, claiming cannabis is completely benign and nothing to worry about. Today, I personally know that at least a couple of them developed serious mental and physical problems, and to this day, they are unable to cope with life without being high.

There should be more awareness about safe cannabis use and its risks rather than framing it as a "healthier" alternative to other drugs, with people usually saying "at least I am not doing X, I am just smoking weed".

AI does make me more productive. At least until the stage of getting my idea to the "working prototype stage". But in my personal experience, no one has been realistically able to get to the 10x level that a lot of people claim to have achieved with LLMs.

Yes, you do produce more code. But LoC produced is never a healthy metric. Reviewing the LLM generated code, polishing the result and getting it to production-level quality still very much requires a human-in-the-loop with dedicated time and effort.

On the other hand, people who vibe code and claims to be 10x productive, who produces numerous PRs with large diffs usually bog down the overall productivity of teams by requiring tenuous code reviews.

Some of us are forced to fast-track this review process so as to not slow down these "star developers" which leads to the slow erosion in overall code quality which in my opinion would more than offset the productivity gains from using the AI tools in the first place.

Trust but verify.

I guess I should have used ‘completely trust’ instead of ‘trust’ in my original comment. I was referring to the subset of developers who call themselves vibe coders.