This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The two positions are not interchangeable—and misperceptions of their roles can hurt teams and compromise productivity. It’s important to understand the differences between a data engineer and a data scientist. Misunderstanding or not knowing these differences are making teams fail or underperform with big data.
Kent Beck concluded , Measure developer productivity? My favorite discussion of the topic is Robert Austins, who wrote Measuring and Managing Performance in Organizations. He says a measurement based approach generates relatively weak improvements and significant distortion of incentives. Not possible. What does that look like?
But how do you prepare others on your team for this next career step? Because if you don’t do the upfront work to prepare your team to take the helm, you won’t have anyone to fill those seats when you want to move up — or step down. I spoke to IT executives and leadership coaches for tips on how to develop the leaders on your team.
Two and a half millennia later, we were now using the ancient basis for illness to describe employee personalities, and what we could do to better team culture in the workplace. This is, of course, an overly simplified explanation of what philosophers both modern and old have struggled to understand. Hippocrates, who?
Distributed teams. Highlights of his career include heading up engineering at New Relic as it grew from 3 developers to 330; growing Invision from 60 developers to 350 as its CTO; working on VisualAge Smalltalk at OTI (Object Technology International); and coordinating the open-source Eclipse developers at the Eclipse Organization.
The Core Responsibilities of the AI Product Manager. Product Managers are responsible for the successful development, testing, release, and adoption of a product, and for leading the team that implements those milestones. Product managers for AI must satisfy these same responsibilities, tuned for the AI lifecycle.
Gone is the massive workforce that came to a workplace boasting three-course meals in the cafeteria and needed yoga rooms and sleeping pods to function. Companies across the board are reviewing their team structures, looking for removable cushioning, cutting down on middle management, and wanting to do more with less.
Distributed teams. Highlights of his career include heading up engineering at New Relic as it grew from 3 developers to 330; growing Invision from 60 developers to 350 as its CTO; working on VisualAge Smalltalk at OTI (Object Technology International); and coordinating the open-source Eclipse developers at the Eclipse Organization.
One of the most valuable skills one can possess as a developer is to learn how to scope down your work into manageable pull requests (PRs). We’ll dive into some of those whys, and then move on to the hows: the processes you can use to scope PRs down, as well as who on your team can assist. It’s easier to test.
Leaders of distributed engineeringteams shouldn’t have to work up solutions to these problems from scratch. So we held a panel discussion with three of today’s top engineering leaders to discuss approaches and lessons learned in building, growing, and maintaining remote and distributed teams.
As engineeringmanagers and leaders, our job of course is to help our teams deliver value to the organization and its customers. Yet from a higher level, our role is to ensure that both engineers and teams continue to grow and develop. That’s our sprint-by-sprint purpose in a nutshell.
GitPrime elevates engineering leadership with objective data. In this interview series, Engineering Leaders talk about how to build high performing teams. Johnathan Nightingale has seen first-hand how powerful a solid management structure can be for growing organizations. “We No one is overwhelmed with direct reports.
Developed in 2012 and officially launched in 2014, Snowflake is a cloud-based data platform provided as a SaaS (Software-as-a-Service) solution with a completely new SQL query engine. You can also become a member of like-minded people by emailing the Snowflake team. Cloud-agnostic approach: a weakness? What is Snowflake?
In this series, we pulled aside folks from across our engineering department to talk about confidence. From the technical executives to folks on the ground in engineering, management and site reliability, we wanted to know what “confidence” meant to them, and how it had changed over the course of their careers.
Of course there was a rough budget based on history, but when a control system was going to be used for some decades, one was never penny wise and pound foolish. One day, after I had some experience myself, an engineeringmanager from upstairs came to ask me for help.
In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineeringmanagement (1:35). How efficient is the team? Transcript.
There is an inherent difference between leaders and managers that is often overlooked. While most think that leaders are “born,” Katie Womersley, VP of Engineering at Buffer, disagrees. Katie’s journey into management. Transitioning others into management and bumps along the way. I am VP of Engineering over there.
GitPrime elevates engineering leadership with objective data. In this interview series, Engineering Leaders talk about how to build high performing teams. That means on a day-to-day level, a career-path level, and a living-breathing-creature level for every one of your engineers and managers.
“We’re really struggling with the Product Owner concept, and many of our Scrum teams just don’t feel very productive.” The company had several vertical markets, with a Scrum team of about ten people assigned to each market. Each market had a Product Manager, a traditional role found in most product companies. they told us.
On May 21, for the Test in Production Meetup on Twitch , Yoz Grahame, Developer Advocate at LaunchDarkly, moderated a panel discussion featuring Rebecca Murphey, Senior Technical PM at Indeed, and Ben Vinegar, VP of Engineering at Sentry. Prior to taking on the tactical project manager role, I was in a senior engineeringmanager role.
In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineeringmanagement (1:35). How efficient is the team? Transcript.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. You’ve decided that Agile will make your teams more successful. Second Edition cover.
In this series, we pulled aside folks from across our engineering department to talk about confidence. From the technical executives to folks on the ground in engineering, management and site reliability, we wanted to know what “confidence” meant to them, and how it had changed over the course of their careers.
The practice of one on ones is important in connecting to a team. @6:44. Announcer: Welcome to the Programming Leadership Podcast, where we help great coders become skilled leaders, and build happy-high performing software teams. And of course if you’re not sure who he is, you might know him by his other name Rands.
The practice of one on ones is important in connecting to a team. @6:44. Announcer: Welcome to the Programming Leadership Podcast, where we help great coders become skilled leaders, and build happy-high performing software teams. And of course if you’re not sure who he is, you might know him by his other name Rands.
In this Perspectives in Engineering interview series, engineering leaders talk about how to build, coach, and scale world-class technology teams. Saminda Wijegunawardena , VP of Engineering at Box, calls this increasing distance “abstraction.” This role doesn’t change whether an engineering org is 5, 500, or 5000 strong.
On June 18, Ben Wilson, EngineeringManager at InVision, spoke at LaunchDarkly’s Test in Production Twitch Stream. Ben explained the process of how, when, and why a virtual squad may be your best bet to speed up decision-making and time-to-release across your engineering, product, and design organizations.
How do we improve in the area of product management? In this episode of Programming Leadership, Marcus and his guest Ellen Gottesdiener, President of EBG Consulting, discuss ways companies can better oversee the development and lifecycle of a product in its entirety. Managing the work vs. the product (19:19). EBG Consulting.
Drawing on his 40 years in the software industry, GeePaw’s solution is to develop a thick culture in which certain standards are established across the industry. How the doubling rate resulted in a lack of leaders that can develop an industry discipline (6:34). Developing a common language of change in the trade (24:24).
Admitting you’re afraid and need help and being vulnerable is a sign of strength not a weakness. @13:48. Announcer: Welcome to the Programming Leadership Podcast, where we help great coders become skilled leaders and build happy, high-performing software teams. ” No, the poor man just walked into the bathroom.
Although you may see more articles on microapps popping up recently, the term and development strategy has been around for some time. To save you some time, here are the 4 top things I've learned about microapps: They reduce complexity for developers and users. Reducing Complexity for Developers and Users.
Announcer: Welcome to the Programming Leadership Podcast where we help great coders become skilled leaders, and build happy high performing software teams. Progressed, eventually, to leading test teams, and managing testers, and then moving more into agile roles and team coaching. Links: Sponsor: GitPrime. Transcript.
Announcer: Welcome to the Programming Leadership podcast where we help great coders become skilled leaders and build happy, high performing software teams. Lara: Yeah, I’m guessing you are talking about these new manager care packages. But like, what if we made a care package for new managers?” Transcript.
Will’s book, An Elegant Puzzle: Systems of EngineeringManagement. Speaker 1: Welcome to the Programming Leadership podcast where we help great coders become skilled leaders and build happy, high performing software teams. Marcus: Will, you are a manager now. When you were little, did you want to be a manager?
In this episode of Programming Leadership, Marcus and his guest Don Gray enlighten listeners regarding the world of software development, the reasons for implementing software changes and why it’s not as easy as people may think. Software development is not linear and not deterministic. Show Notes. Change is complex. Transcript.
Announcer: Welcome to the Programming Leadership podcast, where we help great coders become skilled leaders and build happy, high performing software teams. And it doesn’t matter, it kind of in some ways you know in that stage it doesn’t matter how good you are or how bad you are at managing. @AttackGecko.
And then two years later, I switched to the engineering side of the organization where I currently lead team-building marketing automation solutions, bringing Data Science and Machine Learning to solve these problems for our customers. And we also have dedicated teams to look into some of this. Alfred: Great. Vatsan: Well.
Is conflict always a bad thing? Conflict may be uncomfortable, but it is not always bad. Conflict may be uncomfortable, but it is not always bad. Tension provokes uncertainty which can then change dynamics of individuals or even teams. So, I am a Conflict Management Practitioner and Leadership Development Consultant.
That doesn’t mean everyone on the team has to dress in feathers, rather it means leadership is dynamic, shifting, and also tight knit. In this episode of Programming Leadership, Marcus talks about what it takes to be a good leader and provides real solutions on how to build trust and gain feedback from your team. Show Notes.
Everybody has the capacity to develop compassion; it’s about how we direct our energy, time, and effort. @21:29. Announcer: Welcome to the Programming Leadership Podcast where we help great coders become skilled leaders and build happy high-performing software teams. Compassionate Coding Twitter: @CompassionCode. Transcript.
Then he went on to talk about a zombie haunted pipeline that kept developers awake late into the night. Watch the video below to learn how Eric’s teams survived these horrific events, and the lessons learned that will never be forgotten. I worked on that team for about seven years. TRANSCRIPT.
Charity once said an off-hand sentence that became a mantra for my transition into the VP of Engineering role: “Directors run the company.” Cross-team interactions felt fraught; focus was constantly shifting; nobody was ever sure what bar we were being measured against.
There’s a reason I follow Musk – besides the promise of a Mars trip, I look at him as one of the prime examples of a successful, self-taught developer. . He’s not the first; of course. Every generation has had at least one name who has proven that the best developers are the ones with the best skills, not the best resumes. .
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content