Blog Insights
Formula For Successful Feedback
Feedback doesn’t have to be difficult or scary. Follow this simple formula to structure your next feedback conversation.The Samaritan Engineers
In this post we look to explore some of the techniques and attributes that make engineers unique and highly productive5 Lessons in Product Delivery from Assembling a Murphy Bed
I noticed several similarities between assembling furniture and delivering software.My Apprentice Experience: Working With Many Teams...
Sharing my experience as a Source Allies apprentice.Technical Interviewing at Source Allies
Thinking about joining Source Allies? Here's what you can expect from our technical interviewing process.Growth Fueled by Feedback
"We have to be able to take feedback-regardless of how it's delivered – and apply it productively. We have to do this for a simple reason: mastery requires feedback. I don't care what we're trying to master – and whether we're trying to develop greatness or proficiency – it always requires feedback." - Brené Brown, Dare to Lead.Consulting 101 Part 3: Partner Dynamics
Recently Akrem and Erick presented Consulting 101, an annual presentation delivered at a Source Allies University event. We are publishing a three-part blog series that is a distillation of that presentation. In this third and final part we will be discussing partner dynamics.Consulting 101 Part 2: Team Dynamics
Recently Akrem and Erick presented Consulting 101, an annual presentation delivered at a Source Allies University event. We are publishing a three-part blog series that is a distillation of that presentation. In this second post we will be talking about Team Dynamics.Consulting 101 Part 1: Agile Crash Course
Recently Akrem and Erick presented Consulting 101, an annual presentation delivered at a Source Allies University event. We are publishing a three-part blog series that is a distillation of that presentation. This first post is a crash course on Agile.Hackathon 2021: Escape of the Mad Scientists
What happens when you put several teammates in a room together, separate them out into project teams, and give them less than 48 hours to produce an MVP? A successful Hackathon!