I’m an engineer during the day and a founder at night – so I don’t have time to fiddle with complicated instrumentation or bugs that are hard to track down. That’s why I picked the tech stack that I did.
There are major package size benefits to reducing the amount of generated JavaScript your package is creating. As part of our larger Javascript SDK package reduction, we spent a considerable effort to minify as much of our code as possible. If you’re looking to do the same, here are six improvements to consider.
Leading a team through different growth stages requires evolving insights and for Gorgias CTO and co-founder, Alex Plugaru, it’s important to understand how developers work, not just what they’re working on.
In this post, Matt-Johnson Pint from the Sentry .NET team walks us through how he made a Time Zone Picker user interface control for .NET MAUI, leveraging MAUI's support for platform-specific code.
Developers started to notice just how big our JavaScript package was and yeah, we knew. We weren’t ignoring the issues; after all, we don’t want the Sentry package to be the cause of a slowdown. But to reduce our JavaScript SDK package size effectively we had to account for shipping new capabilities, like being able to manage the health of a release and performance monitoring, while maintaining a manageable bundle size. After all, new features == bigger package - usually.