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
Astro , a startup helping companies to build and manage developerteams with talent from Latin America, today exited from stealth with $13 million in Series A funding contributed by Greycroft with participation by Obvious Ventures and other unnamed investors. million by 2030. based tech companies.
Kent Beck concluded , Measure developer productivity? He says a measurement based approach generates relatively weak improvements and significant distortion of incentives. Its not about literally being the best product engineering org in the world. We use Extreme Programming as our model of how to develop software.
If you’re interested in improving the design mindset in your engineeringculture, I hope that the following techniques provide you with some food for though. For many people, this is a waste of time; it’s pretentious developers geeking out over unnecessary perfectionism. So we need to make it part of everything we do.
Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the software development and boost a proactive, continuous improvement-based engineeringculture in their organizations. Break the routine and allow the team to have another perspective on some parts of the project.
Platform engineering can help organizations reduce cognitive load for developmentteams, and create a significant improvement in developer experience (DevEx) as well as several other areas. Test that the capabilities you want to deliver are actually desired by the teams. Build a pl atform b ased on an actual need.
HackerEarth’s assessments can help you gain valuable insights into candidate strengths and weaknesses, helping you make data-driven hiring decisions and personalize onboarding experiences. Check with your team if you need advanced search functionalities, skills assessments, or employer branding tools, for instance.
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.
For many developers, unit tests and integration tests are often top of mind. Your team’s testing practice should assess the entire application, observe the larger story of how it operates when functioning correctly, and raise alarms when deviations are found. Many teams don’t view security testing as part of their testing suite.
Ourselves: to remind us what we’ve done, and to create an opportunity to reflect on how things have developed since. Our team(s): to give them a broader view of our work, to demonstrate openness about the highs and lows of being a software engineer, and to encourage a growth mindset. Who are personal retrospectives for?
Any significant shift in an organization’s software engineeringculture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. This is why we highly encourage all teams to instrument their code to emit telemetry data. .
PDF) Culture Changes The purpose of the new career ladder is to help change the engineeringculture at OpenSesame. For managers that are new to their team, it’s been tough. Software Engineer Software Engineers contribute to the work of their team without explicit guidance.
At the November Test in Production Meetup in San Francisco, LaunchDarkly’s Yoz Grahame (a Developer Advocate) moderated a panel discussion featuring Larry Lancaster, Founder and CTO at Zebrium, and Ramin Khatibi, a Site Reliability Engineer (SRE) and infrastructure consultant. So, I guess I’m a bad expert on process.
Orchestrated Functions as a Microservice by Frank San Miguel on behalf of the Cosmos team Introduction Cosmos is a computing platform that combines the best aspects of microservices with asynchronous workflows and serverless functions. The centralized data model that had served us well when we were a small team became a liability.
A DDD Exemplar is a project, ideally achievable within a quarter, that results in improvements in a domain(s) and improvements in how teams build products. It lays the foundations for other teams to copy and adapt. It’s a proof-of-concept for how teams build products. Why Thing Get Stuck After Discovery?
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 engineering manager role.
That graph should represent social relations which can be enriched with information about normal engineering practices that each person and their team perform, such as periodic sprint cycles, regular post-incident meetings, or widely adopted standards and tools. This initial group forms the basis of a social graph.
I was working for a big company that had a strong vibrant engineeringculture. The different teams were scattered all over the planet, so coordinating all of the efforts was vital. The QA team had its own separate repo, and more importantly, they had their own environment configurations for our code as well.
Interview with Kevin Wylie This post is part of our “Data Engineers of Netflix” series, where our very own data engineers talk about their journeys to Data Engineering @ Netflix. Kevin Wylie is a Data Engineer on the Content Data Science and Engineeringteam. Kevin, what drew you to data engineering?
Corey Bertram, VP of Infrastructure & SRE at Datadog spoke about how his organization does chaos engineering. He shared his experiences from when he led the SRE team at Netflix, and how thats influenced the way he’s helped the Datadog team put process around chaos engineering experiments. Go after the easy wins.
This book is an excellent read and it covers small things that you can do to build trust and to become an authentic and true leader to your team at different stages of your leadership journey. Book advocates that by focusing on the small things and executing them well, leaders can create a lasting impact on their teams and organisations.
He describes “some surprising theories about software engineering”: I discuss these theories in terms of two fundamentally different development styles, the "cathedral" model of most of the commercial world versus the "bazaar" model of the Linux world. However, the open source world figured out a better way to develop software.
This proactive approach reflects an important shift from older reactive approaches to security, in which you deploy software and hope nothing bad happens. Better that someone on your team discovers that vulnerability first. Open Source and a Culture of Sharing. That’s an important statement.
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.
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