Online Resource

Hayden Library - HC79.I55 S6813 2018

Venugopal Pillai

Santhanagopalan, Shriram, author

Online Resource

Online Resource

Online Resource

Hayden Library - BD396.O54 2018

Online Resource

It’s time to test everyone’s favorite action-camera. The GoPro performs under extreme sports conditions, but how does it hold up against a 9-iron and a powerful swing? Find out, as we take the camera out of its durable case and tee it up for a test of total destruction.

Action cams can handle a lot—or so they say. See which camera comes out on top when we put the GoPro Hero4 Silver, Sony HDRAS20/B, and Contour Roam3 up against one another.

If you hate GoPro's rectangular shape, your prayers have been answered! Sort of. We took the new Hero4 Session into rivers, lakes, and surf, off cliffs and platforms, through trees and go kart courses. Our full review will tell you everything you need to know.

Former Stig, Ben Collins, goes head to head against Wired’s Transportation Editor Alex Davies in a go kart duel.

GoPro's Hero4 Black costs $500, and the Yi 4K costs $250, which one is better? Not the expensive one.

Must be action cam season again and now Garmin has stepped into the game with it's Virb Ultra 30. It doesn't do a bad job when matched against the GoPro Hero4.

GoPro's new 4K cameras, the Hero5 Black and Hero5 Session, aim to deliver the best GoPro experience yet. Brent Rose takes them through their paces, and compares the Hero5 to Garmin's impressive Virb Ultra 30.

*UPDATE* We have looked into the focus issues and have altered our choice accordingly. Please read the updated review at WIRED.com for the full explanation: https://www.wired.com/2016/11/gopro-karma-vs-dji-mavic-pro/ GoPro has entered the drone game, delivering a sleek, foldable device that can fit inside a backpack. Brent Rose compares GoPro's offering with the Mavic Pro; DJI's impressive new foldable drone.

Tech Writer Brent Rose reviews the new GoPro Hero7 Black for WIRED, testing it against the Hero6 Black and the SONY X3000, and reviewing its "hypersmooth" image stabilization, audio capture, timelapse, SuperPhoto stills and more. Read more at WIRED.com: https://www.wired.com/review/gopro-hero7-black-2018

Online Resource

Barker Library - QA276.M73 2019

Online Resource

Online Resource

Online Resource

Hayden Library - P240.85.E46 2018

Online Resource

Hayden Library - QC798.D3 C66 2017

Online Resource

Online Resource

Online Resource

Online Resource

Move violates the federal principles and structure of the Constitution, Rajagopal said.

Panel:

• Charles Max Wood

Special Guests: Ori Zohar and Gopinath Chigakkagari

In this episode, the JavaScript Jabber panelists discuss Cloud-Hosted DevOps with Ori Zohar and Gopinath Chigakkagari at Microsoft Build. Ori is on the product team at VSTS focusing on DevOps specifically on Azure. Gopinath is the group program manager in VSTS primarily working on continuous integration, continuous delivery, DevOps, Azure deployment, etc. They talk about the first steps people should take when getting into DevOps, define DevOps the way Microsoft views it, the advantages to automation, and more!

In particular, we dive pretty deep on:

• Ori and Gopi intro
• VSTS – Visual Studio Team Services
• VSTS gives developers the ability to be productive
• Developer productivity
• What’s the first big step people should be taking if they’re getting into DevOps?
• The definition of DevOps
• The people and the processes as the most important piece
• DevOps as the best practices
• Automating processes
• What people do when things go wrong is what really counts
• Letting the system take care of the problems
• Have the developers work on what they are actually getting paid for
• Trend of embracing DevOps
• Shifting the production responsibility more onto the developer’s
• Incentivizing developers
• People don’t account for integration
• Continuous integration
• Trends on what customers are asking for
• Safety
• Docker containers
• And much, much more!

Links:

• Azure
• Microsoft Build
• VSTS
• @orizhr
• Ori’s GitHub
• Gopi’s GitHub
• @gopinach

Sponsors

• Kendo UI
• Linode
• FreshBooks

Picks:

Charles

• .NET Rocks!
• Shure SM58 Microphone
• Zoom H6

Ori

• Fitbit
• Pacific Northwest Hiking

Gopinath

• Seattle, WA

Tanmai is one of the founders at Hasura. Hasura gives you instant graphQL APIs on top of a Postgres database. The eventual idea is to make data access secure and easy. Tanmai explains the challenges of doing this in the cloud. He talks about some of the difficulties with the tooling around using GraphQL and its bias towards working well with a monolith. Since GraphQL is basically a shared type system that describes your API, that means all your types need to be in the same code base. This is at odds with the folks who want to do microservices and serverless functions, because since their API is split across multiple services they have different types, and forcing these types to work together defeats the purpose of using microservices. Also, storing state across requests doesn’t work well with serverless and cloud native stuff. In short, learning to live without state is one of the general challenges with going serverless. 

This is where Hasura comes into play, and Tanmai explains how it works. Hasura is metadata driven, and each instance of the server can leverage multiple calls and exhibit a high amount of concurrency. It’s designed to be a little more CPU bound than memory bound, which means that configuring auto scaling on it is very easy and allows you to utilize the elasticity of cloud native applications. Tanmai clarifies his usage of the word ‘cloud native’, by which he means microservices. He explains that when you have a metadata based engine, this metadata has a language that allows you to bring to bring in types from multiple upstream microservices, and create a coherent graphQL API on top of that. Hasura is a middle man between the microservices and the consumer that converts multiple types into a single coherent graphQL API.

Next, Tanmai explains how Hasura handles data fetching and a high volume of requests. They also invented PostgresQL, RLS-like semantics within Hasura. He explains the process for merging your microservices into a single graphQL interface. Back on data fetching, Tanmai explains that when the product is an app, preventing an overabundance of queries becomes easier because during one of the staging processes that they have, they extract all of the queries that the app is actually making, and in the production version it only allows the queries that it has seen before. Hasura is focused on both the public interface and private use cases, though private is slightly better supported. 

Tanmai talks about the customizations available with Hasura. Hasura supports two layers. One is an aliasing layer that lets you rename tables, columns, etc as exposed by PostgresQL. The other is a computer column, so that you can add computer columns so you can extend the type that you get from a data model, and then you can point that to something that you derive. 

The panelist discusses the common conception of why it is a bad idea to expose the data models to the frontend folks directly. They discuss the trend of ‘dumbing down’ available tooling to appeal to junior developers, at the cost of making the backend more complicated. They talk about some of the issues that come from this, and the importance of tooling to solve this concern. 

Finally, Tanmai talks about the reasons to use Hasura over other products. There are 2 technologies that help with integrating arbitrary data sources. First is authorization grammar, their version of RLS that can extend to any system of types and relationships, The second is the data wrapper, part of the compiler that compiles from the graphQL metadata AST to the actual SQL AST. That is a generic interface, so anyone can come in and plug in a Haskell module that has that interface and implement a backend compiler for a native query language. This allows us to plug in other sources and stitch microservices together. The show concludes with Tanmai talking about their choice to use Haskell to make Hasura. 

Panelists

• AJ O’Neal

• Dan Shapir

• Steve Edwards

• Charles Max Wood

With special guest: Tanmai Gopal

Sponsors

• Adventures in DevOps

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• The Dev Ed Podcast

Links

• Hasura

• Haskell

• Node.js

• Cloud Native

• Microservices 

• PostGraphile 

• Postgres 

• PostgresQL RLS

• Swagger

• JAMstack

• Soap

• Rest

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

• The Economic Singularity

• Capital Cities

• GameCube Homebrew

Dan Shapir:

• Romania

• JSCamp

Steve Edwards:

• Cold Blooded: The Clutter Family Murders

Charles Max Wood:

• Maxcoders.io

• TripIt

• St. George Marathon

• VO2 Max app

Tanmai Gopal: 

• Follow Tanmai on Twitter @tanmaigo

• Broken Earth Trilogy

• The Three-Body Problem

• graphQL Asia

Online Resource

Rotch Library - GN635.I4 C43 2015

Rotch Library - G73.G57 2020