Posts in "videos"

docker has a straightforward CLI that allows you to do almost everything you could want to a container. All of these commands use the image id (ex. be29975e0098), the image name (ex. myusername/webapp) and the container id (ex. 72d468f455ea) interchangably depending on the operation you are trying to do. This is confusing at first, so pay special attention to what you’re using.

That paragraph switches around pretty quick there. “You followin’ me, camera guy?!” My OODA loop just got chaffed up.

From Getting Started with docker, from CoreOS

Coté Memo #050: not much on Friday, pretty boring for #50

Meta-data Hello again, welcome to #050. Today we have 54 subscribers, so we’re +1. Keep your best behavior up for this new person! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote. Sponsors FRONTSIDE.

NBC Universal turned to Spark to analyze all the content meta-data for its international content distribution. Metadata associated with the media clips is stored in an Oracle database and in broadcast automation playlists. Spark is used to query the Oracle database and distribute the metadata from the broadcast automation playlists into multiple large in-memory resilient distributed datasets (RDDs). One RDD stores Scala objects containing media IDs, time codes, schedule dates and times, channels for airing etc. It then creates multiple RDDs containing broadcast frequency counts by week, month, and year and uses Spark’s map/reduceByKey to generate the counts. The resulting data is bulk loaded into HBase where it is queried from a Java/Spring web application. The application converts the queried results into graphs illustrating media broadcast frequency counts by week, month, and year on an aggregate and a per channel basis.

NBC Universal runs Apache Spark in production in conjunction with Mesos, HBase and HDFS and uses Scala as the programming language. The rollout in production happened in Q1 2014 and was smooth.

Apache Spark Improves the Economics of Video Distribution at NBC Universal – Databricks

Shit’s bonkers out there. If I’d have proposed that to an architect “back in my day,” they’d have told me to go shot myself. They’d say: “uh, so, how about we just make a database table and ETL tool that does that?”

The last part - all those different things used - is amazing. Again, the architect would say: “we write things in Java. Try again.”

Granted, the point is: things like Spark and friends let you move beyond dealing with just tidy data and analitects. But, still, sloppy is as sloppy does, right?

Coté Memo #047: Selling a "platform" is one of the more difficult tech marketing tasks you'll ever do

Meta-data Hello again, welcome to #047. Today we have 52 subscribers, so we’re +/-0. I should write more awesome stuff to get more sign-ups! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote. Sponsors NEXT WEEK!

Coté Memo #046: Who's got the story?

Meta-data Hello again, welcome to #046. Today we have 52 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote. Sponsors SOON! If you’ve been waiting to get more than $200 off, it’s now $400!

Coté Memo #039: research agenda crafting, what Docker will spend $40m on, RAX no longer for sale

Meta-data Hello again, welcome to #039. Today we have 46 subscribers, so we’re +1. Dandy! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote. Sponsors See a preview of my talk at HCTS!

Why Did Docker Catch on Quickly and Why is it so Interesting? | The New Stack

Excellent piece. Too bad my folks didn’t get around to writing it first, but at least now it doesn’t need to be written. The insights in developer relations are great. At a meta-level: It’d be interesting to “crowd source” analyst research agendas by just bundling up pieces like this and original work and having that be your “corpus” of research. It’s what Techmeme does for news (no original content though). That’s kind of what InfoQ does for appdev and I think it works kind of well there (I find video a bit too oblique, but you could do 500-1,000 word summaries a a la Blinkist on all the conference talk videos InfoQ has - that’d be a good premium service).

Coté Memo #29: vRealize almost explained, Compuware gets bought, 1 year at 451

(I cross post my week-daily newsletter here, but also feel free to subscribe to it directly if you’d don’t want to follow CoteIndustries.com regularly.) Meta-data Hello again, welcome to #29. Today we have 36 subscribers, so we’re +3 - good job, subscribers! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.) See past newsletters in the archives, and, as always, see things as they come at Cote.

[audio cote.files.wordpress.com/2014/08/u…_010.mp3]

underdevpodcast:

Summary

We discuss thinking beyond human error as Bill starts to summarize the book Behind Human Error. It’s always helpful to look at how the system and process caused the wrong move. Also, thinking about hardware, and some nice feedback from designers.

Subscribe to the feed: http://feeds.feedburner.com/UnderDevPodcast

Your friends @cote and @BillHiggins

Hardware, what is it?

Follow-up on “design”

Human Error

  • Bill goes over Behind Human Error, causing us to discuss how various pipelines (systems) in product management work in waterfall and non-waterfall mode.
  • How do product managers fit in to a design-heavy pipeline?