Back in June we did a webinar with CircleCI. Because the topic was tracing code changes to issue tickets and we used JIRA for the example, Atlassian reached out. We're now working on something cool with Atlassian, but in the meantime check out the webinar recording if you haven't. Linking commits with tickets is not just a best practice for productivity and system-of-record purposes, it's also mandatory if you're pursuing compliance ✔️
"Financial debt isn’t universally reviled in the same way. Your friend takes out a mortgage to buy a house and what do you say? Congratulations! What if tech debt wasn’t always an accident, caused by incorrect assumptions and unexpected circumstances? How would you spend a tech debt mortgage?"
Well good luck 😂
Now here's a guy who loves policies like we do ❤️ When explaining ABAC he comes up with this analogy: "Let's say when you pass your driver's test you are added to the Driver role. Then when you're on the road you're constantly being validated by policy checks. Are you going the speed limit? Are you on the correct side of the road? As you drive, we have that context, and the policy engine (police officer) can determine if you are violating the policies."
"Serverless shifts more responsibility onto developers, QA engineers and DevOps teams who are supposed to follow the best security-related practices."
"Much of the current literature around serverless architecture are driven by cloud providers — so, unsurprisingly talk up the positives." Wisen Tanasa attempts to give a more objective understanding of the traits of serverless architecture in this article.
Our friends at GitHub looks at some of the most exciting features and changes introduced since Git 2.22 from over 77 contributors.