Podcast appearances and mentions of robert blumen

Tyler Flint, CEO of qpoint.io, joins host Robert Blumen for a conversation about managing external vendor dependencies, including several best practices for adoption. They start with a look at internal versus external services, including details such as the footprint of external services within a micro-services application, and difficulties organizations have tracking their service consumption, quantifying service consumption, and auditing external services. Tyler also discusses the security implications of external services, including authentication and authorization. They examine metrics and monitoring, with recommendations on the key metrics to collect, as well as acceptable error rates for external services. From there they consider what can go wrong, how to respond to external service outages, and challenges related to testing external services. The episode wraps up with a discussion of qPoint's migration from a proxy-based solution to one based on eBPF kernel probes. Brought to you by IEEE Computer Society and IEEE Software magazine.

Christian Mesh, tech lead of the OpenTofu project, speaks with host Robert Blumen about OpenTofu. They start with the history of terraform, terraform providers, license changes to open source projects, the origin of OpenTofu as a fork of terraform, and the structure of the OpenTofu organization. They further explore compatibility issues for HCL, providers, and modules, performance issues, and adoption, as well as significant features in the OpenTofu-included dynamic-provider iteration, and the roadmap for the project going forward. Brought to you by IEEE Computer Society and IEEE Software magazine.

Lukas Gentele, CEO of Loft Labs, joins host Robert Blumen for a discussion of kubernetes vclusters (virtual clusters). A vcluster is a kubernetes cluster that runs kubernetes application on a host kubernetes cluster. The conversation covers: vcluster basics; sharing models; what is owned by the vcluster and what is shared with the host; attached nodes versus shared nodes; the primary use case: multi-tenancy vcluster per tenant; alternatives - namespace per tenant, full cluster per tenant; trade-offs - isolation; less resource use; spin up time; scalability; how many clusters and how many vclusters should an org have? Deployment models for vclusters - helm chart with standard resources; vcluster operator; persistent storage models for vclusters; vcluster snapshotting, recovery, and migration. how many vclusters can run on a cluster? ingress, TLS and DNS. Brought to you by IEEE Computer Society and IEEE Software magazine.

Ganesh Datta, co-founder of Cortex.io, joins host Robert Blumen for a conversation about production readiness. The conversation covers the history of production readiness; its relationship to microservice architecture; the Google SRE model's impact on production readiness; production readiness checklists; the process; and production readiness transparency.

Jim Bugwadia, CEO of Nimrata and a committer to the kyverno projects, joins host Robert Blumen for a discussion of policy-as-code and the open source kyverno project. The discussion covers the nature of policies; policies and security; policies and compliance to standards; security scans that generate reports compared to tools that allow or deny operations at run time; kyberno as a kubernetes service; the kyveno helm charts; the components of kyverno; bootstrapping a kubernetes cluster with kyverno; installing policies; implementing policies; customizing policies; packaging and installing policies; kubernetes dynamic admission controllers; the kyverno admission controller; securing kyverno itself; observability of kyverno; types of reports and messages available to cluster users. This episode is sponsored by QA Wolf.

Luis Rodríguez, CTO of Xygeni.io, joins host Robert Blumen for a discussion of the recently thwarted attempt to insert a backdoor in the SSH (Secure Shell) daemon. OpenSSH is a popular implementation of the protocol used in major Linux distributions for authentication over a network. Luis describes how a backdoor in a supporting library was recently discovered and removed before the package was published to stable releases of the Linux distros. The conversation explores the mechanism of the attack through modifying a function table in the runtime; how the attack was inserted during the build; how the attack was carefully staged in a series of modifications to the lz compression library; the nature of “Jia Tan,” the entity who committed the changes to the open source project; social engineering that the entity used to gain the trust of the open source community; what forensics indicates about the location of the entity; hypotheses about whether criminal or state actors backed the entity; how the attack was detected; implications for other open source projects; why traditional methods for detecting exploits would not have helped find this; and lessons learned by the community. Brought to you by IEEE Computer Society and IEEE Software magazine.

Infrastructure engineer and Kubernetes ingress-Nginx maintainer James Strong joins host Robert Blumen to discuss the Kubernetes networking layer. The discussion draws on content from Strong's book on the topic and covers a lot of ground, including: the Kubernetes network's use of different IP ranges than the host network; overlay network with its own IP ranges compared to using expanded portions of the host network ranges; adding routes with kernel extension points; programming kernel extension points with IP tables compared to eBPF; how routes are updated as the host network gains or loses nodes, the use of the Linux network namespace to isolate each pod; routing between pods on the same host; routing between pods across the host network; the container-network interface (CNI); the CNI ecosystem; differences between CNIs; choosing a CNI when running on a public cloud service; the Kubernetes service abstraction with a cluster-wide IP address; monitoring and telemetry of the Kubernetes network; and troubleshooting the Kubernetes network. Brought to you by IEEE Software magazine and IEEE Computer Society.

William Morgan, founder of the Linkerd service mesh and CEO of Bouyant, joins SE Radio's Robert Blumen for a discussion of sidecars, service mesh, and a forthcoming enhancement to kubernetes to support sidecars natively. The conversation explores the origin of sidecars, sidecars and service mesh, and migrating service mesh to kubernetes. They take a deep dive into some aspects of running service mesh on kubernetes, the difficulties in running a sidecar container in a pod, and Kubernetes Enhancement Proposal (KEP) 753, which is intended to provide better native support for sidecar containers. William also gives some thoughts on the continuing relevance of service mesh.

Andy Suderman, CTO of Fairwinds, joins host Robert Blumen to talk about standing up a kubernetes cluster. Their discussion covers build-your-own versus managed clusters provided by cloud services, and how to determine the number of kubernetes clusters an organization needs. Andy describes best practices for automating cluster provisioning, and offers recommendations about customizations and opinionation of cloud service providers, choice of container registry, and whether you should run complementary services such as CI and monitoring on the same cluster. The episode also examines the day 0/day 1/day 2 lifecycle, cluster auto-scaling at the cloud service level, integrating stateful services and other cloud services into your cluster, and kubernetes secrets and alternatives. Finally, they consider the container-network interface (CNI), ingress and load balancers, and provisioning external DNS and TLS certificates for cluster services.

The Rational Egoist - A Conversation with Robert Blumen on Artificial Intelligence and the Entrepreneurial Mind In this episode of "The Rational Egoist," host Michael Leibowitz engages in a thought-provoking conversation with Robert Blumen, a software engineer with expertise in financial applications. Together, they delve into the intricate world of artificial intelligence (AI), dispelling common myths and setting the record straight on what constitutes true AI. Far from being mere calculators or search engines, AI emerges as a tool that can answer specific questions and perform complex tasks, like driving vehicles. Drawing from Objectivist principles, they explore AI's potential to revolutionise entrepreneurship, driving business innovation and growth much like the internet and computers have done in the past. While the ethical implications of AI are considered, the focus remains on its utility as an entrepreneurial tool. Moreover, they touch upon Ludwig von Mises' critique of socialism, arguing that just like a state-controlled system, a single AI cannot possibly emulate the dynamic interplay of individual minds in a free market. For a deeper dive, read Robert's article at https://mises.org/wire/ai-lacks-entrepreneurial-intelligence-plan-economy. Don't miss this episode where rational self-interest meets groundbreaking innovation. Michael Leibowitz is a renowned philosopher, political activist, and the esteemed host of the Rational Egoist podcast. Inspired by the philosophical teachings of Ayn Rand, Leibowitz passionately champions the principles of reason, rational self-interest, and individualism, seeking to empower others through his compelling work. His life's narrative exemplifies the transformative power of Ayn Rand's writings. Having faced challenging circumstances that led to a 25-year prison sentence, Leibowitz emerged from adversity by embracing the tenets of rational self-interest and moral philosophy put forth by Ayn Rand. This profound transformation propelled him to become an influential figure in the libertarian and Objectivist communities, motivating others to adopt reason, individualism, and self-interest in their own lives. Beyond his impactful podcasting endeavors, Leibowitz fearlessly engages in lively political debates, advocating for the protection of individual rights and freedoms through compelling YouTube videos and insightful interviews. His unwavering commitment to these ideals has garnered him a dedicated following of like-minded individuals. Leibowitz is a versatile author, co-authoring the thought-provoking book titled "Down the Rabbit Hole: How the Culture of Correction Encourages Crime." This groundbreaking work delves into societal attitudes surrounding punishment and rehabilitation, shedding light on how misguided approaches have contributed to the rise of crime and recidivism. Additionally, he has authored the book "View from a Cage: From Convict to Crusader for Liberty," offering an intimate portrayal of his personal journey while exploring the philosophies that influenced his transformation. As you embark on your intellectual journey, join Michael Leibowitz as he advocates for reason, individualism, and the pursuit of self-interest, inspiring others to embrace a philosophy that empowers and uplifts the human spirit. For a deeper exploration of his ideas and insights, don't miss the opportunity to read "Down the Rabbit Hole: How the Culture of Correction Encourages Crime," co-authored by Michael Leibowitz. And also, delve into his book "View from a Cage: From Convict to Crusader for Liberty." Both books are available for purchase using the following links: "Down the Rabbit Hole": https://www.amazon.com.au/Down-Rabbit-Hole-Corrections-Encourages/dp/197448064X "View from a Cage": https://books2read.com/u/4jN6xj

Jeroen Mulder, author of Multi-Cloud Strategy for Cloud Architects, joins host Robert Blumen for a discussion of public cloud, private cloud, and multi-cloud computing architectures and trends. They start by considering what defines cloud computing and what differentiates the major cloud providers, including whether they are more alike or different in the services they offer.  Jeroen discusses governance, regulatory compliance, and data locality as drivers of where enterprises want to run their workload. They explore use cases for multi-cloud, and discuss architectural challenges in migrating to kubernetes, as well as issues with networking, security, and identity management with multi-cloud architectures. Finally, they discuss running public cloud compute on on-prem resources with Anthos, Outback, and related technologies.

Stanisław Barzowski of XTX Markets and a committer on the jsonnet project joins SE Radio's Robert Blumen for a conversation about the jsonnet programming language. A superset of JSON, jsonnet adds programming language capabilities, particularly to address the need to handle large but mostly repetitive JSON configurations. They discuss the project's history, use cases for Grafana and Kubernetes config, interoperability with YAML, and consider details including the command line, constrained capabilities of the language, and objects and inheritance. They examine the toolchain: compiler, formatter, and linter, as well as test frameworks and testing, package management, and the language's performance. Barzowski describes four implementations -- go, C++, Rust, and Scala -- as well as popular libraries and the standard library.

On today's show, podcaster and economic writer Robert Blumen compares the idealistic dystopic future portrayed in science fiction to the harsh realities of the dystopic future Klaus Schwab is promoting, and explains how and why the definitions of words like "vaccine," "immunity" and "effective" have changed since the arrival of COVID-19. GUEST OVERVIEW: Robert Blumen, a software engineer with a background in financial applications. Blumen, who lives in San Francisco, has a physics degree from Stanford University and writes frequently for mises.org and Brownstone.org. He has spoken at economic and finance conferences on Austrian economics, and he is the editor of the podcast Software Engineering Radio.

Writer and podcaster Robert Blumen returns to discuss the big lie that the COVID "vaccines" had 95% effectiveness, and more. GUEST OVERVIEW: Robert Blumen, a software engineer with a background in financial applications. Blumen, who lives in San Francisco, has a physics degree from Stanford University and writes frequently for mises.org and Brownstone.org. He has spoken at economic and finance conferences on Austrian economics, and he is the editor of the podcast Software Engineering Radio.

Software engineer Alex Boten, author of Cloud Native Observability with Open Telemetry, joins SE Radio host Robert Blumen for a conversation about software telemetry and the OpenTelemetry project. After a brief review of the topic and the OpenTelemetry project's origins rooted in the need for interoperability between telemetry sources and back ends, they discuss the open telemetry server and its features, including transforms, filtering, sampling, and rate limiting. They consider a range of topics, starting with alternative topologies with and without the telemetry server, server pipelines, and scaling out the server, as well as a detailed look at extension points and extensions; authentication; adoption; and migration.

Alex Hidalgo, principal reliability advocate at Nobl9 and author of Implementing Service Level Objectives, joins SE Radio's Robert Blumen for a discussion of service-level objectives (SLOs) and error budgets. The conversation covers the meaning...

Keeping your bearings during the current upheaval can be a challenge. Find the time to take a look at Jim Quinn's latest analysis on our Fourth Turning is combining with mass formation psychosis. This won't be good news for everyone but for those of us who have worked to protect our freedom from the covid fear-mongers, it's encouraging. Robert Blumen says the game is over and they have lost. It's clear that many people are finally awakening to what is being done to us. James Howard Kunstler calls it the end of reality consensus disorder. The advent of AI is set to change our world in big ways. Walker Larson explains what writing is and why we misunderstand the importance of the coming of ChatGPT. When it comes to describing Congress and its efforts to raise the debt ceiling, the Babylon Bee said it best. Their headline stated: Congress debates how to raise the theft ceiling. Ron Paul breaks down the debt ceiling hysteria and hypocrisy. Sponsors: Monticello College Life Saving Food Bereli --- Support this podcast: https://anchor.fm/loving-liberty/support

Open source developers Jordan Harband and Donald Fischer join host Robert Blumen for a conversation about securing the software supply chain, especially open source. They start by reviewing supply chain security concepts, particularly as related to open..

Dan Lorenc, CEO of Chainguard, a software supply chain security company, joins SE Radio editor Robert Blumen to talk about software supply chain attacks. They start with a review of software supply chain basics; how outputs become inputs of someone...

Matt Butcher and Matt Farina, authors of the book Learning Helm join SE Radio host Robert Blumen to discuss Helm, the package manager for kubernetes. Beginning with a review of kubernetes and Helm, this episode explores the history of helm;...

This week, Postgres server developer Bruce Momjian joins host Robert Blumen for a discussion of multi-version concurrency control (MVCC) in the Postgres database. They begin with a discussion of the isolation requirement in database transactions (I in ACID); how isolation can be achieved with locking; limitations of locking; how locking limits concurrency and creates variability in query runtimes; multi-version concurrency control as a means to achieve isolation; how Postgres manages multiple versions of a row; snapshots; copy-on-write and snapshots; visibility; database transaction IDs; how tx ids, snapshots and versions interact; the need for locking when there are multiple writers; how MVCC was added to Postgres; and how to clean up unused space left over from aged-out versions.

Leonid Shevtsov talks with host Robert Blumen about email protocols and transactional email.

Networking researcher Iljitsch van Beijnum discusses internet routing and the border gateway protocol (BGP) with host Robert Blumen.

Jeffery D Smith, author of Operations Anti-Patterns, DevOps Solutions, talks about how things can go wrong in development organizations and what DevOps has to offer with host Robert Blumen.

In this episode of Codeish, Marcus Blankenship, a Senior Engineering Manager at Salesforce, is joined by Robert Blumen, a Lead DevOps Engineer at Salesforce. During their discussion, they take a deep dive into the theories that underpin human error and complex system failures and offer fresh perspectives on improving complex systems. Root cause analysis is the method of analyzing a failure after it occurs in an attempt to identify the cause. This method looks at the fundamental reasons that a failure occurs, particularly digging into issues such as processes, systems, designs, and chains of events. Complex system failures usually begin when a single component of the system fails, requiring nearby "nodes" (or other components in the system network) to take up the workload or obligation of the failed component. Complex system breakdowns are not limited to IT. They also exist in medicine, industrial accidents, shipping, and aeronautics. As Robert asserts: "In the case of IT, [systems breakdowns] mean people can't check their email, or can’t obtain services from a business. In other fields of medicine, maybe the patient dies, a ship capsizes, a plane crashes." The 5 WHYs The 5 WHYs root cause analysis is about truly getting to the bottom of a problem by asking “why” five levels deep. Using this method often uncovers an unexpected internal or process-related problem. Accident investigation can represent both simple and complex systems. Robert explains, "Simple systems are like five dominoes that have a knock-on effort. By comparison, complex systems have a large number of heterogeneous pieces. And the interaction between the pieces is also quite complex. If you have N pieces, you could have N squared connections between them and an IT system." He further explains, "You can lose a server, but if you're properly configured to have retries, your next level upstream should be able to find a different service. That's a pretty complex interaction that you've set up to avoid an outage." In the case of a complex system, generally, there is not a single root cause for the failure. Instead, it's a combination of emergent properties that manifest themselves as the result of various system components working together, not as a property of any individual component. An example of this is the worst airline disaster in history. Two 747 planes were flying to Gran Canaria airport. However, the airport was closed due to an exploded bomb, and the planes were rerouted to Tenerife. The runway in Tenerife was unaccustomed to handling 747s. Inadequate radars and fog compounded a combination of human errors such as misheard commands. Two planes tried to take off at the same time and collided with each other in the air. Robert talks about Dr. Cook, who wrote about the dual role of operators. "The dual role is the need to preserve the operation of the system and the health of the business. Everything an operator does is with those two objectives in mind." They must take calculated risks to preserve outputs, but this is rarely recognized or complemented. Another component of complex systems is that they are in a perpetual state of partially broken. You don't necessarily discover this until an outage occurs. Only through the post-mortem process do you realize there was a failure. Humans are imperfect beings and are naturally prone to making errors. And when we are given responsibilities, there is always the chance for error. What's a more useful way of thinking about the causes of failures in a complex system? Robert gives the example of a tree structure or AC graph showing one node at the edge, representing the outage or incident. If you step back one layer, you might not ask what is the cause, but rather what were contributing causes? In this manner, you might find multiple contributing factors that interconnect as more nodes grow. With this understanding, you can then look at the system and say, "Well, where are the things that we want to fix?" It’s important to remember that if you find 15 contributing factors, you are not obligated to fix all 15; only three or four of them may be important. Furthermore, it may not be cost-effective to fix everything. One approach is to take all of the identified contributing factors, rank them by some combination of their impact and costs, then decide which are the most important. What is some advice for people who want to stop thinking about their system in terms of simple systems and start thinking about them in terms of complex systems? Robert Blumen suggests understanding that you may have a cognitive bias toward focusing on the portions of the system that influenced decision-making. What was the context that that person was facing at the time? Did they have enough information to make a good decision? Are we putting people in impossible situations where they don't have the right information? Was there adequate monitoring? If this was a known problem, was there a runbook? What are ways to improve the human environment so that the operator can make better decisions if the same set of factors occurs again?

This episode features a conversation between Robert Blumen, DevOps engineer at Salesforce, and Matthew Myers, principal public key interface (PKI) engineer at Salesforce. Matthew shares his experience running a certification authority (CA) within the Salesforce enterprise. He shares the rationale for the decision to take CA in-house, explaining that becoming a certificate authority means you can become the master of your universe by establishing internal trust. A private or in-house CA can act in ways not dissimilar to a PKU but can issue its own certificates, trusted only by internal users and systems. Using a public certificate authority can be expensive at scale, particularly for enterprises with millions (or even billions) of certificates. However, an enterprise CA can be an important cost-saving measure. It adds a granular level of control in certificate issuing, such as naming conventions and the overall lifecycle. You can effectively have as many CAs as you can afford to maintain as well as the ability to separate them by use case and environment. Further, having the ability to control access to data and to verify the identities of people, systems, and devices in-house removes the cybersecurity challenges such as the recent SolarWinds supply chain attack. Matthew notes that Information within a PKI is potentially insecure “as the information gets disclosed to the internet and printed on the actual certificates which leave them vulnerable to experienced hackers.” Matthews shares the importance of onboarding and people management and the need to ensure staff doesn’t buy SSL certificates externally. Myerss offers some thoughts for businesses considering the DIY route discussing the advantages and limitations of open source resources such as OpenSSL and Let's Encrypt. Identity mapping and tracking are particularly important as you’re giving certificates to people, systems, and services that will eventually expire. Matthew shares the benefits of a central identity store, its core features, and how it works in tandem with PKI infrastructure. There’s also the need to know how many certificates you have in the wild at any given time. As a manager, the revocation infrastructure for PKI implementation means that you're inserting yourself in the middle of every single deal, because if you’re doing it correctly everything needs to validate that the certificates are genuine. When you have a real possibility of slowing down others’ connections, you want to ensure that your supporting infrastructure is positioned in such a way that you are providing those responses as quickly as possible. Network latency becomes a very real thing. Auditability and the ability to trust a certificate authority are paramount. The service that creates and maintains a PKI should provide records of its development and usage so that an auditor or third party can evaluate it. Links from this episode Salesforce Wikipedia page on Public Key Infrastructure Wikipedia page on Certificate Authorities OpenSSL Let’s Encrypt

Robert Blumen is a DevOps engineer with Salesforce, and he's joined in conversation with Andrzej Ludwikowski, a software architect at SoftwareMill, a Scala development shop. Andrzej is introducing listeners to the concept of event sourcing against the more traditional pattern of CRUD, which stands for create-read-update-delete. CRUD systems are everywhere, and are most typically associated with SQL databases. In comparison, event sourcing is a simply a sequential list of every single action which occurred on a system. Whereas in a database, a row may be updated, erasing the previous data in a column, and event source system would have the old data kept indefinitely, and simply record a new action indicating that the data was updated. In a certain sense, you can get the state of your system at any point in time. Each architectural pattern has its pros and cons. For one, an event source system can make it easier to track down bugs. If a customer notes an issue an production, rather than pouring through logs, developers can simply "rewind" the state of the application back to some earlier event and see if the faulty behavior is still there. On the flip side, since the event stream is immutable, fixes to previous data needs to be made at the end of the stream. You can modify old events or insert new ones into the flow. CQRS, or Command Query Responsibility Segregation, builds on top of event sourcing. The idea is to separate the part of the application responsible for handling commands and writes from the part responsible for handling queries and reads. This separation is not only on a software level (different repositories and different deployments), but also on the hardware level ( different hosts and different databases). The motivation for this is to be able to scale each part independently. Maybe your app has more writes than reads, and thus requires different computing power. It allows for a separation of concerns, and can make overall operations more efficient, albeit at a complexity cost. Andrzej is quick to note that event sourcing and CQRS divisions are not necessary for every application. Teams, as always, need to understand how the data flows in their application and which architectural pattern is most efficient for the problems they are trying to solve. Links from this episode SoftwareMill is a Scala development shop Martin Fowler gives a brief run-down on event sourcing On the SoftwareMill blog, Andrzej has a blog posts on entry-level event sourcing, keeping your domain clean in Event Sourcing, and the best serialization strategy for Event Sourcing CQRS.nu provides more educational resources Andrzej Ludwikowski's web site and talk Event Sourcing: What could go wrong?

Alexis Richardson discusses gitops - a deployment model based on convergent infrastructure as code with host Robert Blumen.

Luke Kysow is a software engineer at HashiCorp, and he's in conversation with host Robert Blumen. The subject of their discussion is on the idea of a service mesh. As software architecture moved towards microservices, several reusable pieces of code needed to be configured for each application. On a macro scale, load balancers need to be configuring to control where packets are flowing; on a micro level, things like authorization and rate limiting for data access need to be set up for each application. This is where a service mesh came into being. As each microservice began to call out to each other, shared logic was taken out and placed into a separate layer. Now, every inbound and outbound connection--whether between services or from external clients--goes through the same service mesh layer. Extracting common functionality out like this has several benefits. As containerization enables organizations to become more polyglot, service meshes provide the opportunity to write operational logic once, and reuse it everywhere, no matter the base application's language. Similarly, each application does not need to rely on its own bespoke dependency library for circuit breakers, rate limiting, authorization and so on. The service mesh provides a single place for the logic to be configured and everywhere. Service meshes can also be useful in metrics aggregation. If every packet of communication must traverse the service mesh layer, it becomes the de facto location to set up counters and gauges for actions that you're interested in, rather than having each application send out non-unique data. Luke notes that while it's important for engineers to understand the value of a service mesh, it's just as important to know when such a layer will work for your application. It depends on how big your organization is, and the challenges you're trying to solve, but it's not an absolutely essential piece for every stack. Even a hybrid approach, where some logic is shared and some is unique to each microservice, can be of some benefit, without necessarily extracting everything out. Links from this episode HashiCorp helps automate infrastructure configuration Consul, Linkerd, Istio, and Kuma are several open source components for service meshes and control planes Mastering Service Mesh: Enhance, secure, and observe cloud-native applications with Istio, Linkerd, and Consul by Anjaki Khatri and Vikram Khatri Consul service mesh What's a service mesh? And why do I need one? by William Morgan offers additional advice on when to use service meshes The Service Mesh: What Every Software Engineer Needs to Know about the World's Most Over-Hyped Technology What is a Service Mesh? - a blog from NGINX

Robert Blumen is a DevOps Engineer at Salesforce, joined by Ev Haus, Head of Technology at ZenHub. Together, they're going over a critique over several methodologies when writing code as part of a large team. First, there's DRY, which stands for Don't Repeat Yourself. It's the idea that one should avoid copy-pasting or duplicating lines of could, in favor of abstracting as much repeated functionality as possible. Then, there's DAMP, or Don't Abstract Methods Prematurely, which is somewhat in opposition to DRY. It advises teams to not create abstractions unless they are absolutely necessary. Last on the list is WET, or Write Everything Twice. This is the idea to embrace duplication whenever possible. Ev notes that, like many programming absolutes, the success of each strategy depends entirely on the context. DRY, for example, sounds like a really good idea, until it happens everywhere. Suddenly, a chunk of code becomes difficult to reason, as a developer jumps around various method definitions to piece together a flow. DAMP often makes sense as a counterpart to DRY, because if you abstract too early in your codebase, you may find yourself overloading methods or appending arguments to handle one-off cases. DRY is typically best suited for testing environments, where an absolutely reproducible set of explicit steps is often preferable in order to quickly understand what is occurring. No matter the strategy you use, the core tenant is to solve the problem first. Try to accomplish the goal you need to, whether that's adding a feature or squashing a bug. Don't over optimize until you've finished what you need to, and don't think too far into the future about all the possible edge cases. The rest of the balance comes with experience. Some duplication is bad, but not all of it. Figuring out the absolute perfect solution is unlikely, so you've got to put the code out into the real world to find out what works. After that, bake some flexibility into your processes to adjust hot code paths or refactor them when needed! Links from this episode ZenHub is an agile project management tool for GitHub Wikipedia's definition of DRY "Using DRY, WET & DAMP code" is Ev's article on different coding methodologies Codewars is a website with programming puzzles and challenges The Pragmatic Programmer by Dave Thomas is a popular book highlighting some of these concepts DRY code, DAMP DSLs by Jay Fields and DRY vs DAMP in Unit Tests by Vladimir Khorikov are more write-ups on the subject

Doug Fawley of the gRPC project discusses gRPC with host Robert Blumen. Their conversation covers the HTTP layer, protobuf, and use cases within microservices architectures.

Robert Blumen is a DevOps engineer at Salesforce interviewing Doug Fawley, a software engineer at Google. Doug is also the tech lead for the Golang implementation of gRPC. RPC, in general, is a system which enables any client and server to exchange messages. gRPC is Google's extension to the protocol, with support for more modern transports like HTTP/2. This allows for features like bidirectional streaming and stream multiplexing. It also enables better interoperability with load balancing, tracing, health checking, and authentication. To get started with gRPC, you would define your services and your messages using a language independent schema IDL protobuf. By explicitly stating what data you expect to receive, respond with, and error on, you can build a more reliable way of communication. In fact, many microservices have moved towards gRPC communication as opposed to something like REST, because of this level of introspection. gRPC is not technically a standard; it is, however, open source, and many languages have implementations against its spec. There's a very active community building tooling and resources, and for that reason, many of the largest software companies in the world have begun to implement it for their services. You can reach Doug on GitHub @dfawley. Links from this episode gRPC is a high-performance, open source universal RPC framework. protobuf is a language-neutral, platform-neutral, extensible mechanism for serializing structured data. gRPC web provides a JavaScript library that lets browser clients access a gRPC service. GRPCurl is a command-line tool that lets you interact with gRPC servers.

Robert Blumen is a DevOps engineer at Salesforce, and he's interviewing Sean Porter, the CTO of Sensu, a cloud monitoring platform. Monitoring your infrastructure often looks like keeping track of the four golden signals: latency, throughput, error rate, and saturation. To that, Sean advocates identifying data specific catered to security and privacy. For example, with regards to intrusion detection, a company could track the rate at which unauthorized attempts are being made, and where they're coming from. This could signal potential weak spots in the system or software which malicious actors are probing. Armed with this data and analysis, one could reinforce their security. More broadly, intrusion detection is really about monitoring changes to your system's state. You could take a snapshot of your entire file systems, from permissions of folders to the individual bytes of each binary; by recording the information of a known "good" state, you can track any changes that are occurring. You would be able to identify the rate at which your servers are undergoing configuration drift, or be notified if key system software, such as ssh or ps, have been tampered with. Monitoring your security is about taking a proactive approach to observing any state change on a machine, not necessarily whether unauthorized ports are being sniffed. With regards to privacy, you could build some auditing functionality to ensure that you're not exposing any user information you shouldn't be. One approach might be to monitor whether numbers that look like a credit card are being accidentally showing up in your logs. It's also important to be mindful of compliance with regulations like GDPR. GDPR stipulates that users must give explicit permission for the ways in which you store and make use of their information. Sean points out that there are tracing systems which can track a user's movement from their browser navigation through each microservice they transparently access. Your monitoring system would want to keep an eye on these flows and ensure that every system is behaving appropriately. Links from this episode Sensu is a platform that automates monitoring workflows Sensu Go open source projects Sean Porter articles on DevOps Sean Porter technical blog Sean Porter talk on monitoring architecture patterns Google SRE book (free online version) CPU vulnerabilities like Spectre are a new breed of attack on public cloud systems Terraform offers tools for managing configuration drift

Welcome to another episode of Develomentor. Today's guest is Jeff Meyerson. Jeffrey Meyerson is the creator and host of the podcast Software Engineering Daily (@software_daily). He is also the founder of FindCollabs, a platform to find collaborators for ventures.Jeff definitely took a non-traditional path to software engineering. Before getting his degree he played poker professionally for 3 years and then became a poker coach!Post-college, he worked at a number of software companies including Amazon and eBay as an engineer. Pretty quickly, Jeff realized that he prefers to work for himself. These days he is a podcaster, founder, and investor. Click Here –> For more information about tech careersIn this episode we’ll cover:Why did Jeff start his tech podcast, Software Engineering Daily? How does it make money?What should you do if you feel out of place in tech? Is it worth it getting a remote job so that you can have more flexibility?Where is the podcast space headed? Is it saturated or is there still room to grow?Additional ResourcesSoftware Engineering Radio - Podcast by Robert Blumen. https://www.indiehackers.com - A good place to learn how to start a small businesshttps://www.indiehackers.com/podcast/114-jeff-meyerson-of-software-engineering-daily - Interview with Jeff Meyerson about podcasting!Charles Max Wood – From Programmer to Full-Time Podcast Wiz - Episode 31 of DevelomentorYou can find more resources in the show notesTo learn more about our podcast go to https://develomentor.com/To listen to previous episodes go to https://develomentor.com/blog/Follow Jeff MeyersonTwitter: @the_prionFollow Software Engineering Daily @software_dailyLinkedIn: linkedin.com/in/jeff-meyerson-05275716/Follow Develomentor:Twitter: @develomentorFollow Grant IngersollTwitter: @gsingersLinkedIn: linkedin.com/in/grantingersoll

Yevgeniy Brikman, author of Terraform: Up & Running: Writing Infrastructure as Code and co-founder of Gruntwork talks with host Robert Blumen about how to apply best practices from software engineering to the development of infrastructure as code, primarily with Terraform. The discussion covers similarities and differences between conventional software engineering and code-driven infrastructure; factoring code […]

Yevgeniy Brikman, author of Terraform: Up & Running: Writing Infrastructure as Code and co-founder of Gruntwork talks with host Robert Blumen about how to apply best practices from software engineering to the development of infrastructure as code...

Giorgio Regni, the co-founder and CTO of Scality, and Robert Blumen, a DevOps engineer at Salesforce, cover the basics of on prem, public cloud, private cloud and multi-cloud. The discussion covers business drivers, use cases, division of workloads, architecture, and networking concerns present in each of these categories. For enterprises, there is no "one cloud fits all" approach to building applications. The public cloud is more than an experimental platform for non-critical applications and unproven products - nor is the path of all computing migrating to its final home in the public cloud inevitable. Instead enterprises are arriving at the right mix of on premises private clouds which are increasingly containers providing APIs, and one or more public clouds. The motivations for selecting a cloud type can be vertical best-of-breed based on the offerings of a specific cloud provider, distributing peak capacity at lower cost, off site disaster recovery, or choosing a mix of vendors to avoid lock in. This mixed model works conceptually, but it also introduces issues around security, privacy, and the ability of enterprises to meet service level agreements. Increasingly, companies are grappling with integrating authentication solutions for these disparate locations. As a cloud storage provider, Giorgio provides his insights on how companies are building out these infrastructures and the tools they use to solve their problems. Links from this episode Scality is a company which develops storage software https://www.docker.com/ https://kubernetes.io/ https://aws.amazon.com/ https://cloud.google.com/gcp/ https://azure.microsoft.com/ what is hybrid cloud eBook what is hybrid cloud according to MS Azure what is hybrid cloud according to Red Hat

Jay Kreps, CEO of Confluent, talks with Robert Blumen about how an enterprise integration architecture organized around a Kafka event log simplifies integration and enables rich forms of data sharing. #podcast #seradio #ieeecs #ComputerSociety

Jay Kreps, CEO of Confluent discusses an enterprise integration architecture organized around an event log. Robert Blumen spoke with Jay about the N-squared problem of data integration; how LinkedIn tried and failed to solve the integration problem;  the nature of events; the enterprise event schema; schema definition languages; the use of an event log in […]

Robert Blumen is a Dev Ops engineer at Salesforce. He's interviewing Alexey Syomichev, a software engineering principle architect at Salesforce, with over 25 years of experience. Their conversation begins with what constitutes an event (an immutable record encoding something that happened to an app). They then move on to describe consumers of those events, whether they're internal to an app or external to other services and business departments. Finally, they discuss ways in which you can store that event, either in a database or a running event log. Databases and event logs each have their strengths and weaknesses, which Alexey enumerates. Event logs, for example, are easier to write to; but databases are easier to query for information. In general, Alexey believes that it can be important to organize your larger systems around an event log. The conversation concludes with a discussion on how to use an event log in practical ways. First, you'll need to decide the schema to use when representing an event. State transitions are another reality to consider. If multiple events representing the same action come in, you need to make sure that the event log is atomic. Finally, there's a question of precisely how many events to retain, how far back you store your application's state. Links from this episode OK Event Log (the architecture files episode 3) by Ian Varley Apache Kafka CQRS Pattern by Martin Fowler Event-driven architecture How Apache Kafka Inspired Our Platform Events Architecture by Alexey Syomichev About event-driven driven_architecture Protobufs and Apache Avro are two ways in which you can serialize an event.

Joshua Davies discusses TLS, PKI vulnerabilities in the PKI, and the evolution of the PKI to make it more secure, with host Robert Blumen.

Joshua Davies, author of Implementing SSL / TLS Using Cryptography and PKI discussed SSL/TLS, public-key infrastructure, certificate authorities, and vulnerabilities in the security infrastructure.  Robert Blumen spoke with Davies about the history of SSL/TLS; TLS 1.3; symmetric and asymmetric cryptography; the TLS handshake; the Diffie-Helman key exchange; the HTTPS protocol; verification of domain ownership; man-in-the-middle […]

Dr. Andrii Gakhov, author of the book Probabilistic Data Structures and Algorithms for Big Data Applications talks about probabilistic data structures and their application to the big data domain with host Robert Blumen.

Bernd Rücker, who has contributed to multiple open source workflow management projects, discusses orchestrating microservices with workflow management.  As distributed systems evolve into a family of microservices that must handle long-running stateful processes with time-dependent actions, events, multiple paths through the system, and complex rollbacks, the workflow management model provides a way to ensure clear modeling, correctness, and separation of concerns.   Rücker recommends a federated model in which each microservice is paired with its own workflow to handle retries and other policies and failure modes around that service.  Robert Blumen spoke with Rücker about microservice architecture, event-driven systems, long-running stateful processes versus synchronous request/response, event handling, time-outs, and handling exceptional conditions with compensating transactions. Rücker compares the choreography versus orchestration models for collaboration and discusses why orchestration provides a better separation of concerns.  The discussion delves into the implementation of workflow management systems including persistence, scaling, event handling, timers and scheduling, and similarities to CQRS.  The discussion wraps up with monitoring and visualization.

Brent Laster, author of a book on Jenkins 2, speaks with host Robert Blumen about the Jenkins 2 build server, CI/CD, DevOps and “pipeline as code”.

Postgres developer Bruce Momjian joins Robert Blumen for a discussion of the SQL query optimizer in the Postgres RDBMS. They delve into the internals of query planning and look at how developers can make it work for their apps.

Bruce Momjian, a longtime Postgres developer, educator and consultant joins Robert Blumen for a discussion of the SQL query planner in the Postgres relational database. Topics covered include what is a query? How queries are evaluated by the server; the phases of query evaluation; SQL as a declarative language; why declarative query evaluation is simpler […]

In this episode Andy Davis talks Robert Bluman, an editor and host of the podcast Software Engineering Radio and also a lead DevOps Engineer. On the show he chats to Andy about moving from a software engineering role to a DevOps engineer. He also discusses his role at Software Engineering Radio. Robert Blumen is a DevOps engineer at Salesforce with more than 25 years’ experience in software development, programming, architecture, and media production. His interests include software architecture, scalability, high availability, persistence, big data, and devops. Robert is a graduate of Stanford University and the University of California Berkeley. Show Notes: 1.09 The history of Software Engineering Radio. 2.27 The sharing community that has been built around the technical community. 5.25 The importance of having a strong team dynamic as well as a team with great technical skills. 7.11 What were the reasons behind you moving to a DevOps position. 8.21 DevOps as a cultural shift not a technical discipline. 9.24 Will DevOps evolve again? 10.58 Do you still work on projects around work? 12.02 Progressing into the managerial role? 12.37 Company’s creating paths for employees who don’t want to progress into management. 14.22 How have your responsibilities with software engineering radio changed since you started. 17.04 What’s the typical feedback you like to receive for software engineering radio. 19.23 Audience interaction with your podcast. 21.34 Generating revenue from podcasts. 23.14 Podcasts and there competitive marketplace. 24.55 Committing to producing content. 26.58 How long did it take Software engineering radio to grow?

Robert Blumen talks to JBoss Drools project lead Edson Tirelli about Rules Engines. The show covers: the nature of business rules; rules and facts; rules and actions; the importance or rules to a business; the structure of a business rule; how many is “a lot” of rules?; communication about rules between the business and software […]

Robert Blumen talks to Edson Tirelli about business rules, rules engines, and the JBoss Drools engine.

James Turnbull joins Robert Blumen for a discussion of Terraform, an infrastructure-as-code tool, and a deep dive into how Terraform implements the declarative programming model.

James Turnbull rejoins the show with Robert Blumen for a conversation mostly about Terraform, as well as a bit about Puppet. Terraform is a declarative programming tool for automating infrastructure resource creation; it targets resource providers, such as Amazon AWS, Microsoft Azure, Digital Ocean, and other cloud and SAAS back ends. The discussion explores the […]

Guest: Robert Blumen @RobertBlumen Full show notes are at https://developeronfire.com/podcast/episode-227-robert-blumen-content-creation-mentor

James Cowling of Dropbox (architect of their distributed storage system), speaks to Robert Blumen about their move from Amazon’s S3 to their own infrastructure; The show covers: the size, scope and scale of Dropbox’s data management; their experience on Amazon’s S3; why S3 over time did not meet their needs; how the decision was made […]

James Cowling of Dropbox tells Robert Blumen about their massive migration from Amazon’s S3 to their own distributed storage system.

John Allspaw CTO of Etsy speaks with Robert Blumen about systemic failures and outages; how are systems defended against outages?; why do they fail anyway?; why are failures not entirely preventable?; why do outages involve multiple failures?; the time that Etsy identified it’s own office as a potential source of fraud; the human as part […]

John Allspaw CTO of Etsy speaks with Robert Blumen about systemic failures and outages. Why they cannot be totally prevented, how to respond, and what we can learn from them.

Donny Nadolny of PagerDuty joins Robert Blumen to tell the story of debugging an issue that PagerDuty encountered when they set up a Zookeeper cluster that spanned across two geographically separated datacenters in different regions.

Donny Nadolny of PagerDuty joins Robert Blumen to tell the story of debugging an issue that PagerDuty encountered when they set up a Zookeeper cluster that spanned across two geographically separated datacenters in different regions.  The debugging process took them through multiple levels of the stack starting with their application, the implementation of the Zookeeper […]

In this week’s podcast, Robert Blumen talks to Oliver Gould at QCon San Francsico 2016. Oliver is the CTO of Buoyant where he leads open source development efforts. Prior to Buoyant he was a Staff Infrastructure Engineer at Twitter where he was technical lead on Observability, Traffic, Configuration and Co-ordination teams. Why listen to this podcast: - Stratification allows applications to own their logic while libraries take care of the different mechanisms, such as service discovery and load balancing - Cascading failures can’t be tested or protected against, so having a fast time to recovery is important - Having developers own their services with on-call mechanisms improves the reliability of the service; it’s best to optimise automatic restarts so problems can be addressed during normal working hours - Post mortem analysis of failures are important to improve run books or checklists and to share learning between teams - Incremental roll out of features with feature flags or weighted routing provides agility while testing with production load, which highlights issues that aren’t seen during limited developer testing Notes and links can be found on: http://bit.ly/2ivoz9w 4m:05s - Each domain has different failure and operating modes, and the layered approach to resiliency means that the layer handles this automatically 4m:30s - Large systems may fail in unexpected ways 4m:35s - Twitter originally had the “Fail Whale” but this has been phased out as the system has become more stable 4m:50s - As Twitter grew, it needed to move quicker, with more engineers and less whale time 5m:10s - Automation and social tools were needed to improve the situation More on this - Quick scan our curated show notes on InfoQ: http://bit.ly/2ivoz9w You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Gil Tene joins Robert Blumen for a discussion of tail latency. What is latency? What is "tail latency"? Why are the upper percentiles of latency more relevant to humans? How is human interaction with an application influenced by tail latency? What are the economics of tail latency? What are the origins of tail latency within a system? What is the difference between response time and service time? How does queuing within a system contribute to response time? Java garbage collection and its contribution to latency outliers. How can we build systems with bounded tail latency out of components with variable latency? What type of observability to do we need to build systems with bounded latency? How is latency a driver of capacity planning?

Gil Tene joins Robert Blumen for a discussion of tail latency. What is latency? What is “tail latency”? Why are the upper percentiles of latency more relevant to humans? How is human interaction with an application influenced by tail latency? What are the economics of tail latency? What are the origins of tail latency within […]

Software Engineering Daily was started a year and a half ago, based on what I learned from my podcasting experience on Software Engineering Radio. Last week, I interviewed Robert Blumen, the editor of Software Engineering Radio, about how that podcast is produced. In today’s episode, Robert interviews me about this podcast. If you are thinking The post How Software Engineering Daily Works appeared first on Software Engineering Daily.

Björn Rabenstein discusses the field of Site Reliability Engineering (SRE) with host Robert Blumen. The term SRE has recently emerged to mean Google's approach to DevOps. The publication of Google's book on SRE has brought many of their practices into more public discussion. The interview covers: what is distinct about SRE versus devops; the SRE focus on development of operational software to minimize manual tasks; the emphasis on reliability; Dickerson's hierarchy of reliability; how reliability can be measured; is there such a thing as too much reliability?; can Google's approach to SRE be applied outside of Google?; Björn's experience in applying SRE to Soundcloud - what worked and what did not; how can engineers best apply SRE to their organizational situation?; the importance of monitoring; monitoring and alerting; being on call, responding to incidents; the importance of documentation for responding to problems; they wrap up with a discussion of why people from non-computer science backgrounds are often found in devops and SRE.

Björn Rabenstein discusses the field of Site Reliability Engineering (SRE) with host Robert Blumen. The term SRE has recently emerged to mean Google’s approach to DevOps. The publication of Google’s book on SRE has brought many of their practices into more public discussion. The interview covers: what is distinct about SRE versus devops; the SRE […]

Four years ago, I started volunteering for a popular podcast about software–Software Engineering Radio. For the next two years, I learned about the process of making a quality podcast about engineering. With its emphasis on preparation, timeless engineering principles, and attention to the listener, Software Engineering Radio continues to be one of the most popular The post Software Podcasting with Robert Blumen appeared first on Software Engineering Daily.

Robert Blumen talks with Cody Voellinger, the founder of a recruiting firm that specializes in filling software engineer roles for San Francisco-area startups, about how jobs are created and how companies and engineers get matched up. Their discussion covers the entire job search process, from job descriptions to salary negotiations. They look at the job market from both sides: how companies define what they want, find the right people, and evaluate candidates, and how job seekers can position themselves for the role they want. Other topics include culture fit versus skill and resumes in an age of social networking. They conclude with a look at the mistakes that job seekers, recruiters, and companies should avoid.

Robert Blumen talks with Cody Voellinger, the founder of a recruiting firm that specializes in filling software engineer roles for San Francisco-area startups, about how jobs are created and how companies and engineers get matched up. Their discussion covers the entire job search process, from job descriptions to salary negotiations. They look at the job […]

Monica Beckwith joins Robert Blumen for a discussion of java garbage collection. What is garbage collection? GC algorithms; history of GC in the java language; fragmentation and compaction; generational strategies; causes of pauses; impact of pauses on application performance; tuning GC; GC on multi-core and large memory machines; should production servers be implemented in non-GC […]

Robert Blumen talks to Christopher Meiklejohn about conflict-free replicated data types (CRDTs). The discussion covers forms of consistency in distributed systems; conflicts and conflict resolution algorithms; consistency and concurrency; the discovery of CRDTs; state-based and operations-based CRDTs; examples of some well-known CRDTs, including counters and sets; time and space complexity; uses of CRDTs in chat […]

Robert Blumen talks to Christopher Meiklejohn about conflict-free replicated data types. The discussion covers consistency in distributed systems, CRDTs, and their use in NoSQL databases.

Alex Budzier of the Oxford Saïd Business School and Jürgen Laartz of McKinsey Berlin join Robert Blumen to discuss their research on large IT project failures. The show covers: What is a “large” project? What is the definition of failure? Cognitive biases and project failures. Are some attributes of projects predictive of failure? The catastrophic […]

Alex Budzier of the Oxford Saïd Business School and Jürgen Laartz of McKinsey Berlin join Robert Blumen to talk about the their research on large IT project failures. Why do large projects fail and to what extent are these failures avoidable?

Show editor Robert Blumen begins with a history of the show, what he has been doing since he became the show editor a year ago, and where he wants the show to go in the future. The remainder of the show is a series of interviews with all of the active hosts, the founder of the […]

Fangjin Yang, creator of the Druid real-time analytical database, talks with Robert Blumen. They discuss the OLAP (online analytical processing) domain, OLAP concepts (hypercube, dimension, metric, and pivot), types of OLAP queries (roll-up, drill-down, and slicing and dicing), use cases for OLAP by organizations, the OLAP store’s position in the enterprise workflow, what “real time” […]

Robert Blumen talks with Eric Brewer, who discovered the CAP (consistency, availability, partition tolerance) theorem. The first part of the show focuses on Brewer’s original thesis presented at the 2000 ACM Symposium on Principles of Distributed Computing (PODC): What set of problems motivated the formulation of CAP? How was it understood at the time? What are […]

Senior performance architect and author of *Systems Performance* Brendan Gregg talks with Robert Blumen about systems performance: how the hardware and OS layers affect application behavior. The discussion covers the scope of systems performance, systems performance in the software life cycle, the role of performance analysis in architecture, methodologies for solving performance problems, dynamic tracing […]

Robert Blumen talks to Jon Gifford of Loggly about logging and logging infrastructure. Topics include logging defined, purposes of logging, uses of logging in understanding the run-time behavior of programs, who produces logs, who consumes logs and for what reasons, software as the consumer of logs, log formats (structured versus free form), log meta-data, logging […]

Guest Udi Dahan talks with host Robert Blumen about the CQRS (command query responsibility segregation) architectural pattern. The discussion begins with a review of the command pattern. Then a high-level overview of CQRS, which consists of a separation of a command processing subsystem that updates a write model from one or more distinct and separate, […]

Tom talks to Robert Blumen about his article "Say's Law and the Permanent Recession." Check out Robert's article archive at Mises.org.

Alan discusses a couple of articles. Todd looks to short the S&P if we can get to 1350. Robert Blumen argues that we have been in a recession since 2001. Ileana Johnson weighs in on the 25 years since she fled communism, attacks on our property rights, and the latest musings from the global warming crowd. The show ends with David Eicher, editor of Astronomy magazine.

Claus Vogt is a contrarian investor. We may sleep better at night when our views agree with the majority. But when the majority opinion is wrong it can be disastrous for you. Claus Vogt has identified a host of reasons why the stock market will decline big time this year. He has also provided three danger signs. But Claus has some ways in which you can protect your wealth and actually gain from the impending decline. We will also delve into his new book, The Global Debt Trap. How will this crisis eventually end? Will it be through the flames of hyper inflation as prior guests on this show like Marc Faber, Ron Paul and John Williams think? Or will it be through a deflationary cleansing like Robert Prechter, Ian Gordon and Mish Shedlock assume. Also joining us this week will be Robert Blumen who will explain why paying attention to new gold mine supply is a waste of time in predicting the gold price. We will also talk to the CEO of an exciting uranium exploration company.

Claus Vogt is a contrarian investor. We may sleep better at night when our views agree with the majority. But when the majority opinion is wrong it can be disastrous for you. Claus Vogt has identified a host of reasons why the stock market will decline big time this year. He has also provided three danger signs. But Claus has some ways in which you can protect your wealth and actually gain from the impending decline. We will also delve into his new book, The Global Debt Trap. How will this crisis eventually end? Will it be through the flames of hyper inflation as prior guests on this show like Marc Faber, Ron Paul and John Williams think? Or will it be through a deflationary cleansing like Robert Prechter, Ian Gordon and Mish Shedlock assume. Also joining us this week will be Robert Blumen who will explain why paying attention to new gold mine supply is a waste of time in predicting the gold price. We will also talk to the CEO of an exciting uranium exploration company.

Claus Vogt is a contrarian investor. We may sleep better at night when our views agree with the majority. But when the majority opinion is wrong it can be disastrous for you. Claus Vogt has identified a host of reasons why the stock market will decline big time this year. He has also provided three danger signs. But Claus has some ways in which you can protect your wealth and actually gain from the impending decline. We will also delve into his new book, The Global Debt Trap. How will this crisis eventually end? Will it be through the flames of hyper inflation as prior guests on this show like Marc Faber, Ron Paul and John Williams think? Or will it be through a deflationary cleansing like Robert Prechter, Ian Gordon and Mish Shedlock assume. Also joining us this week will be Robert Blumen who will explain why paying attention to new gold mine supply is a waste of time in predicting the gold price. We will also talk to the CEO of an exciting uranium exploration company.

Philip Zeyliger of Cloudera discusses the Hadoop project with Robert Blumen. The conversation covers the emergence of large data problems, the Hadoop file system, map-reduce, and a look under the hood at how it all works. The listener will also learn where and how Hadoop is being used to process large data sets.

Philip Zeyliger of Cloudera discusses the Hadoop project with Robert Blumen. The conversation covers the emergence of large data problems, the Hadoop file system, map-reduce, and a look under the hood at how it all works. The listener will also learn where and how Hadoop is being used to process large data sets.

Philip Zeyliger of Cloudera discusses the Hadoop project with Robert Blumen. The conversation covers the emergence of large data problems, the Hadoop file system, map-reduce, and a look under the hood at how it all works. The listener will also learn where and how Hadoop is being used to process large data sets.