💭 Releases · stackrox/kube-linter

Waylon Walker Author

June 24, 2024 1 min read

GitHub - stackrox/kube-linter: KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.

KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices. - stackrox/kube-linter

GitHub · github.com

A linter for linting kubernetes manifests and help charts.

Note

This post is a thought. It’s a short note that I make about someone else’s content online #thoughts

Latest Thoughts #

💭 A love letter to Pi | Lucas Meijer

www.youtube.com

I hate how he called out terminal user interfaces as shit… then proved web interfaces to be superior. Damn him. I love working from my terminal, but having ai prove itself through html reports including video, image, metrics, charts, and text is goated. Rethinking yourself has the bottleneck not the orchestrator feels real. Validating the work is hard, theres a shift right now and everyone is trying to figure it out. Lucas’s technique is a little bit of be lazy and tell it to prove itself to you, so as you juggle your 15 agents you have a nice report to read.

💭 How Claude Code’s Creator Starts EVERY Project - YouTube

www.youtube.com

This is a really good guide, with quite a few good nuggets. I need to try deleting my AGENTS.md and rebuilding it from scratch more often. I liked how he talked about having agents prove their work and tell them up front how they will be judged. What I didn’t care for so much was the feeling that a lot of the rules go in markdown, thats not a rule, thats a suggestion. Rules should be deterministic. They should be tests and linters that ensure they are followed. Suggestions are good, but dont trust the agents to always follow them. And don’t trust that they wont change your rules, keep them honest.

💭 POV: Growing up as a Millennial be like 🤣 AC:@mikemancusi #mil...

www.youtube.com

Feeling this today, feels like everything continues to get worse. Trying to be more positive, and its hard.

💭 Write It First, Then Let AI Drive - Kenneth Reitz

kennethreitz.org

Interesting take by Kenneth Reitz. Not quite sure how I feel about it anymore. It kinda hurts, but I’m not sure if code aesthetics matter as much as the product anymore. I cared when I was the one editing, but at this point I’m not doing a lot of edits by hand. Do these aesthetics affect the final products that users use, Not sure. AI makes me sad.

💭 I am slowly coming around to AI assisted programming.

x.com

If agents make prime a bit faster, what does that mean for the rest of us mortals?

Recent Pings #

Ping 49 #

What's going to happen to all of our software when Anthropic Mythos finds all of the 0 day vulnerabilities? Will everything depending on the bugs break? Will it be possible to fix them cleanly? Will we all get pwnd when the bad actors get access to them before everything is patched? Will LTS Operating Systems Die?

Ping 48 #

What is this job anymore #

The job of writing code is dying, models are getting better, the average person will have their average features implemented in average ways with no effort by agents, the writing is on the wall. We are still trying to review most of the critical code, this is slowing us down, is it really stopping any bugs or giving us any more familiarity with the product, marginally.

The time is now to grease up your UAT, testing, deployment pipelines. Dont let agents delete entire regions. Review your backup and restore strategy, you do have a DR plan right?

Things are changing fast, the best of us are still better than the clankers. Most of us have more context than the clankers. Most of us have more intuition of what and where to implement fixes. Context windows and memory will be solved problems. Your DR plan, UAT, testinng and QA environments will not come for free, you need to make them, and deeply integrate them into your processes.

Ping 47 #

The year of the supply chain attacks #

I think I'm starting to understand my role as a platform developer in 2026.

least priveleged access
default deny + explicit allow
understand your blast radius
GREASED creds rotate process
PIN EVERYTHING
keep packages up to date
but not too up to date, use dependency cooldowns

`j`	Scroll down
`k`	Scroll up
`g` `g`	Scroll to top
`Shift` `G`	Scroll to bottom
`d`	Half-page down
`u`	Half-page up

`j` / `↓`	Next post (in feeds)
`k` / `↑`	Previous post (in feeds)
`Enter` / `o`	Open highlighted post
`Shift` `O`	Open in new tab
`g` `h`	Go to home
`g` `s`	Focus search
`[`	Previous page
`]`	Next page
`s`	Toggle simple/rich feed view

`/`	Focus search input
`⌘CtrlK`	Focus search (alternative)
`y` `y`	Copy URL to clipboard
`?`	Show this help
`Esc`	Close / clear highlight