#Devops
12 notas · última:
Books Every Software Engineer Must Read in 2024
The page argues that developers should invest in lasting fundamentals rather than short-lived frameworks, and recommends books on software development, architecture, testing, distributed systems, DevOps, leadership, and habits.
You're getting your last mile wrong
The article argues that software teams should treat production delivery as part of development from the start, so projects stay potentially shippable instead of facing costly last-mile delays and bugs.
How to Create a Learning Culture: 9 Leadership Strategies for Defining Workplace Success
A page outlines nine leadership patterns for building a learning culture: celebrate learning moments, support experimentation, make time for learning, and use OKRs, vulnerability, MVPs, audits, pain, and intent to reinforce growth.
Estimates – a necessary evil? - Erik Thorsell
The post argues that estimates help product owners balance priorities, release dates, and technical debt, but become harmful when treated as deadlines. Continuous updates are presented as the better practice.
How to Write Less Code for More Money
The post argues that mid-career developers can find better pay and less routine coding in QA, DevOps, specialized consulting, people management, or hybrid roles that mix support, teaching, and refactoring.
10 Books Every Senior Engineer Should Read
Semaphore lists ten books that shaped its engineering culture, covering agile practice, delivery pipelines, remote work, project management, data systems, SRE, microservices, and modern software engineering.
How to build stable systems
The guide argues that stable systems stay under developer control, ship in small reversible steps, and favor limited scope, reproducible builds, strong testing, and operational safety.
7 DevOps Habits
Forrester analysts Glenn O'Donnell and Kurt Bittner outline seven DevOps habits centered on collaboration, outside-in thinking, automation, simpler environments, systems engineering, feedback loops, and developer support.
Architecture is abstract until operationalized
The post argues that software architecture is only a snapshot until it is implemented, upgraded, monitored, and able to survive real operational conditions. DevOps, continuous delivery, and microservices make those concerns part of design.
Problematic deployment is over
The page contains only an image and the credit line “by uaiHebert,” so it does not state any further argument or explanation about the deployment itself.
Developers Need to Broaden Their Range
Mike Loukides argues that full-stack work means broad familiarity with the stack, design, hardware, networking, cloud, data, and tooling, so developers can collaborate well across specialties.
A Gentle Introduction to Ember
The page mainly shows InfoQ account prompts and navigation, plus a featured DevOps talk. It does not provide content about Ember beyond the title and page framing.