Software Delivered the Same Way Every Time Before security enters the picture, SDLC exists to solve a simpler problem: making software delivery repeatable. A team that builds features ad hoc, without a defined sequence of requirements, design, coding, testing, and release, ends up with wildly inconsistent outcomes — some releases solid, others full of regressions, […]
I wrote some time ago about “How to create security user stories” and I received in the meanwhile a lot of good feedback and questions about it. For these reasons, I decided that it is time to write again on the topic, this time with focus on two importat groups in any software developer team: […]
We started to talk about the SOC2 Type 2 certification and I feel that we neglected it a bit. I wrote a bit about SDLC, Secure SDLC in particular, but now it is time to bring them together. SOC 2 Type 2 and Secure SDLC — the big picture SOC 2 Type 2 evaluates whether […]
Evaluating Python library safety comes down to a few key dimensions: Check the source and provenance PyPI page: Look at download counts, release history, and whether the project links to a real GitHub/GitLab repo. Author/org reputation: Libraries maintained by well-known companies (Google, Meta, Microsoft, Palantir) or established OSS orgs carry more trust than anonymous accounts. […]
What is the Cyber Resilience Act – CRA The Cyber Resilience Act is the first European regulation to set a mandatory minimum level of cyber security for all connected products available on the EU market – something that did not exist before. The CRA is a regulation from the European Union — formally Regulation (EU) 2024/2847 […]
This is a a developer focused guide in three parts to evolving code, architecture, and processes with the purpose of turning a raw concept into a usable product. This process is one of the hardest parts of software development. Teams often jump into implementation too early, or they build something polished before testing whether the […]
We continue the series of 3 articles with the second one, about the Minimum Viable Product (MVP). Here is the first article in the series, From Idea to Proof of Concept to MVP: The Idea stage (1/3) and the second article, the From Idea to Proof of Concept to MVP: The POC stage (2/3) . 3. […]
We continue the series of 3 articles with the second one, about the Proof of Concept (POC). Here is the first article in the series, From Idea to Proof of Concept to MVP: The Idea stage (1/3) . 2. The Proof of Concept (POC) The POC is where the team tests a specific risky assumption […]
This is a a developer focused guide in three parts to evolving code, architecture, and processes with the purpose of turning a raw concept into a usable product. This process is one of the hardest parts of software development. Teams often jump into implementation too early, or they build something polished before testing whether the […]
Click below for the podcast version (AI generated): Guide for delivering frequently software features that matter: the three Pillars of successful frequent delivery If you’re a software engineer older than 30 years, then you definitely have worked following a non-agile methodology. Those methodologies are based on a fixed structure, a lot of planning, and hope […]
You must be logged in to post a comment.