From Failure to Focus
A developer shares lessons from two failed CI/CD products and how they led to creating CI Insights, an observability tool for CI pipelines.
A developer shares lessons from two failed CI/CD products and how they led to creating CI Insights, an observability tool for CI pipelines.
Summary of a panel discussion at NVIDIA GTC 2025 on insights and lessons learned from building real-world LLM-powered applications.
Senior engineers must excel at communication and problem articulation, not just technical skills, to be truly effective.
Explores how intentional rituals can build belonging, engagement, and culture within engineering teams, with examples from past workplaces.
Explores why complex ideas and systems are often favored over simpler ones in tech and academia, and argues for the advantages of simplicity.
A software engineer draws parallels between the perfect, durable design of an IKEA clock and the principles of good software design.
A data scientist explains the 'Why, What, How' framework for writing effective technical documents like one-pagers, design docs, and after-action reviews.
Challenges the view that management is a promotion and engineering a demotion, arguing for cultural change in tech organizations.
A discussion on defining a software team's 'critical path' by focusing on business-critical processes that directly impact revenue and customer experience.
A candid look at the realities of being a Product Manager, emphasizing data gathering, customer interaction, and team dynamics over high-level strategy.
A personal reflection on the excitement and technical significance of SpaceX's historic Falcon 9 rocket landing, which could revolutionize spaceflight economics.
SUSE's Hack Week allows engineers to work on self-chosen projects, fostering innovation, learning, and collaboration.
A blueprint for product management focusing on building trust, establishing velocity, and strategically killing scope to align product and engineering teams.
A developer's perspective on why solving new problems is easier to sell than making marginal improvements to existing solutions.
A developer argues for creating novel solutions over incremental improvements, focusing on unsolved problems for easier market entry.