Pasar al contenido principal
No se ha encontrado ningún elemento.
Logotipo de Dropbox Sign
¿Por qué elegir Dropbox Sign?
Desplegar o contraer acordeón

Qué puedes hacer

Firmar documentos en línea
Crea firmas electrónicas
Selecciona o crea plantillas
Rellenar y firmar PDF
Finalizar contratos en línea
Gestión de documentos‍
Ver funciones
Icono de flecha hacia la derecha

Casos prácticos

Desarrollo comercial y de negocio
Recursos humanos
Start-ups
Tecnología financiera
Propiedad inmobiliaria
Servicios a la carta
Productos
Desplegar o contraer acordeón
Icono de Dropbox
Sign
Facilita el envío y la firma
Icono de Dropbox
Sign API
Integra las firmas electrónicas en tu flujo de trabajo
Icono de Dropbox Fax
Fax
Envía faxes sin tener fax
Icono de integraciones de Dropbox
Integraciones
Estamos donde trabajas
Recursos
Desplegar o contraer acordeón
Blog
Amplios conocimientos sobre flujos de trabajo y noticias sobre productos
Experiencias de clientes
Historias reales con resultados tangibles
Centro de ayuda
Consejos avanzados para usar nuestros productos
Colección de recursos
Informes, vídeos y hojas informativas
Desarrolladores
Precios
Desplegar o contraer acordeón
Precios de Dropbox Sign
Encuentra el plan perfecto para ti
Precios de Dropbox Sign API
Historias reales con resultados tangibles
Contactar con ventas
Registrarse
Contactar con ventas
Iniciar sesión
Desplegar o contraer acordeón
Dropbox Sign
Dropbox Forms
Dropbox Fax
Pruébalo gratis
Blog
/
Desarrolladores

Recharge Your Dev Team with a Bug Squash

por 
Chris Paul
August 24, 2016
3
minutos de lectura
Recharge Your Dev Team with a Bug Squash
icono de mensaje emergente

Cambio de imagen, pero ¡el mismo gran producto! HelloSign ahora es Dropbox Sign.

icono de cerrar

If you’re a developer, you likely spot (and ignore) irksome bits in your code or product regularly. Perhaps it’s an excessively long if-block or a border offset by 1 pixel too many. Maybe you manually run through 5 steps every week to get your test database just right. 

‍

We let these annoyances slide because we might not have time to fix them. We also understand that what seems small isn’t always a quick nip-tuck fix. 

‍

Last year, the Dropbox Sign engineering team started holding a quarterly "Bug Squash" to clean up these exact types of issues. Like the name implies, it’s a two-day event to fix small bugs but we also use the time to make workflow enhancements, perform housekeeping, create developer tooling, fix broken windows, and tinker with small projects. 

‍

It’s had a positive effect on team morale and satisfaction, and resulted in improved product quality and provided useful improvements to the team and our users. 

‍

Some examples of what we’ve squashed:

‍

  • Added a Google Inbox Action to our signature request emails.
  • Fixed the display of apostrophes in team names.
  • Quieted noisy logging and tests.
  • Replaced the JavaScript alert() calls in our internal support tool to use Sweet Alert (because our Support Team is equally sweet!).

‍

Bugs and product improvements aside, the eight days a year we use to re-channel our energy has been time well spent from an emotional and psychological health perspective. We’re a small team and spend the remaining 97% of the year driving product initiatives to our users. A two-day breather mixes the schedule up, allowing us to focus on something new and flex our engineering muscles in a way that feels more like play than work. 

‍

This may not be the first time you’ve heard of a Bug Squash. Some companies even regard them as an anti-pattern that should be avoided because they communicate that quality can be added later. 

‍

At Dropbox Sign, the quality improvements that result from the Bug Squash are expressly secondary. We dedicate a percentage of every release cycle to fixing bugs that are prioritized by our QA, Product, and Customer Care teams and the Bug Squash is just another tool in our belt that gives our engineers freedom to practice their craft and take pride in their product, team, and dev environment. 

‍

If we’ve convinced you to try your own Bug Squash, consider these tips that have worked well for us:

‍

Get Buy-In

‍

The support of your department and company can go a long way towards positioning the Bug Squash for success by eliminating fears of distraction or time wasted. Impress upon stakeholders the importance of pride and high morale that can motivate engineers to take deeper ownership in their work and product the rest of the year.

‍

Create a Wish List

‍

Encourage your teammates to create Bug Squash tickets year-round. We use JIRA and ticketing these items is helpful when prioritizing, coming up with a theme, and ultimately pulling changes into your SDLC and QA process.

‍

Pick a Theme 

‍

Choose a broadly applicable theme like “UI Polish,” “The API,” or “Integrations” to provide direction for new team members or those that have long lists and require a bit of focus.

‍

Celebrate and Share

‍

Schedule a team review at the end of the Bug Squash to talk about accomplishments, challenges, and v2’s or next steps. Snacks and libations highly recommended! Don’t forget to share what you accomplished with the rest of the company and celebrate!

‍

Time to Get Squashing!

‍

Do you conduct events that are great for team morale? Have ideas or suggestions for improving this format? We’d love to hear your thoughts in the comments! 

‍

If you're interested in reading more about how we foster a positive developer environment here at Dropbox Sign, you might enjoy these posts: "5 Tips For Cultivating Psychological Safety" and "APIs for Humans: The Rise of Developer Experience."  

No pierdas el hilo

¡Listo! Revisa tu bandeja de entrada.

Thank you!
Thank you for subscribing!

Lorem ipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum
Icono de flecha hacia la derecha
icono de cerrar

Up next:

Ilustración en primer plano de una firma manuscrita, que representa soluciones modernas para la firma digital.
Desarrolladores
15
minutos de lectura

Integración de Dropbox Sign con Ruby on Rails: un tutorial paso a paso

Ilustración en primer plano de una firma manuscrita, que representa soluciones modernas para la firma digital.
Desarrolladores
15
minutos de lectura

Dropbox Sign vs. SignNow for developers

Evento

Flujos de firma electrónica ágiles y seguros: implementar la autenticación de firmantes por SMS con la API de Twilio

Productos
Dropbox SignDropbox Sign APIDropbox FaxIntegraciones
Por qué Dropbox Sign
Firmas electrónicasFirmar documentosFirma y rellena documentos PDFContratos onlineCrea firmas electrónicasEditor de firmasFirma de documentos de Word
Asistencia
Centro de ayudaContactar con ventasPonte en contacto con el departamento de asistencia.Gestionar cookiesPrimeros pasos: Dropbox SignPrimeros pasos: Dropbox Sign API
Recursos
BlogExperiencias de clientesCentro de recursosGuía de legalidadCentro de confianza
Socios
Socios estratégicosLocalizador de socios
Empresa
EmpleoCondicionesPrivacidad
Icono de FacebookIcono de YouTube

Métodos de pago aceptados

Logotipo de MastercardLogotipo de VisaLogotipo de American ExpressLogotipo de Discover
Insignia de conformidad con la CPAInsignia de conformidad con la HIPAAInsignia de Sky High Enterprise-ReadyInsignia de certificación ISO 9001

Las firmas electrónicas de Dropbox Sign son legalmente vinculantes en los Estados Unidos, la Unión Europea, el Reino Unido y en muchos otros países.
Para obtener más información, consulta nuestros Términos y condiciones y la Política de privacidad.