Happy Mother’s Day! To the single moms, this day should be yours two times over. I’m sorry if you don’t even get so much as a bathroom break to yourself today. To the almost moms, this day is yours. Don’t let anyone tell you otherwise; if they do, send them my way. To the moms that have lost a child, this day is especially yours. For those of us whose toxic moms have been extricated from our lives, this day might be a little heavier. That’s okay too; do what you need to do. No one says you can’t celebrate someone else’s awesome mom either. For example, Emily Freeman’s mom is the human embodiment of DevOps, honor her. Regardless, I hope everyone has a marvelous Mother’s Day. Ready for your dream tech job? Say goodbye to tech recruiter spam. Indeed Prime matches you with companies that fit your career goals and sends jobs right to your inbox. You’ll also have free access to technical career coaches who are here to help you with interview tips, resume best practices and more. Join for free today! SPONSORED ...

Friday afternoon (US east coast time), some oddities around git repos being taken for ransom started to pop-up. Safe to say, I’m paranoid af when it comes to the software delivery pipeline (GitHub and GitLab are both used to manage DevOps’ish). I immediately changed passwords everywhere I have code stored (and you should too if you haven’t already). GitLab chimed in on the issue to confirm it did not appear to be a total loss of data on affected repos and provided potential fixes. GitLab also provided extensive incident details I recommend checking out. The cause? The age-old problem of exposing version control dot directory when deploying a web site. Don’t publicly expose .git or how we downloaded your website’s source code. Find your next tech job No more inbox spam from recruiters! Indeed Prime matches you with top tech companies and only sends tech job opportunities that match your career goals, technical skill set, location, and salary preferences. Join for free today! SPONSORED ...

NOTE: Please read my Disclaimer before breaking out the tar and feathers. What a series of unfortunate events for Docker in 2019. In what appeared to be a massive talent flush due to what looks like a potential earnings miss, the Great Docker Culling of 2019 happened. Docker appears to have laid off the vast majority of its well-known talent. Andrea Luzzardi, Sam Alba, and Gareth Rushgrove are among a slew of recent Docker layoffs discussed in this newsletter earlier this year. According to one source teams were, “killed,” and Docker, “missed their number, and by a lot.” Fast forward to Friday night on the US east coast (like we weren’t going to notice?!?). Many people (myself included) received an e-mail from Docker about a Docker Hub breach impacting at least 190,000 accounts. According to the e-mail, “Data includes usernames and hashed passwords… as well as Github and Bitbucket tokens for Docker autobuilds.” Audit any Docker Hub tokens right now. Docker also, “revoked GitHub tokens and access keys. This means your autobuilds will fail.” Nothing like a page on a weekend because Docker broke your builds. Check your Docker Hub Linked Accounts and re-link them. You’ll then likely have to do a weird do-si-do in the Build config of one of your image pages to get everything working as is. ...

I hope you had a wonderful week and are looking forward to the week ahead. I have been heads down working on Red Hat Summit work, upcoming releases, and trying to properly define DevOps this week. But, it has left me little time to really think about solving new problems. What do you do when you have complex problems to solve but only short bursts of time to work on them in? It’s a balancing act for sure. Good luck this week in your endeavors! Log Management Modernized With LogDNA’s fast, multi-cloud logging platform, DevOps and Engineering teams can easily and quickly aggregate all system and application logs into one efficient platform. Whether on-premise, in the cloud, or a hybrid solution, we have you covered. Don’t take our word for it. Try it yourself. Get started logging in a few minutes with a free trial. SPONSORED 170+ live online training courses opened for March and April Get hands-on training in machine learning, AWS, Kubernetes, Python, Java, and many other topics SPONSORED ...

I received my first credible death threat from someone over the internet when I was eighteen (I was working for an ISP and had to cancel an account for terms violations). No one knew what to do then. A few years later, I referred a credible threat to the FBI for investigation (Muslim extremists). No one knew what I should do then either. A few months ago, a Twitter troll hounded my personal and several corporate accounts FOR DAYS. Why? I liked a tweet telling the troll people aren’t obligated to talk to them because they released open source software. I liked a tweet and had to watch a troll degrade my team, background, and professionalism. But, corporate policy is don’t feed the trolls, so I didn’t. I know folks that have gotten a lot worse. One of my coworkers did something awesome behind the scenes and I got credit for it. When I asked my coworker if I could credit them, they asked me not to. They didn’t want “that kind” of attention. That kinda sucked but, I completely understand. I talked to a friend of mine this week that was going through a hard time. They were getting all manner of trolls and “creepy fetish emails” this week. They protected their Twitter account and contacted their superiors as needed. But, at what point is the employer obligated to step in and digitally protect their employee? Sure, physical protection at events is excellent. But, the harassment on the internet this week alone has me thinking that employers do share some responsibility for it. We have these public personas for our jobs. The e-mails come to work addresses. At what point do we need to force Human Resources, Corporate Security, InfoSec, and others to sit at the table and figure this out? ...