iamdeedubs

Working on two routing / proxying projects.

grpc-comparator proxies between an original service, and it's replacement calculating timing and any deltas in responses. You instruct it which response attributes you care about.

edge-flipt uses/abuses Istio ext_authz to inject headers derived from flipt snapshot evaluations for downstream consumption, including VirtualService route selection.

In my experiments with SpecKit I was always left wondering "when does it merge all this specs into a single ground truth". I never got there and it felt like a huge missing step.

Now I'm left trying to define/design what a "spec" for communication between humans and coding agents would look like, to power what Birgitta called spec anchored.

One example of restarting a previously shuttered nuclear power plant to power a data center.

https://www.technologyreview.com/2024/09/26/1104516/three-mi...

Although the fine print is that it will be dumping power into the grid to be pulled out by various DCs vs powering them directly

Definitely check out https://debezium.io/. I've been using to stream data out of mongo and postgres to great effect.

You can use it with kafka-connect or a standalone process.

It would be worth taking a look at https://backstage.io/

Git based dev portal, lots of interesting modules: - service discovery - swagger / avro rendering - k8s integration (urls, cost est,)

Something like the tech radar in a large org is worth the price of admission IMHO

I feel like "a hold my beer" version of this just accepts webhooks from your artifact registry and pre-pulls new versions of running images, or maybe images that node has seen in the last X hours

Authors putted themselves as time travelers

> A human study in 2089 elderly individuals looking for possible persistence of anti-gliadin antibody

⊙.

I had written the wittiest of emails, clicked 'Send', and the button just went grey. No other signals. I hit refresh, ignored the warning about losing data, autosave drafts FTW right(?!).

And now I wait with my wit in my clipboard...

Yeah the customization options on JIRA kill me. I have an old joke I always reference when I join a new team

> When your team grows to 25 devs, its an almost certainty that at any point of the day, one of them is adjusting a JIRA workflow

- https://twitter.com/deedubs/status/880819973488340992

I'd like to have cli be a first class experience. Work offline. GUI for the pointy hairs.

I'm working on this very thing. Albeit only on AWS currently https://github.com/massivekube/massivekube

Edit: Forgot url -_-

They only show a snippet because they can't sell your eyeballs via the RSS feed. They need just need to drsw you to click onto their full site to blast you with ads.

The XPS 13 with the i7 and Max ram is a great machine. I liked it so much I made it the standard equipment for my ops team.

The kubernetes community is pouring a lot of resources into cri-o. I imagine you are going to see the kubernetes clusters that are built 'the hard way' start switching over and removing docker. It will still be used for building pushing containers for the time being.

This sounds like the Idiocracy plot summary, which is still predicting the future more accurately than I'd prefer.

http://www.imdb.com/title/tt0387808/

Very excited to see this exit preview. I really hope this gets covered under the BAA and available in a HIPAA context.

It's definitely a tricky space to navigate. If it were a private network you may be able to discourage false accusations.

I've heard of 'whisper' networks which warn people of unscrupulous behavior from colleges when they join new workplaces. It could be the realization of that concept.

That was my initial thought as well. CRI-O hits 1.0, and then this. To me, it comes across as an attempt to stay in the news. Possibly to start changing the narrative from Docker vs Kubernetes to Docker <3's Kubernetes.

My PHD says everything is a-ok sigh

If this taints your decision to purchase software you may want to reevaluate how you procure software.

We have been evaluating several tools and the vision Gitlab is demonstrating with their idea to production is near perfectly aligned.

Once https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10109 lands it'll be an amazing place to host projects and specifically monorepos that produce multiple containers.

I would assume, I couldn't even share a screen shot of my evidence to my team on slack!

k8s-the-hard-way explicitly says its not production ready. Is there a document that explains what its missing or production topology documented somewhere?

Aren't we tech people taught that sales and marketing is the cost you pay for being unoriginal?

This is nothing really. If you sign up for a New Relic trial. There sales people, hey Dom, will email you pretty consistently and then start using language like "I’m looking for a courtesy response.". I owe you nothing...

Maybe that's the disconnect here. There are plenty of small orgs using kubernetes for the ease of use and portability

While the general idea presented here is solid. It's a terrible idea to deploy your apps using the latest tag. It completely obliterates marathons ability to rollback should something go terribly wrong.

It would be better to use the CIRCLE_BUILD_NUM they expose as an ENV var to tag the image and deploy that via Marathon.

It gets symlinked to node and npm

Baby monitor - Show me a waveform of an audio stream when it goes above a certain point that I can tap to hear.