Beacon is giving development teams the ability to measure what matters. We take best practices from production observability and apply it to local environments.
Meet Beacon!
We’ve built the first dev experience platform for frontline eng mgrs. Development complexity is increasing; teams don’t measure the impact of this. Big tech co’s have solved this w/ whole teams. Who’s looking out for everyone else?
Try us out: https://t.co/BUt6IRr2Th
CPA fired for misrepresenting time spent on a project. Company used time tracking software to nail her.
Should this type of software be used in software engineering? If so, how? If not, why not?https://t.co/LPKsaljcgW
@CIOonline #3 prio for 2023: rationalize the tech estate.
More powerful tech & cloud-based services + not retiring legacy systems they were meant to replace = tech debt. Time to “reallocate those resources towards building the future” https://t.co/41FXjoB2Vf
Air traffic is resuming after the FAA lifted an order to ground all U.S. flights. Thousands of flights are still facing delays.
Follow updates. https://t.co/o0p5WazWzj
Sometimes there’s more tech debt to be fixed than the “20% time” can handle
You can: quantify the impact (as much as possible), share where the unknowns lie & understand your counterpart’s goals...
How do you explain tech debt to your non-tech teammates? https://t.co/oCdSOkTwHS
Most of us think about time management to max our productivity, but it's helpful to reframe as ENERGY management. We assume we don't need as much rest (in all forms) as we likely do.
How do you keep your energy tank topped up? https://t.co/iH8Ig1ZTGf
“Software half-life seems to be decreasing rapidly across the board…what’s stayed the same? The developer tools” …that can handle the constantly shifting landscape @mattrickard https://t.co/XB1xATVIzZ
@cmccarty@kaitlinsennatt Oh 👋 @cmccarty! I like that approach so you can take on something bigger...and focus...
Do you try to quantify tech debt at all?
Most high performing teams we spoke with used “fixed” time to pay down tech debt, devoting a % of each sprint to fixing or improving tech debt...usually 20%...
How is tech debt prioritized on your team? Is it working?
How do you quantify the impact of paying down tech debt?