
Sign up to save your podcasts
Or


Today on the show we are joined by none other than our host, Michael Nuñez’s brother, Steven Nuñez! Steven will be helping us in our discussion about a very special topic and one that is very common amongst developers, imposter’s syndrome! Sound familiar? Feel familiar? Well, chances are at some point in your professional career (and beyond) you have probably felt like an imposter.
Today, we’ll be talking about whether comments are considered harmful or helpful. We’re pretty sure that there are many different comments you may have run into in your careers. Comments are something that is really common to every programmer, everyone can relate to them – whether they’ve been tormented or blessed by them. We’ve come across some pretty funny comments in the past like, “Holy crap, WTF is this?” or “Drunk, will fix later,” or “Magic, do not touch,” or just the standard, “I’m sorry.” Aside from their entertainment value, comments can be useful for a multiple of other reasons – such as documentation and setting to do reminders for a team. But how can we utilize comments most effectively to avoid the shame game? In this episode, we discuss how best to use comments for to-tasks, writing tests, the value of user stories, the dangers of tech debt and the almighty perils of the copypasta driven development boys. In addition, we will also discover how scout’s honor applies to code (as well as to developers from the Bronx), why a comment is the only code that can lie to you and how you can quite simply avoid comments altogether.
Today on the podcast we welcome the awesome and the infamous, Saron Yitbarek. If you haven’t heard of her before, Saron is a developer, speaker, the Founder of Code Newbie and is heading up the 2018 Code Land Conference kicking off in May this year in NYC.
In today’s episode, we’re speaking about the terror of public speaking. Public speaking is scary for a lot of people, ourselves included. Almost everyone has had a universally bad experience with public speaking – maybe yours happened in college where you froze up in front of the entire lecture hall.
On today's show’s we talk about a few great tools that you can use with Python. We are joined by Darlin Alberto from mighty.com to help us unpack some of these tools and break down what’s good and what’s not. We look through a list of current tools and compare and critique their utility for your listening pleasure. We also chat about the latest update to version 3.0 from 2.7 and how this might affect compatibility and unity among developers. We are sadly missing William Jeffries today but we hope we can make up for this with our great guest and discussion. Without further ado let’s get down to business! Listen in to hear all about it!
The focus of today’s episode is GraphQL. The team break down the language and how it might just be the way to go for the foreseeable future. Dave shares much of his experience and opinions on using GraphQL and we look at how it can fit into the rest of your operations. During the show we also look at instances in which GraphQL may not be the best query language and why this may be. In addition to the usual teach and learn section, we give you the best overview of GraphQL, covering all angles and imagining its utility in different settings. So, let’s get into it!
Today we’ll be talking about how to have effective one on one meetings and why you should bother having them. There’s nothing worse than a manager cornering you at the coffee station and saying, “We need to talk”. One on one meetings are scary enough, but the truth is they don’t have to be if they are initiated and conducted right. One on one’s are a vital way to get to know your team, check in with their individual needs and aspirations and give constructive feedback without the pressure of a group. But how do you go about them
On today’s show we talk about refactoring. As most of us know, refactoring can be a very important part of tidying code and making it more useable in the future. But for a few reasons it is not always the highest priority on a project, which can lead to the process being neglected.
On today’s episode we talk to Tom Benham about machine learning. Tom has worked in finance and risk services and has studied data science machine learning. Although the term seems to be used widely and frequently it can also be an area in which information is not always readily available. Tom gives us some insight into how algorithms are becoming useful in his field of work as well as some other professional examples. We chat about the positive sides of this, such as the reduced chance of human error, as well as looking at the shortcomings of present configurations such as data biases. If you want an introduction to a vital concept and area of the contemporary world as well as a gateway to more info on the subject, we got you! Listen in to hear all about it!
On today’s show we discuss context switching. We all know how much time can be spent on changing between projects and how distracting arising issues can be. The data around just how much time is wasted is quite startling, but how do we manage the multi-project nature of most of our work? We break down a few different strategies for minimizing wasted time and the ensuing frustration. Whether the distractions are internal, external, necessary or not, we could all do with a bit more control of what we afford our attention at what time and for how long. Listen in to hear all about it!
From the publisher's feed