Featured Post

Notes and takeaways from Software Engineering at Google

    I really enjoyed and learned a lot from this book.  I noted that, as is the case with many O'Reilly books about best practices at Google, different people will find various chapters more/less interesting and pertinent to them. Below are the excerpts that I found most pertinent.   Leadership Contrary to some people’s instincts, leaders who admit mistakes are more respected, not less.
 If you perform a root-cause analysis on almost any social conflict, you can ultimately trace it back to a lack of humility, respect, and/or trust.
 Your organization needs a culture of learning, which requires creating psychological safety that permits people to admit to a lack of knowledge.
 If you try to achieve an impossible goal, there’s a good chance you’ll fail, but if you fail to try to achieve the impossible, you’ll most likely accomplish far more than you would have accomplished had you merely attempted something you knew you could complete.
 “Sometimes you get to be the tooth fairy, other

Zoom meeting best practices

  My Zoom meeting best practices (also now in my engineer read me): If I don't have my video feed on, it is likely because I am listening but multitasking (working on something, doing something at home, etc) and I don't want those other activities to be distracting to the meeting attendees. I will sometimes use the Zoom emoji feature rather than interrupting the speaker to express my feedback on something. I find that this allows me to provide feedback without interrupting whoever is speaking. I am working on interrupting people less, slowing down my pace, and pausing more often. This is to increase the clarity of what I am communicating while also increasing my emotional intelligence. I am getting real-time feedback on this via a system called Poised . In particular, rather than interrupting a speaker when I have something to say, I am trying to indicate that via non-verbal communication via video. Photo by iyus sugiharto on Unsplash  

My notes on No Rules Rules: Netflix and the Culture of Reinvention

  Summary Value people over process Emphasize innovation over efficiency Minimize controls Talent density Talented people make one another more effective.  High performers thrive where talent density is high. Adequate performers: Sap manager’s energy Reduces the quality of discussions Cause others to work around them Drive people who seek excellent to quit Show the team that the leader accepts mediocrity Jerks, slackers, and sweet people with non-stellar performance, or pessimists on the team will bring down the performance of everyone. Feedback Put feedback on the agenda of every one on one meeting. Don’t just ask for feedback, but show your team it is expected. Clarify the difference between being selflessly candid vs being a brilliant jerk Don’t seek to please your boss, seek to do what is best for the company. Innovation cycle: Farm for descent Test out big ideas Make your bet If it succeeds, celebrate.  If it fails, sunshine it (learn from it and make it transparent so others can

AMA : Transparency - A core value at GitLab

  I did an AMA on "Transparency - A core value at GitLab" with PlatoHQ.  What a fun discussion!

Panel discussion on 20 years of agile - the good, the bad, and the ugly

 I was able to participate in a great panel discussion on 20 years of agile - the good, the bad, and the ugly sponsored by Agile New England .   Details and contact information for the speakers.

Talk on engineering productivity, metrics, and morale

You will find below my talk (sponsored by non-profit in Singapore) on engineering productivity, metrics, and morale.  The questions were awesome. 😎 Recording   Slides      

Security Shouldn't be a Secret. Why Transparency Matters

 Security Shouldn't be a Secret. Why Transparency Matters   Two discussions on this topic are below.   Interview with Security Weekly podcast Security can be somewhat of a mystery at a lot of organizations. Most companies choose to be tight-lipped about the security measures they have implemented. Rightfully so, there is an underlying fear that publicizing your security efforts could make you more vulnerable to security attacks and damage your reputation with your customers. However, there is another way. Transparency can be your ally in security.  In this interview, we will be talking about how transparency practices can lead to improved security. With transparency being one of our core values at GitLab, we will talk about the processes we have implemented to maintain our security stance while operating with the highest possible public transparency and how you can apply them to your enterprise to achieve increased security and transparency.  Recording:  ISSA webinar Security can

Nice to see this patent application I worked on with a peer published by the USPTO

Systems and Methods for Distributed Extended Common Vulnerabilities and Exposures Data Management Abstract In one aspect, the present disclosure is directed to systems and methods for validating and securely storing security entry updates. The security entry update is received from a contributor, and broadcast to a plurality of computing nodes. It then is determined whether to validate the received security update at each computing node of the plurality of computing nodes. If the received security entry update is validated, information relating to the received security update is added as transaction information in a current block, the current block is included in a blockchain that is stored in a datastore of each computing