A developer analyzes the failure of his SaaS project, College Conductor, sharing lessons on technology choices and focus.
A guide for software engineers on handling project estimation requests, offering strategies for bottom-up and top-down approaches.
A developer argues that well-run business meetings are crucial for software teams, distinguishing them from wasteful gatherings.
Explores adapting Agile/Scrum frameworks for data science teams, covering effective practices and necessary adjustments for the unique challenges of data science work.
Analyzes how Agile methodologies like Scrum can be applied to data science teams, highlighting effective practices and inherent challenges.
A panel discussion exploring whether Agile methodologies can be effectively applied to data science projects, featuring insights from industry experts.
Explains that Test-Driven Development is about iterative problem-solving and small steps, not just writing tests first.
Argues that Shadow IT, often seen as a risk, can be a valuable incubator for digital transformation and agile practices within organizations.
A critique of modern software development, arguing that the rush to release features in the cloud leads to perpetually buggy and poorly documented products.
A developer shares three powerful mindset principles from a Thoughtbot podcast: strong opinions loosely held, nothing is set in stone, and rejecting 'because we've always done it'.
Argues against the traditional 'tech lead' role in software teams, advocating for a collaborative, flat team structure to boost productivity and learning.
A developer's personal recap of attending the Topconf Tallinn 2013 software conference, covering talks, panels, and networking.
A software engineer shares five key principles for successful software delivery teams: flexibility, commitment, respect, communication, and reliability.
An inside look at Heroku's agile engineering culture, focusing on small team structures, self-chosen tools, and collaborative practices.
A developer shares key lessons learned from applying Domain-Driven Design (DDD) and Command Query Responsibility Segregation (CQRS) in an agile project.
Explores why enterprise software development struggles to connect with consumers, contrasting it with the agile, user-driven approach of startups.
A critique of traditional 'business requirements' gathering in software development, arguing it's an ineffective approach for building products.
