60 lines
4.3 KiB
Markdown
60 lines
4.3 KiB
Markdown
icon:: ✏️
|
||
generation_time:: [[2026-01-23]] T11:00:02Z
|
||
|
||
- # **TODOs and IDEAs**
|
||
- {{query (and [[TODO]] [[KaraKeep-Highlights]] (or [[Ideas]] [[KaraKeep-Highlights]]))}}
|
||
query-table:: true
|
||
query-properties:: [:block]
|
||
- ## **“Vibe Coding”: The Future of Development or a Generational Divide? | CodeGPT**
|
||
source:: https://www.codegpt.co/blog/vibe-coding-future-or-hype
|
||
url:: https://karakeep.diruscio.org/dashboard/preview/osk8ozdguev9vbkw6ufwgesi
|
||
tags:: [[AI-Assisted-Coding]] [[Artificial Intelligence]] [[Programming-Productivity]] [[Software Development]] [[Tech-Industry-Trends]]
|
||
- The AI is treated as a "typing assistant" or "pair programmer."
|
||
background-color:: green
|
||
- The human acts as: The "guide, tester, and refiner"—maintaining full control and responsibility.
|
||
background-color:: blue
|
||
- The proponents of "vibe coding" (Definition 2) argue for a fundamental shift in the developer's role, from implementer to designer and strategist.
|
||
background-color:: blue
|
||
- A healthcare professional with no coding background can now prototype a patient tracking system.
|
||
background-color:: green
|
||
- "weekend toy projects" with tools like Cursor and Claude
|
||
background-color:: green
|
||
- "programming by intention". The AI handles the "syntactic details" and "technical implementation", liberating the human to focus on "higher-level design" and "creative problem-solving".
|
||
background-color:: green
|
||
- The promise of vibe coding is cognitive liberation, reframing the bottleneck in software from technical skill (writing syntax) to product vision (knowing what to build).
|
||
background-color:: blue
|
||
- Security Vulnerabilities
|
||
background-color:: blue
|
||
- Technical Debt and Maintainability
|
||
background-color:: blue
|
||
- This creates a "debugging nightmare". As one developer put it: "Debugging AI-generated code can be harder than writing it manually" because when an AI writes the code, the developer has no "mental map" of its logic.
|
||
background-color:: green
|
||
- > **Note:** #P1
|
||
- The hype of "10x productivity gains" is directly challenged by empirical data. A Randomized Controlled Trial (RCT) studying experienced developers working on real open-source repositories found that using AI tools made them 19% SLOWER.
|
||
background-color:: green
|
||
- The Skillset Developers "manage AI rather than just write code".
|
||
background-color:: green
|
||
- it's intelligent orchestration. The developers who will thrive in this new landscape are not those who abdicate responsibility to AI, but those who learn to conduct it.
|
||
background-color:: blue
|
||
- it's about humans with AI, working in a careful, intentional partnership.
|
||
background-color:: green
|
||
- > **Note:** [[P1]]
|
||
- From Meme to Mainstream: Defining the Phenomenon
|
||
background-color:: green
|
||
- > **Note:** This is related to [[PAPERS/J-Collaborative-Development]]
|
||
|
||
- ## **L’eclissi del pensiero critico? Intelligenza Artificiale, debito cognitivo e responsabilità**
|
||
source:: https://www.quotidianosanita.it/uncategorized/leclissi-del-pensiero-critico-intelligenza-artificiale-debito-cognitivo-e-responsabilita/
|
||
url:: https://karakeep.diruscio.org/dashboard/preview/q145b7y1pzntp7p8rcnkuwvy
|
||
tags:: [[Artificial Intelligence]] [[Cognitive-Science]] [[Critical-Thinking]] [[Human-Computer-Interaction]] [[Medical-Education]]
|
||
- DEFT-AI che può offrire un approccio strutturato e di buon senso per promuovere il pensiero critico nelle interazioni con i sistemi di IA.
|
||
background-color:: yellow
|
||
- saper riconoscere quando poter fare affidamento (modalità cyborg) e quando invece è necessario confermare criticamente gli output (modalità centauro).
|
||
background-color:: yellow
|
||
- sostituire la logica del “trust and go” (fidarsi e andare avanti) con la metodologia del “verify and trust” (verificare e fidarsi) in cui l’output dell’IA viene prima valutato secondo il principio di esplicabilità e poi utilizzato.
|
||
background-color:: yellow
|
||
- nuove competenze o si potenziano quelle esistenti per adattarsi a tecnologie e pratiche emergenti (up-skilling).
|
||
background-color:: yellow
|
||
- In definitiva con l’up-skilling non solo si incrementa efficienza e sicurezza ma ci si protegge anche dai rischi di deskilling, garantendo che l’apprendimento e la pratica professionale evolvano insieme alla tecnologia.
|
||
background-color:: yellow
|