Oppenheimer, Michael, author

The company on Wednesday beat Wall Street sales and profit expectations

The tech giant also noted that there has been a sharp spike in fraudulent ads for in-demand products like face masks amid the COVID-19 pandemic that has claimed lakhs of lives globally

Tropicana Joint Venture

Police Commissioner Ch. Dwaraka Tirumala Rao on Friday suspended two Armed Reserve (AR) police constables, P. Kiran Kumar and V. Naresh, for allegedly

The panelists have an open discussion.

The panelists talk to Brad Green of Google, about Angular.js and managing open source projects.

The panelists discuss dependency injection with Vojta Jína & Misko Hevery.

Panel:

Charles Max Wood

Aimee Knight

Corey House

Joe Eames

Special Guests: 

In this episode, JavaScript Jabber speaks with Dirk Hohndel about Open Source Software. Dirk is the Chief Open Source Officer at VMWare and has been working with open source for over 20 years. Dirk duties as the Chief Open Source Officer is to engage with the open source community and help promote the development between the community, companies, and customers.

Dirk provides historical facts about open sources to current processes. The discussion covers vision and technological advances with languages, security, and worries of using open source software, view/consumption and burnout on maintaining a project. This is a great episode to learn about more different avenues of Open Source.

In particular, we dive pretty deep on:

• What does the Chief Open Source Officer do?
• What is really different and has stayed the same in open source?
• Technological advances
• Good engineering and looking ahead or forward
• 100 million lines of code running a car…
• This is in everything..
• Production environments
• Security
• Bugs in the software and the security issues
• Scaling and paying attention
• Where should we be worried about open source
• Notation and data sets
• Write maintainable software
• How does VMWare think about open source?
• View and Consumption of open source
• The burnout of open source projects - how to resolve this abandonment
• To much work to maintain open source  - not a money issue
• Scaling the team workload not the money
• Contribution and giving back
• Companies who do and don’t welcome open source
• What to do to make a project open source?
• Adopting an API
• And much more!

Links:

• @_drikhh
• VMWare
• Drikhh - everywhere!
• https://github.com/dirkhh

Picks:

Aimee

• De Contact 
• Dodow 

Dirk

• Track This Critical Thinking

Charles

• Nicholas Zakas - Books 

Corey

• Fun Fun Function Show

Joe

• Dice Forge
• Concept of empathy

Panel:

• Charles Max Wood
• Aimee Knight
• AJ ONeal
• Joe Eames

Special Guests: Henry Zhu

In this episode, the JavaScript Jabber panel talks to Henry Zhu about Babel and open source software. Henry is one of the maintainers on Babel, which is a JavaScript compiler, and recently left this job to work on doing open source full time as well as working on Babel. They talk about where Babel is today, what it actually is, and his focus on his open source career. They also touch on how he got started in open source, his first PR, and more!

In particular, we dive pretty deep on:

• Henry intro
• Babel update
• Sebastian McKenzie was the original creator of Babel
• Has learned a lot about being a maintainer
• What is Babel?
• JavaScript compiler
• You never know who your user is
• Has much changed with Babel since Sebastian left?
• Working on open source
• How did you get started in pen source?
• The ability to learn a lot from open source
• Atrocities of globalization
• More decentralization from GitHub
• Gitea and GitLab
• Gitea installer
• Open source is more closed now
• His first PR
• JSCS
• Auto-fixing
• Prettier
• Learning more about linting
• You don’t have to have formal training to be successful
• Codefund.io
• Sustainability of open source
• And much, much more!

Links:

• Babel
• JavaScript
• Gitea
• GitLab
• Gitea installer
• Prettier
• Codefund.io
• @left_pad
• Henry’s GitHub
• henryzoo.com
• Henry’s Patreon

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• Orphan Black
• Crucial Accountability by Kerry Patterson

Aimee

• Desk with cubby holes for cats
• The Key to Good Luck Is an Open Mind blog post

AJ

• Gitea
• Gitea installer
• Greenlock

Joe

• Solo
• Justified

Henry

• Celeste
• Zeit Day talks

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. 

Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API.

Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. 

Panelists

• Dan Shapir

• Charles Max Wood

Guest

• Josh Ponelat

**To receive your the 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us at Facebook - click on "Send A Message"and type "YES"**

Sponsors

• Sentry | Use the code “devchat” for $100 credit

Links

• Swagger

• Open API

• Difference Between Swagger and Open API

• GraphQL

• Designing APIs with Swagger and Open API

Picks

Dan Shapir

• Saga of Pliocene Exile

Charles Max Wood

• DevChat.tv Merchandise 

• BusyCal

Josh Ponelat

• AsciiDoc

• FASD tool

Today the panel is discussing iterating on open source projects. Aimee and AJ recall a conversation they had in the past on this subject and AJ talks about some of his experience iterating with open source. AJ believes that we have an obligation to capture the value of what you create so that we can reinvest and create more value, though he admits that making money in open source is a unique challenge because donations only really work if you have a project that gets billions of downloads a month. As your project grows, it has to change in order to survive, and eventually you will need to get financial support from your project. The panel agrees that some of the main issues with iterating in open source are maintaining the code and getting feedback from users, financial backing, and roadmapping and integrations.

The panel discusses their methods for getting feedback from their users. This feedback is valuable because it can show you things that you missed. They acknowledge that there can be conflicts of interest between those who only use the project and those who financially support it, and you have to make a choice. Unfortunately, someone is probably going to be inconvenienced no matter what choice you make. When making these decisions, you have to consider who it helps, who it frustrates, and who it may cause problems for. The panelists talk about different ways they’ve handled making these decisions in the past. The JavaScript experts talk about the importance of having data on your user base in order to make good choices for your users. They talk about different methods for notifying your users of upcoming changes and how it will affect compatibility, and some of the challenges with communicating with your users. AJ talks about an iteration he thought was a good idea but that a lot of people hated and how he noticed that the new users liked it but the old users did not. They panel agrees that people in general don’t like change. AJ talks about what he learned from this experience. 

Another common issue is integrating with other services. Integrating with cloud services, or at least giving people the option to integrate gives you an opportunity to reach more people and maintain the project long term. AJ gives some final thoughts to close the show, namely that most projects never go anywhere, and that’s ok. If you’ve got something that starts going somewhere, think early on about how you can better serve the community and remember that these people are mostly grateful and semi-willing to support you. He believes that if you are helping people create value, you deserve to see the fruits of your labor. He advises listeners to stay true to your open source ideals, think about your users perspective, and that the earlier you can think about this and make these choices, the better it is for your project

Panelists

• Aimee Knight

• Steve Edwards

• AJ O’Neal

• Charles Max Wood

**To receive your 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us on Facebook - click on "Send A Message"and type "YES"**

Sponsors

• Sentry | Use the code “devchat” for $100 credit

Links

• How-npm-am-i

• React

• Vue.js

• Let’s Encrypt

• Async/await

• Node

Picks

Aimee Knight:

• Debug Like a Ninja

Steve Edwards:

• Jack Ryan 

AJ O’Neal:

• Why I, as a black man, attend KKK meetings

Charles Max Wood:

• It’s a Wonderful Life

• Mr. Kreuger’s Christmas

Adam dives into how to document your application using OpenAPI (formerly Swagger) and then how to generate great documentation for your API's using Redoc. He gives us the history of Redoc, breaks down the process for building API documentation, and understanding the OpenAPI specification.

Panelists

• Aimee Knight

• Dan Shappir

• AJ ONeal

• Steve Edwards

Guest

• Adam Altman

Sponsors

• G2i

____________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Links

• https://twitter.com/redocly

• Https://Redoc.ly

• https://www.facebook.com/redocly

Picks

Steve Edwards:

• https://wesbos.com/announcing-my-css-grid-course/

• https://flexbox.io/

Aimee Knight:

• https://github.com/ErikCH/DevYouTubeList

Dan Shappir:

• Old Kingdom Book Series

AJ O’Neal:

• Final Fantasy VII and VIII (Physical Copy, English) on Play Asia

Adam Altman:

• concepts.app

Deutscher, Penelope, 1966-

Childs, G. W. (Musician)

Springhall, John

Anglin, Douglas George

Spencer, Scott, 1975-

Badger, Michael

Badger, Michael

This is not the way to treat govt. doctors, observes bench

Online Resource

Online Resource

Online Resource

Copenhaver, Adam, author

Downs, David J., 1977- author

Archer, Kenneth J., author

Riches, Tanya, author

Kloppenborg, John S., 1951- author

Munson, Chuck, author

Interview with Mehraneh D. Jafari, MD, and Kasra Ziai, MD, authors of Association of Compensation From the Surgical and Medical Device Industry to Physicians and Self-declared Conflict of Interest

Interview with Daniel L. Chao, MD, PhD, author of Success in Attaining Independent Funding Among National Institutes of Health K Grant Awardees in Ophthalmology: An Extended Follow-up