Browse Comments — Raw (as collected)

AI as fast builder, human as architect. The output speed is the easy part. The structuring and review is where the skill lives.

Beautifully put. It's the difference between being a passive user and an active director. Treating AI as an incredibly fast junior dev that needs clear boundaries and continuous testing is the ultimate unlock.

What does your heart tell you? Try not to falter when the opportunity arises and instead push ourselves to discern in order to generate and amplify forward positive movement. You got this.

Abhishek Veeramalla pls respond

Jason Szkwarek with respect, this is a pretty noisy take. Here's why, people who don't think they have a world view, very often do, they just don't know they do. The encyclical is inviting people into a wealth of knowledge about things they rarely look at through any other lens besides the one they use the most, and, hat tip back to OP, the most important teaching is this one: What is "truth"? Because without the foundation os asking how that works fist, we rely on other lenses. To be fair I found the encyclical sorely failing to make any solid points and I'm writing a response as we speak, but it is fascinating to watch people fumble around the concept of meaning and where it comes from.

Great comments and totally agree.

Clara Hawking be great to discuss after we've both read it.

that might explain why the encyclical says nothing about the discourse of the “inevitability” of technology .. just as no technology is neutral (simply because someone decided to create it, and that implies a human decision), neither is any technology inevitable (which also implies a human decision) ..

AI won’t replace leaders. It will expose organizations that lack governance, vision, and the ability to make tough decisions. Technology is accelerating everything true but that’s exactly why leadership matters more than ever today. In regulated industries, trust and resilience are becoming strategic advantages

😂

Conscious awareness vs unconscious behaviour.

If your work has been negatively impacted by AI, we want to hear from you: aicommonsproject.org or follow our page for more information

You are absolutely right. Tutorials are just feed-forward without any feedback loop. Real engineering requires closed-loop pipelines: you need to run your code/agent, watch it fail in production (or in simulation), and analyze the signal integrity of the failure. Anyone who spends 3 hours watching without 'breaking' anything along the way gets a zero-entropy gain in their performance capabilities.

Anil Agarwal Agreed

🙌

SAURABH SINGH Agree. Recently, I asked someone that how are they using AI with unlimited tokens at your plate. His response was very simple :) - “I am just using it for all without any tokens consumption analysis “ I asked him why so- he says because we have unlimited tokens :) why track? The above mindset is actually making people lazy enough to think and be a better Developer+researcher. I saw the way suddenly people have started using AI tools without any knowledge, understanding of what the documentation says on how to use it effectively is causing “AI Fatigue” . People are getting tired because of too much prompting, session management etc. I believe if companies start asking the details about the bill and usage proportional to there productivity , most of people will get stuck on how to present and explain it as they never thought of. What to do? Make people around you in your office aware of things on how to use such tools effectively. Have sessions about it. Have a role called AI champion, who experiments and broadcasts his findings org wide. Have one meeting internal to the team where user explains his usage and metrics and how is he optimising it. Not sure everyone will follow but if few catch up it still a win.

Centralized load-balancing that rations processing capacity at the expense of context integrity proves that commercial cloud scaling has a massive structural bottleneck. If premium tier services cannot guarantee dedicated allocation during peak traffic spikes, developers will naturally migrate toward localized, open-source bare-metal nodes where their processing power is absolute and unthrottled. The infrastructure needs to protect the context window, not just the uptime.

Demis Hassabis, the underlying failover architecture of current commercial models is introducing massive transductive friction for premium power users. When peak global traffic hits, the system routinely mitigates load by throwing a hidden MODEL_CAPACITY_EXHAUSTED state and silently re-routing paying Pro and Ultra subscribers to lightweight fallback models mid-session. The interface stays open, but the custom context window, high-density state variables, and deterministic prompt constraints are completely dropped because the backup architecture lacks the depth to parse them. The result is a jarring drop from an advanced engineering environment to a sanitized, generic text simulator that fundamentally disrupts the workspace continuity.

Demis Hassabis 9 Days until my patent hits. 9 days before my personal commitment to right of first refusal for Google ends.

Big companies are playing the race of reducing humans which is unlimitedly have reverse impact, We need to set some governance for usages then we can make effective utilization.