Developer Tea

In today's episode of Developer Tea, we're talking about the concept of time. We'll linger on the idea that moments have a timeline: future, present, and past. How do our moment timelines help us become better developers and coworkers?  

Just like many of the other distortions that our brains trick us into believing, the idea that we have two selves, good and bad, hides away our complex ego. In today's episode, we're talking about ego and how to get outside of our self-perception when we make a mistake in order to grow and learn. 

In today's episode, we're talking about an environment of learning that you can create on your own. How can we create an environment that puts us in a state of discomfort in order to keep us growing? 

If you think about most achievements awarded, they are handed out over a period of time when the dues are paid and effort put in. In today's episode, we're talking about pictures of achievement and taking a moment to reflect on what it means to live a full and satisfying life as a developer.  

Aside from the fact that we're making a living being engineers, what is it that keeps us coming back into work every day? At some point in your career, the initial things that brought you into engineering will shift, and when those things change, what is left? What keeps you going? Today, we talk about what motivations drive us and how to keep our motivations relevant when the career changes.

What do you do when you hit a mental block and don't know how to solve a problem? Today we'll dig into what we can do about this blocked scenario and how can we better deal with negative emotions that follow.  

In today's episode, we're  talking to early engineers and challenging all new engineers to think about how they will handle the pressure of not knowing the answer to a question asked by a co-worker.  

In this short episode, we're digging into the relationship between our belief and knowledge and how we form our beliefs based on knowledge.  

In today's episode, we dive into Saul's question by recounting past experience and providing tools to approach this situation at a human level and from your employers expectation.  

In today's episode we're talking about problems and how we involve questions into our day-to-day tasks as developers. We'll cover question framing techniques and practices to boost collaboration with your co-workers on problem solving.

 As someone who was a self-taught developer, I have an affinity for people eager to become a developer. In today's episode, we'll offer four different pain points that you're likely to experience in your career and give tips on how to use those moments to continue your growth and develop your skills.  

Changing our minds on a belief or issue that we stand by is not easy and as humans but is required of us to grow as people and as professionals.In this episode of Developer Tea, we're walking through three different visualizations to help us better understand and become more comfortable with when and why we decide to change our minds.

In today's episode, we're talking about goals and what we tend to give up in order to reach those goals. We'll cover how to define goals, and how to keep going toward your goals when motivations run thin.

In today's episode, we're talking about balance as it relates to decision making. We'll dig into two models of thinking that can help us understand the nuance of balance as it relates to daily decisions.

A useful default is an action you can take on a regular basis that you expect to provide some level of utility. In today's episode, we're talking about the fine line between useful default behaviors and when those behaviors can lead you astray and become more of a distraction from an overall goal.

How can you write a pull request that's productive? in today's episode, we're talking about how to be a better PR author by offering three guidelines to writing productive pull requests so that PR reviews go quickly and smoothly.

What does it mean to collaborate as an engineer with other engineers? In today's episode, we're talking about the pull request process and the lack of attention it seems to get from engineers. In this episode, we'll cover what a PR process is, the players in a PR review and offer four ways to be a better PR reviewer.

How do our brains and our minds perceive code? In today's episode, we're talking about what code is to our mind vs. our brain?

When you think correlation and causation you might think of graphs and research. As one data point changes another data point also changes. In today's episode, we're talking about controlling variables and how to avoid assuming that correlation is causation.