One thing that continues to fascinate me is how after so many years I can still walk into IT organizations and see basic practices not being followed (e.g. Software Configuration Management or Continuous Integration or… ). Shouldn’t we all know better? I recently came across some slides from the late 90s and early 2000s that pretty much read like something that comes from a DevOps conference today
in an article in infoworld, adam bertram takes a look at some of the most common misconceptions and flawed implementations of devops. chances are, your company has fallen prey to at least one of them so read on. sign no. 1: you need to buy “the devops” “devops” cannot be obtained overnight with a simple check and a little training. it is a transformational approach to core processes, and it takes
in a series of 26 interviews with ceos, the harvard business review identified 3 key issues which were worrying business leaders around the globe. a major challenge was finding and retaining the right staff, especially in today’s technologically complex world. another big worry was the impact of operating in a global market – navigating this context and keeping a company of thousands of individual
Sanjay Zalavadia writes in an article for InfoQ that while Agile software development has proven to be a major benefit to various teams, it can affect businesses differently depending on their size and how they integrate the methodology into their operations. Zalavadia provides eight common areas which impact the adoption of agile development process in large enterprises: #1 - Lack of ClarityLarge
Are you working on a project, that runs badly? Have you ever asked yourself if your project is doomed to failure? In this blog, I will list 10 signs, that may help you to find out. Let me quickly tell you, who I am: I am working as an IT freelancer/consultant in the area of Java(TM) Enterprise Applications since 2000 and I must admit, that besides some successful projects, I also had to experience
The distinction is often made between agile adoption and agile transformation. The agile coach, from my experience, is often working at an intimate, team level; evangelizing, guiding, and embodying agile principles. When the entire enterprise is hoping to "transform", they need more than a coach; they need an agile consultant. No disrespect to agile coaches; many can and do perform enterprise evol
After reading Intercom on Customer Support, I thought it would be a great time to shine a light on a less glamorous growth tactic — stellar customer support. “The number one reason customers quit is because they believe the company no longer cares about them.” — IntercomThe 5 Key Customer Support MetricsAccording to Des Traynor and John Collins, there are 5 key metrics to a successful customer sup
To gather insights for DZone's Continuous Delivery Research Guide, scheduled for release on January 26, 2016, we spoke to 24 executives who are implementing continuous delivery in their own company or helping clients do so. Specifically we spoke to: Casey Kindiger, CEO, Avik Partners | Ez Natarajan, Vice President Cloud, Beyondsoft | Tom Cabanski, Director of Software Development, Blinds.com | Kur
For more insights on microservices, JVM languages, and more trends in Java, get your free copy of the DZone Guide to the Java Ecosystem! It is not necessary to change. Survival is not mandatory. —W. Edwards Deming The principles of the agile manifesto , now non-controversial and well accepted, speak to how to both write and deploy software more quickly and more safely—to production. Indeed, the ve
TL;DR: This blog outlines the key use-cases enabled by the newly released Docker plugins in the Jenkins communities. You can drill into more depth with an in-depth blog for each of the use case. The CloudBees team has actively worked within the community to release these plugins. Lately, I have been fascinated by how lean manufacturing radically improved the production of goods - the key being a f
What exactly makes a “good” API? That is a question a lot of developers ask when designing their first API. While there are hundreds of resources online, all with differing opinions about what defines “good,” the majority of them share some similar themes. Logical endpoint naming conventions, clear error messaging, accessibility, and predictability are all crucial pieces in any well-designed API.
Continuous delivery is a set of patterns and best practices that can help software teams dramatically improve the pace and quality of their software delivery. Instead of infrequently carrying out relatively big releases, teams practicing continuous delivery instead aspire to deliver smaller batches of change into production, but much more frequently than usual — weekly, daily, or potentially multi
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く