Video game / the ship: murder party

We May Have DevOps, But Does Ops Have the Dev?

Back in 2013, Pager Duty’s Ranjib Dey surmised that it would take ages for traditional operations teams to learn and adopt mainstream development technologies. The opinion sparked quite a lively discussion around what those mainstream development technologies are, what hurdles exist for operations team to adopt them, and whether it all would be as glacial as Dey guessed. For Episode 58, we welcome Ranjib to the show for a panel discussion to revisit the tweet and look to see if anything has improved in the last 2 years. Join the panel as we parse through the puzzle of:

We May Have DevOps, But Does Ops Have the Dev?

Join J. Paul Reed, aka @JPaulReed, Youssuf El-Kalay, aka @buildscientist, Seth Thomas, aka @cheeseplus, and J. Michael McGarr, aka @SonOfGarr for the discussion, plus a the last couple of weeks in News & Views and another Tool Tip!

Note: the audio levels on this episode were not set quite correctly; we’re aware of the issue and will fix it for the next episode. Apologies for the poor quality.

Your browser does not support the audio tag.

Or, download Episode 58, or any of our previous shows!

Show Links/Notes

• 1:32 – News & Views
  • The OpenBSD team reimplements the venerable sudo tool: introducing doas
  • “Father Time” Harlen Stenn gets funded to maintain NTP for yet another year
  • Linux Foundation introduces “badges” for secure open source software
  • Badge criteria: available on GitHub
  • The reason you shouldn’t upgrade to .NET 4.6 reveals a fascinating debugging tale…
• 15:31 – Main Segment: We May Have DevOps, But Does Ops Have the Dev?
  • Ranjib’s original Tweet heard ’round the DevOps Twittersphere, from back in 2013!
  • Netflix’s Roy Rappoport at Monitorama 2015 on Business Insight platform
  • Primer’s on DRY and SOLID software development principles
  • Our episode with Ruby author Sandi Metz: Practical Object OO (and Cat!) Design with Sandi Metz!
  • The cautionary
• 58:55 – ToolTip
• devopsconferences.com has the latest

Join Us!

How long do you think it will take for mainstream development practices to be one in the same with mainstream operations practices.

How have you gotten your team to become more dev-like (or more ops-like)?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

Системные требования Ship: Remasted

Второе, что стоит сделать при возникновении каких-либо проблем с Ship: HD, это свериться с системными требованиями. По-хорошему делать это нужно еще до покупки, чтобы не пожалеть о потраченных деньгах.

Минимальные системные требования Ship: Remasted:
Windows 7, Процессор: Intel Xeon E5520, 4 GB ОЗУ, 3 GB HDD, NVIDIA GeForce GTX 260 Видеопамять: 512 MB, DirectX 9.0, Широкополосное подключение к интернету, Клавиатура, мышь

Посмотреть рекомендуемые требования

Каждому геймеру следует хотя бы немного разбираться в комплектующих, знать, зачем нужна видеокарта, процессор и другие штуки в системном блоке.

Developing CareerOps

It’s been awhile, but we’re finally back, and special guest Katherine Daniels (aka @beerops) is with us to talk over career development in a DevOps context! We discuss All The Things related to leveling up your career, including specialization vs. generalists, training and learning (especially if you don’t have a degree in computer sciency things), and some techniques you can employ to make sure your career doesn’t stagnate! Join us as we delve into:

Developing CareerOps

Join J. Paul Reed, aka @SoberBuildEng,

EJ Ciramella, aka @eciramella, Sascha Bates, aka @sascha_d, J. Michael McGarr, aka @SonOfGarr, and Katherine Daniels, aka @beerops for the discussion, plus the month in News & Views and a brand new Tool Tip!

Your browser does not support the audio tag.

Or, download Episode 53, or any of our previous shows!

Show Links/Notes

• @beerops’ On Disconnecting
• 3:24 – News & Views
  • Development from DockerCon!
  • Top intern salaries: really that crazy?
  • Dave Farley’s often-forgotten strategies for effective acceptance testing
  • Martin Fowler on The Test Pyramid
  • Adventures in building Vim from 1993
• 15:20 – Main Segment: Developing CareerOps
  • Nathen Harvey’s Quit Your Job (video)
  • Silicon Valley’s Dirty Little Secret: “The Hotel 22“
  • CoffeeOps, all over the place!
• 50:14 – ToolTip

Tool Tip

Paul introduces us to Scott Muc and Subhas Dandapani’s DevOpsBookmarks.com; some hilarity ensues.

(See also: O’Reilly’s similar developer field guide.)

Join Us!

What do you do to make sure your career doesn’t stagnate?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

I Don’t Always Test, But When I Do…

Do you test? Do you want to test? For many operations and build/release engineers (and even some developers!), testing can be a bit of a foreign concept. It’s hard to pay attention to getting to 100% code coverage on your unit tests for your inrastructure cookbooks and manifests when the infrastructure is on fire! But… maybe that’s why it’s on fire? For this episode, Mike McGarr walks us through the nuts and bolts of testing, so we can all become better testers, and start integrating testing into our workflows, even if we’re not developers. Join us for:

I Don’t Always Test, But When I Do…

Join J. Paul Reed, aka @SoberBuildEng, Seth Thomas, aka @cheeseplus, Pete Cheslock , aka @petecheslock, J. Michael McGarr, aka @SonOfGarr, and Katherine Daneils, aka @beerops for the discussion, plus a the last couple of weeks in News & Views and a special O’Reilly guest!

Episode 55 is sponsored by

Your browser does not support the audio tag.

Or, download Episode 55, or any of our previous shows!

Show Links/Notes

• 2:59 – News & Views
  • Google shuts down Google Code
  • HP attempts to patent Continuous Delivery
  • Why don’t game developers use test-driven development?
  • PackageCloud.io ships their enterprise service
• 18:08 – Main Segment: I Don’t Always Test, But When I Do…
  • The Testing Pyramid returns!
  • Netflix on an 8-bit Nintendo?!
• 51:28 – A Special Guest
• Velocity: Santa Clara
• ALM Forum
• Various DevOps Days around the World

A Special Guest

Paul and Courtney Nash, O’Reilly’s Director of Strategic Content and Velocity Conference tri-chair, discuss the thematic changes for Velocity Conference.

Join Us!

What is your relationship with testing?

What’s the best story where a unit or acceptance test totally saved your bacon?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

Появляется чёрный экран в The Ship: Остаться в живых

• Драйверы установлены/обновлены, но The Ship: Остаться в живых всё равно отказывается работать
  нормально? Тогда нужно проверить ПО, установлены ли вообще необходимые библиотеки? В
  первую очередь проверьте наличие библиотек
  
  Microsoft Visual C++
  
  и
  
  .Net
  Framework
  
  , а также наличие «свежего»
  
  DirectX
  
  .
• Если ничего из вышеописанного не дало нужного результата, тогда пора прибегнуть к
  радикальному способу решения проблемы: запускаете The Ship: Остаться в живых и при появлении
  чёрного экрана нажимаете сочетание клавиш «Alt+Enter», чтобы игра переключилась на
  оконный режим. Так, возможно, откроется главное меню игры и удастся определить
  проблема в игре или нет. Если удалось перейти в оконный режим, тогда переходите в
  игровые настройки The Ship: Остаться в живых и меняйте разрешение (часто получается так, что
  несоответствие разрешения игры и рабочего стола приводит к конфликту, из-за которого
  появляется чёрный экран).
• Причиной этой ошибки также могут послужить различные программы, предназначенные для
  захвата видео и другие приложения, связанные с видеоэффектами. А причина простая –
  появляются конфликты.
• И напоследок – проблема, вероятнее всего, может быть связана с технической
  составляющей «железа». Видеоадаптер может перегреваться, как и мосты на материнской
  плате, что влечёт за собой уменьшенное энергопотребление видеокарты. Мы не будем
  вдаваться в детальные технические подробности, поэтому просто рекомендуем в
  обязательном порядке почистить свою машину от пыли и также поменять термопасту!

Extinguishing Burnout

2015 was the year that we saw the issue of systemic, professional burnout make its unfortunate entrance onto the stage of high technology and DevOps. In this episode, we interview the world’s foremost expert on burnout, Dr. Christina Maslach, a psychology professor and researcher at UC Berkeley about burnout, its causes and effects, and most importantly: what we can do about it. It’s been a year since a series of events started the conversation in our industry and it has all but died back down again. But for people, teams, and organizations struggling with burnout, it remains a critical issue for the industry to confront. Join the entire Ship Show Crew and Dr. Maslach for a very special episode of the podcast:

Extinguishing Burnout

Join J. Paul Reed, aka @jpaulreed, Youssuf El-Kalay, aka @buildscientist, EJ Ciramella, aka @eciramella Sascha Bates, aka @sascha_d Seth Thomas, aka @cheeseplus, Pete Cheslock, aka @petecheslock, J. Michael McGarr, aka @SonOfGarr, and Katherine Daniels, aka @beerops for the discussion, plus the last few of weeks in News & Views and a special end segments.

Your browser does not support the audio tag.

Or, download Episode 60, or any of our previous shows!

Show Links/Notes

• 2:23 – News & Views
  • Netflix and Google announce Spinnaker, Asgard’s successor
  • As containers continue heating up, 10 Things to Avoid in Docker Containers
  • Pete’s view on “Stateful Containers“
  • Paul’s architectural diagram of containers with interdependent microservices
  • OpenBSD’s LibreSSL unaffected by the new DROWN OpenSSL vulnerability
  • Glibc vulnerability reminds us all Glibc exists
  • Etsy releases tools for managing your ELK cluster when, for instance, you need to upgrade glibc
• 24:00 – Main Segment: Extinguishing Burnout
  • 2015 Velocity Santa Clara panel on Burnout
  • Christie Koehler’s departure from Mozilla
  • Dr. Maslach’s original research on the topic: Burnout: The Cost of Caring
  • Banshing Burnout: Six Strategies for Improving Your Relationship with Work
  • Of her books, Dr. Maslach recommends reading The Truth About Burnout: How Organizations Cause Personal Stress and What to Do About It first
• 1:19:20 – An End Segment to End All End Segments
  • The “Continuous All the Things” episode
  • SAY THE WORD, PETE!!
  • Blooper reel episode (in the final segment)
  • The Monitorama episode
  • I don’t always test… and I didn’t.

Join Us!

What is the best strategy you’ve found, personally or with your team, to tackle burnout?

What was your favorite episode or moment of The Ship Show?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

Infinite Diversity in Infinite Combinations

The topic of diversity in the technology and software development industries has been important to The Ship Show co-hosts ever since our first episode. It’s also one we hope our audience is interested in as well or, at least, aware of.

In 2014, we announced our Ship Show Diversity Program.

It was an experiment to find a way to help improve the state of diversity within our industry. It focused on increasing the attendee diversity of the various tech conferences in the “build engineering, DevOps, release management, and everything in between”-space.

It was something new for us. We fumbled a bit. We made a few mistakes.

It didn’t quite work out the way any of us had envisioned, at least not entirely.

But we learned a lot.

And we were able to help some individuals attend tech conferences. So by at least that measure, we were somewhat successful.

But at the end of the year, when we looked back at what we’d intended and envisioned and what we were able to do, we didn’t feel we had done enough.

So the co-hosts discussed it and we decided The Ship Show should make up the difference by donating to various organizations.

These organizations all do really important, on-the-ground work to improve our industry’s diversity story; we were able to donate over $2,000 in total to:

• Girls Who Code
• Code 2040
• Trans*H4ck
• TransCode

In 2015, The Ship Show plans to continue working on trying to improve the state of diversity within our industry.

And we’ll continue refining the diversity program we started in 2014, trying to make it better serve the needs of our listeners, our community, and our industry.

This is our 2015 resolution.

(Our other resolution is to get a new podcast out; it’s on its way, we promise!)

Oh, and Happy New Year!

Packaging Your Software for Maximum Freshness

It’s a part of software developers hate writing and operations teams hate dealing with: packaging, installers, and upgrade scenarios. In Episode 54, the team looks at the fundamentals of packaging, tools that make the job both harder and easier, installer horror stories, and some good practices to make sure your packages don’t make others want to rip their hair out. Join the crew as we provide some tips for:

Packaging Your Software for Maximum Freshness

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, Seth Thomas, aka @cheeseplus, Pete Cheslock , aka @petecheslock and J. Michael McGarr, aka @SonOfGarr for the discussion, plus a the last couple of weeks in News & Views and a new Tool Tip!

Episode 54 is sponsored by

Your browser does not support the audio tag.

Or, download Episode 54, or any of our previous shows!

Show Links/Notes

• 3:03 – News & Views
  • We have a new contender: Configi
  • Who secures your secure shell?
  • How sloppy consumer electronics release engineering losing and recovering your NAS password?
  • Finally answering:
• 14:36 – Main Segment: Packaging Your Bits for Freshness
  • FPM
  • PackageCloud: Package repositories in the cloud
  • RPM Lint
  • Debian lint tool
  • Winstone Servlet Container
  • SpringBoot
  • Gradle’s Nebula.os-package
• 58:16 – ToolTip
• Lean UX in New York coming up!
• ChefConf
• Velocity Santa Clara: coming up
• devopsconferences.com has the latest

Join Us!

How do you package your bits?

What’s the weirdest installation or upgrade problem you’ve ever run into?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

Низкий FPS, The Ship: Остаться в живых тормозит, фризит или лагает

• Запустите диспетчер задач и в процессах найдите строку с названием игры
  (The Ship: Остаться в живых). Кликайте ПКМ по ней и в меню выбирайте
  
  «Приоритеты»
  
  , после
  чего установите значение
  
  «Высокое»
  
  . Теперь остаётся лишь перезапустить
  игру.
• Уберите всё лишнее из автозагрузки. Для этого все в том же диспетчере задач нужно
  перейти во вкладку
  
  «Автозагрузка»
  
  , где нужно отключить лишние процессы при
  запуске системы. Незнакомые приложения лучше не трогать, если не знаете, за что они
  отвечают, иначе рискуете испортить запуск системы.
• А также рекомендуем в настройках, связанных с энергопотреблением, установить
  
  «Максимальную производительность»
  
  . То же касается и видеокарты: нужно
  установить максимальную производительность в настройках графического процессора (это
  можно сделать в
  
  «Управлении параметрами 3D»
  
  ), а в фильтрации текстур
  выбирайте параметр
  
  «Качество».
  

• Если ваша видеокарта от Nvidia по возрасту не старше серии графических процессоров
  GTX 10, тогда частоту кадров вполне реально поднять за счёт ускорения работы с
  видеокартой. Для реализации задуманного опять-таки нужно открыть
  
  «Панель
  управления»
  

  Видеокарты, перейти
  в уже знакомую вкладку
  
  «Управление параметрами 3D»
  
  и выбрать в списке с
  программами игру, после чего отыскать
  
  «Вертикальный синхроимпульс»
  
  и кликнуть
  по нему, чтобы в меню выставить параметр
  
  «Быстро»
  
  .

• Следует удалить временные папки, ненужные файлы и кэш. На просторах интернета можно
  найти кучу самых разных программ, которые помогают это сделать. Мы рекомендуем
  воспользоваться для этого программой

  BleachBit

  или

  CCleaner

  .

• Проведите дефрагментацию или оптимизацию жёсткого диска. Для этого перейти в
  
  «Свойства жёсткого диска»

  вкладка
  «Сервис»

  «Дефрагментация» или
  «Оптимизация»
  
  . Кроме того, там же можно провести проверку/очистку диска, что
  в некоторых случаях помогает.

• В конце концов, перейдите на простое оформление, чтобы компьютер не нагружался
  ресурсоёмкими эффектами. К примеру, можно смело отключать встроенные отладчики,
  индексирование поиска и многое другое.

Лучшие видеокарты для комфортной игры в 1080p

Пусть 4K доминирует в заголовках и привлекает многих техноблоггеров, сейчас большинство игроков
предпочитает Full HD и будет это делать еще несколько…

Ошибка DirectX в The Ship: Остаться в живых

«DirectX Runtime Error»

«DXGI_ERROR_DEVICE_RESET»

«DXGI_ERROR_DEVICE_HUNG»

«DXGI_ERROR_DEVICE_REMOVED»

• Первым делом необходимо установить «чистую» версию драйвера вашей видеокарты (то
  есть не стоит сразу спешить устанавливать тот же GeForce Experience, ничего лишнего
  от AMD и аудио).
• При наличии второго монитора попробуйте отключить его, а также отключите G-Sync и
  любые другие виды дополнительных/вспомогательных устройств.
• Воспользуйтесь средством проверки системных файлов для восстановления повреждённых
  или отсутствующих системных файлов.
• В случае если используете видеокарту от Nvidia, тогда попробуйте включить
  
  «Режим
  отладки»
  
  в панели управления видеокартой.

• Часто причиной ошибки служит перегретая видеокарта, поэтому для проверки её
  работоспособности рекомендуем воспользоваться программой

  FurMark

  . Если это оказалось действительно так, тогда следует
  понизить частоту видеокарты.

• Если вдруг столкнулись с другими ошибками, тогда рекомендуем переустановить DirectX,
  но перед этим лучше на всякий случай удалить старую версию (при этом обязательно
  удалите в папке перед переустановкой все файлы начиная с
  
  «d3dx9_24.dll»
  
  и
  заканчивая
  
  «d3dx9_43.dll»
  
  ).

The Ship: Murder Party provides examples of:

• An Axe to Grind: The Fire Axe.
• Bookends:
• Bottomless Bladder: Averted; the call of nature is one of the needs that have to be satisfied as you’re wandering the ship.
• Butt-Monkey: The Captain of the Ship in single-player. You’ll rob him, then poison him, and then break into his hospital room and kill him, mostly for entirely circumstantial reasons.
• Camping a Crapper: As Bottomless Bladder is thoroughly averted, it’s possible to catch your target at their most vulnerable when they’re forced to answer the call of nature.
• Cherry Tapping: There’s ample opportunity for it with some of the less impressive weapons…
• Chessmaster: Mr. X, who sets up all the players to kill each other, but is not directly involved in any of it himself.
• Contract on the Hitman
• Dangerously Close Shave: The straight razor is one of the most powerful melee weapons in the game.
• Deadly Game
• Diesel Punk: Played with. While the game is set on a series of cruise ships from the 1920s and 30s, it in fact takes place in the present day. References to 2006 (the game’s year of release on Steam) can be found in certain areas.
• Drop the Hammer: An ordinary carpenter’s hammer, natch.
• Escort Mission: The ambassador is pushed by a wheelchair. Through his travels, a total of four goons will attack at different points on the trip.
• Expy: The psychiatrist looks and sounds a lot like Sigmund Freud.
  Psychiatrist: Tell me about… your mother.
• Flare Gun: A surprisingly effective and easy-to-find weapon.
• Frying Pan of Doom: One of the weapons available in the galley.
• Golf Clubbing
• Good Smoking, Evil Smoking: Mr. X, being a diabolical villain, naturally uses a long black cigarette holder.
• He Knows Too Much: Jimmy the Bellhop in the single-player game will inform you that Mr. X doesn’t pay the winning passengers and let them leave — he scuttles the ship and kills them all, to clean up loose ends. Getting the money to bribe your way off the ship before it gets sunk drives the plot of the single-player game.
• He Who Must Not Be Seen: Outside of backstory, Mr. X’s most prominent role in the game is… as a HUD element. Upon killing your quarry, their portrait will be replaced by one of Mr. X grinning from ear to ear; if you are yourself killed, you’ll get an image of Mr. X pouting.
• High-Class Gloves: The socialite wears a pair of long red gloves.
• Hospital Hottie: The nurse NPC.
• Improbable Weapon User: Any player playing the game. The weapons that can be used to off fellow passengers range from the mundane (pistols, knives, axes) to the absolute strange (scalpels, umbrellas, knitting needles).
• Locked in a Freezer: It’s possible to lure your target into a walk-in freezer, lock the door behind them and turn up the cold to maximum.
• Malevolent Architecture: Depending on whether you’re using it or it’s being used against you. You won’t notice it if you aren’t looking for it, but Mr. X seems to have a passion for both secret passages and traps. For example, one ship hosts
• Parasol of Pain: You can, if you so desire, off your target with an umbrella.
• Pretty in Mink: The socialite wears a white fox neck wrap.
• Poisoned Weapons: The most devious weapon you can use is a hypodermic needle filled with poison. Stab your target once and they will become violently sick, starting a countdown until they keel over. Just be sure they’re not so close to the medical bay that they can be cured first.
• Sauna of Death: Much like the freezer example above, you can roast anyone who wanders into the sauna by turning up the heat to lethal levels.
• Self-Imposed Challenge: The game scores everyone based on their bank account balance. This includes both Hunters (the main players) and Passengers (effectively spectators). Passengers do have needs and will end up using their money (which starts at $250 + $2500) at some point, and they can only get more money from wallets or coin purses dropped by those killed by their hunter or quarry. If a Passenger is more aware than the hunters, it is actually possible for him/her to beat most of the hunters in bank balance, even if they never die (which will typically require buying food and drink).
• Shout-Out: The crowbar’s description reads «Used by a Free Man.»
• Socialite
• Speaking Simlish: Most dialogue with non-player characters goes like this.
• Stocking Filler: On the nurse NPC that shows up in the lobbies of most maps’ sickbays. Those maps, however cleverly put her behind a chest-high counter that can’t be get around or get marked for trespassing if you do head behind it, so to get a view, one either has to quickly jump in front of the counter, or use the noclip cheat code.
• White Mask of Doom: Mr. X

The DevOps Checklist Manifesto

The DevOps community has long resisted a push to define the movement via instruments like cookbooks or manifestos, creating an interesting thread of “lack-of-definition” when describing DevOps and DevOps practices. This issue has come to a head in 2015, as some proponents think we’re long overdue to provide a stronger framework around what DevOps actually means in practice. For episode 59, we sit down with the creator of the DevOps Checklist, Steve Pereira, to talk through the items on the checklist, whether or not it’s a good idea to even have a checklist, and debate the finer points of what could become:

The DevOps Checklist Manifesto

Join J. Paul Reed, aka @jpaulreed, Seth Thomas, aka @cheeseplus, and Pete Cheslock , aka @petecheslock, for the discussion, plus a the last couple of weeks in News & Views and a Tool Tip!

Your browser does not support the audio tag.

Or, download Episode 59, or any of our previous shows!

Show Links/Notes

• Paul changed his Twitter name!
• 4:06 – News & Views
  • We predict the future: New attacks on NTP can defeat HTTPS
  • How is the NSA breaking so much crypto?!
  • Coding Academies: useful or nonsense?
  • x86 among the things now considered harmful
• 17:25 – Main Segment: The DevOps Checklist Manifesto
  • The DevOps Checklist
  • Based on the IxD Checklist
  • Devops Enterprise Summit 2014
  • Dimensions of Learning Survey
• 56:29 – ToolTip
• Scale 14 is in January!
• devopsconferences.com has the latest

Join Us!

How does your organization score on the DevOps Checklist?

What changes would you make to the checklist?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com

We Monitor the Monitorama

If DevOps is CAMS—culture, automation, metrics, and sharing—then it makes sense there’d be a conference on monitoring and metrics…and there is: Monitorama! In episode 56, the crew gets together with Jason Dixon , aka @obfuscurity, the founder of Monitorama to talk about the fourth incarnation of the conference. We do a deep dive into what all is encompassed when we say “monitoring,” why monitoring really isn’t about CPU load and memory, other things you can monitor, and why Paul was stupid for not coming to Monitorama earlier; join us, the crew, as…

We Monitor the Monitorama

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, EJ Ciramella, aka @eciramella Seth Thomas, aka @cheeseplus, Pete Cheslock, aka @petecheslock,
and Katherine Daniels , aka @beerops for the discussion, plus a the last couple of weeks in News & Views and a
fresh Tool Tip!

Episode 56 is sponsored by

Your browser does not support the audio tag.

Or, download Episode 56, or any of our previous shows!

Show Links/Notes

• 1:47 – News & Views
  • Let’s Encrypt to start shipping free certs next month
  • Mozilla claiming it will work tirelessly to deprecate HTTP
  • Is Go doomed to succeed?
  • GitHub looking for a billion-with-a-B dollar valuation
  • Paul Ford’s expose on what, exactly, code is
• 13:10 – Main Segment: Who Monitors the Monitorama
  • Kyle Kingsbury on Reimann
  • Laura Thomson on developer happiness
  • Roy Rapoport on Monitoring for business insight at Netflix
  • Brendan Gregg on monitoring at Netflix
  • Brendan Gregg’s book: Systems Performance: Enterprise and the Cloud
  • Stephen Boak on Monitoring design
  • The Stripe Team on holding game days
  • ALL the Monitorama Talks
• 51:30 – ToolTip
• DevOps Days Minneapolis
• DevOps Days Pittsburgh
• DevOps Days Chicago
• Velocity New York
• Agile 2015
• PuppetConf
• DevOps Enterprise Summit
• devopsconferences.com has the latest

Join Us!

What comes to mind when you hear the word monitoring? #monitoringlove or #monitoringsucks?

What’s your best monitoring story?

Join the discussion!

• Tweet at us: @ShipShowPodcast
• Shoot the crew an email: crew@theshipshow.com