Posts

I’m a huge music nerd. I’ve played in many bands in my teens 20s, and music is a big part of my life.. I’m also a big fan of Pitchfork music reviews. There was a mashup site I was using called Pitchify, which was no longer updating, and it eventually got taken down. So I did what any engineer would do and I created my own mashup! 12inch.reviews is a mashup of Pitchfork’s album reviews with Spotify’s web playback SDK. It utilizes the browser’s IndexedDB API to allow for fast, responsive searching and sorting of 17k+ album reviews, and allows you to play the full album right in the browser! ...

I am an avid side project-er. At any point in time I always have at least one “thing” going on in the background that feeds my appetite for playing with new tech and learning new stuff. Side projects can be liberating and super fun. They are great for your career overall and could lead to great opportunities. These side projects have had an amazing effect on my career, and they can help yours immensely as well! ...

When it comes to software, the term “QA” itself is highly loaded. Because what is it, really? Is it just a thing at the end of the software delivery line, where quality gets lovingly sprayed on at the end, achieving a nice glossy sheen? Is it a separate department that bolts on quality, where the engineers don’t really need to worry about it after they throw it over the wall? Is it that one integration test that one engineer wrote, once, and it’s “probably good enough”? Of course not! ...

“Ok, so we launched our new feature last night. However we have 30 customer emails from last night about bugs, and we need to hit those right away. Also the error rate is a little spikey, which probably means there’s more issues, and our response time is up a few ticks. Have a nice day!” What a bummer. This is unfortunately how things go during a standup meeting after just after shipping a successful feature. The above narrative might as well be the following instead: ...

Individuals an interactions over processes and tools. Why? Because the first principle of the Agile Manifesto is so easy to break. We broke it big time, and we learned a lot when fixing it. Tools like Jira seduce you into building a mammoth process that is convoluted and hard to convey to your team. You get blinded by the allure of super-sweet metrics and charts. And so the thought goes: “We’ll know our burndown rate and velocity, and it will all be on this pretty graph, and we’ll put it up on the wall TV, and we shall revel in our newfound measurements!” ...

The following is a story about how we matured as an engineering team. We went from an ad-hoc process to Scrum, and used Scrum for a whole year. Scrum leveled us up as a team in terms of structure and process. But it caused major morale issues. Then we found Kanban. We implemented it and have never looked back. From nothing to Scrum We started using Scrum after using a strange, ad-hoc system of developing software. There was a perception from the rest of the company that things were disorganized. We did not have a PM and did not have a great communication channel to the rest of the company. No one knew when things were shipping or what they included when they shipped. We had quality issues because QA was not a big part of the process, and we did not do peer code reviews, so we spent more time fixing bugs than shipping features. ...