I recently read an interesting article about a neural network that, instead of artificial neurons, has logic gates.

https://google-research.github.io/self-organising-systems/difflogic-ca/?hn

The paper described its neural network as “sparse”, and this made me want to ask ChatGPT “Why does this paper describe logic-gate networks as sparse?”

I didn’t realize this really important fact:

In “Deep Neural Networks”, they’re called “Deep” because it’s a 2D matrix of nodes “neurons” that are FULLY CONNECTED to every single output in the previous layer.

Okay!!!

TL:DR; Don’t pay for a domain name. Don’t pay for hosting. It’ll teach you stuff but is annoying to maintain!

Use GitHub Pages. Or .carrd.co. It’s free. It’s simple. It works. It doesn’t cost $144/year. The build system is simple. It’s hard to mess up. And you can literally copy my site, or someone else’s.

I’ve gone through many different iterations of this:

2019: Custom HTML.
2020: ^^
2021: Hugo + GitHub Pages.
2022: Hugo with a custom theme.
2023: ReactJS custom site.
2024: ^^
2025: Back to Hugo + GitHub Pages.

Brainstorming on CICD Pipeline Design

What are the questions that I should be asking myself when I’m thinking about how to automate security in a CICD pipeline?

What about a CICD pipeline without thinking about security?

• What should CICD Pipelines do?
• What shouldn’t CICD Pipelines do?

These feel too general. These might be valuable to explore, but I think that making them more specific will be better.

The questions that I ask myself are important because they will determine the architecture of the pipeline. I feel like I’m starting to understand what 2 of my coworkers, Gil and Vishal, are talking about. If I start trying to design a CICD pipeline with an existing piece of automation, it’s not a good starting point. But if I start with the right principles in mind, building good ideas becomes easier.

Intro

I’m thinking about what the best way is to manage vulnerability scanning in the SDLC.

Sitting down and really thinking about this is a culmination of talking with coworkers about this for a while, and stuff that’s been happening at work.

Specifically, if the goal is to:

1. Provide developers vulnerability data as fast as possible
2. Provide developers vulnerability data in a FULLY automated manner

(Maybe as a bonus, we can also)