A few days ago I instituted a new organisational paradigm for a project at work - bugzilla. This move was done because I was getting slowly fed up with everyone coming straight to me to report what's not working well, often something I was either already working on or something that was far away from what I was currenlty doing.
Naturally a lot of the stuff got forgotten along the road before I could get around to them, I also had no idea how important something was and how much it broke things. This is where bugzilla comes in. It keeps all bug reports in a nice format, organised by priority and I get notified of any new bugs or changes to them via e-mail.
What I love most is the sequental nature of bug displaying. I can just go to the first bug, resolve it and it shows me the next bug I should work on based on priority and some other things I can't quite fathom. It's awesome because it gives me a clear "This is what you should do next, do it!" so I don't have to bother with organising myself and just focuse on the code.
What I don't like about bugzilla, however, is that it's so very obviously made by engineers, for engineers. Worse still, made by bugzilla users for bugzilla users. As a new kid in town it took me quite a while to even figure out how to set things up and teaching my boss to bugreport? HA! I'm lucky he even agreed to using it ... and we're trying to put the application in a public alpha testing next week where anyone should report bugs they find.
Luckily though I'm getting more and more used to bugzilla and was so able to put a link on the front page that lists all bugs - I think - and set up a default user with all the login fields already filled in for anyone not wishing to make a special account.
No matter the difficulties, bugzilla will be used with all large-ish projects I work on henceforth.
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️