6 links tagged with all of: software-development + accountability
Click any tag below to further narrow down your results
Links
The author critiques the reliance on AI tools like LLMs for code generation, arguing that it undermines the essential thinking and problem-solving skills of developers. They compare generated code to fast fashion—appealing but often flawed—emphasizing the importance of accountability and understanding in software development.
The article critiques common practices in team retrospectives that lead to inaction and documentation without resolution. It emphasizes the importance of immediate problem-solving, clear ownership of tasks, and implementing permanent fixes to foster a culture of continuous improvement.
This article discusses the concept of Write-Only Code, where production code is generated by AI and often never read by humans. It explores the implications for software development roles, accountability, and the need for new practices in managing code that cannot be reviewed line by line.
This article emphasizes the responsibility of software engineers to deliver code that has been thoroughly tested and proven to work, both manually and automatically. It argues against the trend of relying on AI tools to submit untested code and stresses the importance of accountability in the development process.
The keynote presentation discusses the concept of accountability within software departments, emphasizing the importance of defining it internally rather than allowing business partners to impose their interpretations. The speaker draws parallels between historical biases, software development practices, and the misunderstandings that arise when teams attempt to implement methodologies like Extreme Programming without fully grasping their intent.
The article discusses the emerging trend of "vibe coding," where developers prioritize intuition and feelings over structured methodologies. Critics argue that this approach can lead to unproductive outcomes and a lack of accountability in software development practices. The piece highlights the tension between traditional coding practices and the growing acceptance of vibe-based methods in the tech industry.