Passa ai contenuti principali
Nessun elemento trovato.
Logo di Dropbox Sign
Perché scegliere Dropbox Sign?
Fisarmonica aperta o chiusa

Cosa puoi fare

Firma documenti online
Creare firme elettroniche
Scegli o crea modelli
Firmare e compilare file PDF
Completare contratti online
Gestione dei documenti
Esplora le funzionalità
Icona di una freccia che indica a destra

Casi d'uso

Vendite e sviluppo aziendale
Risorse umane
Startup
Tecnologia finanziaria
Immobiliare
Servizi on demand
Prodotti
Fisarmonica aperta o chiusa
icona dropbox
Sign
Semplifica l'invio e la firma
icona dropbox
Sign API
Integra eSign nel tuo flusso di lavoro
Icona di Dropbox Fax
Fax
Invia fax senza ricorrere al fax
Icona delle integrazioni Dropbox
Integrazioni
Noi ci adattiamo al tuo lavoro
Risorse
Fisarmonica aperta o chiusa
Blog
Competenza nei flussi di lavoro e novità sui prodotti
Storie di clienti
Storie reali con risultati concreti
Centro assistenza
Guide approfondite per i nostri prodotti
Libreria delle risorse
Report, video e schede informative
Sviluppatori
Prezzi
Fisarmonica aperta o chiusa
Prezzi di Dropbox Sign
Trova il piano che fa per te
Prezzi di Dropbox Sign API
Storie reali con risultati concreti
Contatta l'ufficio vendite
Registrati
Contatta l'ufficio vendite
Accedi
Fisarmonica aperta o chiusa
Dropbox Sign
Dropbox Forms
Dropbox Fax
Prova gratuita
Blog
/
Sviluppatori

Recharge Your Dev Team with a Bug Squash

Scritto da 
Chris Paul
August 24, 2016
3
Durata della lettura:
Recharge Your Dev Team with a Bug Squash
Icona Suggerimenti

Lo stesso prodotto con un nuovo aspetto! HelloSign è diventato Dropbox Sign!

Icona Chiudi

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."  

Rimani sempre aggiornato!

Fatto! Controlla la posta in arrivo.

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
Icona di una freccia che indica a destra
Icona Chiudi

Up next:

Illustrazione in primo piano di una firma scritta a mano, che rappresenta le moderne soluzioni di firma digitale.
Sviluppatori
15
Durata della lettura:

Integrazione di Dropbox Sign con Ruby on Rails: un tutorial dettagliato

Illustrazione in primo piano di una firma scritta a mano, che rappresenta le moderne soluzioni di firma digitale.
Sviluppatori
15
Durata della lettura:

Dropbox Sign vs. SignNow for developers

Evento

Dropbox Sign a Startup Grind 2022: come espandere la tua startup mantenendo il fattore umano al primo posto

Prodotti
Dropbox SignDropbox Sign APIDropbox FaxIntegrazioni
Perché scegliere Dropbox Sign
Firme elettronicheFirma documentiFirmare e compilare i PDFContratti onlineCreare firme elettronicheEditor di firmaFirma su Word
Supporto
Centro assistenzaContatta l'ufficio venditeContatta il supportoGestisci cookieGuida introduttiva: Dropbox SignGuida introduttiva: Dropbox Sign API
Risorse
BlogStorie di clientiCentro risorseGuida alla legalitàTrust Center
Partner
Partner strategiciPartner Locator
Azienda
Opportunità di lavoroTerminiPrivacy
icona facebookicona youtube

Metodi di pagamento accettati

Logo di MastercardLogo di VisaLogo di American ExpressLogo di Discover
Badge di conformità con la legge CPABadge di conformità con le norme HIPAABadge di Sky High Enterprise ReadyBadge della certificazione ISO 9001

Le firme elettroniche di Dropbox Sign sono legalmente vincolanti negli Stati Uniti, nell'Unione Europea, nel Regno Unito e in molti altri Paesi nel mondo.
Per ulteriori informazioni, consulta i nostri termini e condizioni e le Norme sulla privacy