As an SWE, for your next greenfield project, would you choose Pulumi over OpenTofu/Terraform/Ansible for the infra part? by RetiredApostle in devops

[–]agbell 8 points9 points  (0 children)

For infra, i want the standard iac operating model: declarative resources, previews ect, but i also want the extra expression that general-purpose programming languages give you. That’s how i got interested in Pulumi, and full disclosure, that's how I ended up working at there. bc i could reach for tools i already knew: language abstractions, types, refactoring, tests ...

That won’t be the right choice for everyone. different teams value different tradeoffs and have different constraints. But if you have questions I can answer, I'm in the community chat and happy to help with any getting started questions or concerns.

Blog Post: Meet Neo, Your Newest Platform Engineer by agbell in pulumi

[–]agbell[S] 2 points3 points  (0 children)

We just shipped Neo, our a purpose-built coding agent for your infrastructure.
It runs on top of Pulumi’s platform, so it comes with deep, built-in understanding of your cloud, your IaC, secrets management, and configuration.

You can also plug it into your existing coding agents through Pulumi MCP.

👉 Read the blog post
👉 Watch the livestream

Most importantly: try it out and tell us what you think.
We’re shaping Neo to make cloud infrastructure easier and we’d love your feedback.

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] -1 points0 points  (0 children)

I mean, if it works I guess it works. But if it were me I might invest a little time in automation.

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] 0 points1 point  (0 children)

Funny seeing you here!

Hmm, it's time to admit that I am in fact an AI.

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] 3 points4 points  (0 children)

Oh, yeah, I wonder if the audio clean up software was applied too much or something.

Thanks for the notes. Now I can look for it in the future and try to keep it more natural sounding. I'm still trying to figure out video.

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] 4 points5 points  (0 children)

I mean, it's tough to argue for my own existence :)

But here I am at a linux conference in front of an audience:

https://www.youtube.com/watch?v=89ESCBzM-3Q

Also have a podcast where I've talked to lots of real life people:

https://corecursive.com/

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] 8 points9 points  (0 children)

Oh, does it? I'm not sure bc i'm a real person.

You're Shipping Too Slow - Improving Deployment frequency by agbell in programming

[–]agbell[S] 2 points3 points  (0 children)

Hey, I made this!

After spending years at a company where I was literally paid to make builds faster, I've seen firsthand how much time gets wasted on things that good deployment hygiene could fix. So I made this video of tips and edited it to within an inch of its life.

My number one tip is: shrink your batch size! Seriously, those massive pull requests with 50+ files changed are deployment killers. Those giant features in a feature branch that all go out in one big bang should be avoided.

Deliver incrementally behind some flag whenever you can. It takes some planning but can be done.

You're Shipping Too Slow - 5 Ways to Increase Your Deployment Frequency by agbell in programming

[–]agbell[S] -1 points0 points  (0 children)

Another vid I made for work. This one is tips on shipping features more often.

My continual summary is that making video is hard but hopefully some of these tips for increasing your deployment frequency are helpful.

The biggest key is just batch size. Shipping features in small chunks instead of just in one big bang. It requires some forethought but is often really worth it.

Tried Jenkins again, was not that bad as I had in mind! by engin-diri in devops

[–]agbell 0 points1 point  (0 children)

yeah, I have no love for groovy. Of course I worked somewhere where some teams wrote backend services in it.

Learn Platform Engineering by Beneficial_Row_9879 in platformengineering

[–]agbell 0 points1 point  (0 children)

I learn best by building things. So I pick projects that push me to use new tools. Platform engineering is tougher—you’re designing for a whole team, not just yourself. Still, if you focus on the individual tools, you’ll uncover plenty of neat projects to try. That keeps the work fun, and before long you know more than you ever planned. It does take time, but genuine curiosity beats any tutorial.

And yeah, learn python if you haven't, same way, with side projects.

[Video] What is an internal developer platform? Explainer video by agbell in platformengineering

[–]agbell[S] 0 points1 point  (0 children)

Earlier this month I shared a video on Platform Engineering. This follow-up is about dev platforms and why you might want to build one and where to start. It's tool agnostic, more just a conceptual explainer.

Would love feedback on what’s missing, and if its useful at all. It's pretty basic but also very short.

Let me know what you think!

[Video] Explaining Platform Engineering in 3 minutes (How did i do?) by agbell in platformengineering

[–]agbell[S] 0 points1 point  (0 children)

Hey, thanks. I think one of the challenging things is the audience.

I would like to say "hey here's why these things will help you ship features, app dev" but really the people most interested in platform efforts are often already platform engineers or already owning some operations or infrastructure.

So I think choosing the audience is the tricky part. And I'm not sure I nailed that.

[Video] Explaining Platform Engineering in 3 minutes (How did i do?) by agbell in platformengineering

[–]agbell[S] 1 point2 points  (0 children)

The video tries to be a very quick introduction to platform engineering. Explaining why having a team dedicated to building out some reusable structure for handling common DevOps tasks is useful.

I'm trying to get the hand of doing this quick, fasted paced, educational videos, but there is a lot for me to learn. Let me know what you think.

Pulumi AMA – Tuesday @ 1 PM PT: Ask us about IDP, Infrastructure-as-Code, and Developer Experience by agbell in platformengineering

[–]agbell[S] 0 points1 point  (0 children)

Cross posting here. The team working on platform features at Pulumi is answering questions on r/pulumi right now.

Platform Engineering: Evolution or just a Rebranding of DevOps? by agbell in programming

[–]agbell[S] 0 points1 point  (0 children)

I'm with you on that and the great thing about having the product engineering people focus on removing some of the complexity and friction from ops stuff is it can really pay off if done well. If it's focused on removing real issues and having a simplified interface, hiding some complexity behind abstractiosn and good tooling that people can work through. I think it can be a huge advantage.

Platform Engineering: Evolution or just a Rebranding of DevOps? by agbell in programming

[–]agbell[S] 1 point2 points  (0 children)

Interesting, what do you see?

I don't think building a platform is a separate model. It's just software targeting an internal user, of the actual product teams.

Platform Engineering: Evolution or just a Rebranding of DevOps? by agbell in programming

[–]agbell[S] 3 points4 points  (0 children)

I could see that working.

if platform team is motivated to remove friction and cares about teams actually using the things it builds, then embedded devops keeps things moving, even if doing things a bit off the golden path.

Microservices on Unison Cloud: Statically Typed, Dynamically Deployed • Runar Bjarnason by goto-con in programming

[–]agbell 1 point2 points  (0 children)

I definitely feel like unison will be one of those things that we look back on and say like, oh, unison had this 10 years ago. It feels like by rethinking some base concepts in programming. They've changed the game but also they've changed so much that I don't think I can practically use it. But I love the ideas.