TechCrunch
AUGUST 29, 2022
Astro , a startup helping companies to build and manage developer teams 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.
Strategic Tech
MARCH 16, 2021
If you’re interested in improving the design mindset in your engineering culture, 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.
Apiumhub
MARCH 3, 2022
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 engineering culture in their organizations. Break the routine and allow the team to have another perspective on some parts of the project.
O'Reilly Media - Ideas
NOVEMBER 22, 2022
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.
Gitprime
MAY 30, 2019
Leaders of distributed engineering teams 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.
CircleCI
APRIL 20, 2022
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.
CircleCI
OCTOBER 25, 2021
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?
Expert insights. Personalized for you.
188 
Let's personalize your content