Suggestions
Yonas Beshawred
Founder & CEO at StackShare
Yonas Beshawred is the Founder and CEO of StackShare, a platform that allows developers and companies to share and discover software tools and technologies.13 He founded StackShare in 2014 as a solution to help developers choose the right tools for building applications.23
Beshawred's background includes:
-
Education: He holds a B.S. in Information Systems from the University of Maryland's Robert H. Smith School of Business (2005-2009) and an M.S. in Human-Computer Interaction from the University of Maryland College Park (2011).12
-
Early Career: After graduation, he worked as a business analyst at Accenture before moving to Silicon Valley to join a startup called Cube as an intern.2
-
StackShare Journey: He started StackShare as a side project, which grew into a community of over 1 million developers.3 The platform allows users to share their tech stacks and helps companies map out their internal technology usage.3
-
Acquisition: In August 2024, StackShare was acquired by FOSSA, with a reported valuation of $20 million.5 Beshawred now serves as the Head of Product for StackShare at FOSSA.4
-
Entrepreneurial Spirit: Beshawred comes from an immigrant background, with his parents moving from Ethiopia to the United States.2 This upbringing influenced his entrepreneurial drive and problem-solving approach.2
Throughout his career, Beshawred has focused on solving problems in the tech industry, particularly in helping developers and companies make informed decisions about their technology stacks.235
Highlights
“Overall tests are now about 4x faster” @starslingdev 🚀
Faster runners make CI jobs faster. They don't make you run fewer of them.
Where CI time actually goes (and the fix for each):
-
Compute: the job itself. Faster machines help here.
-
Waiting: queues from concurrency caps. A faster machine doesn't shorten a queue.
-
Setup: checkout, installs, cache restores. Shallow checkouts and warm caches.
-
Redundant work: runs for commits you already replaced, the full suite for a docs change. cancel-in-progress, path filters, affected tests only.
-
Idle time: fixed sleeps, healthchecks that wait on an open port instead of a ready database.
Most teams only fix #1. The bigger wins are usually in 2–5, and they live in your workflow files, not your hardware.
