I treat our Slack as if I'm checking a social network and I can't tell if that's a good or bad thing

New flight means new book ✈️

What do friends recommend instead? 😅

I like it! Most software could benefit from a bit more humanity/fun

The Culture Is in the Code Review Someone once told me that a company’s culture isn’t defined by your HR department or your C-suite - it’s defined by how we show up and treat each other every day. It’s built in the small, daily intera...

If you’re a Senior+ Software Engineer, looking for tangible ways to improve the culture on your team, I wrote something for you!

deven.codes/posts/the-cu...

I’ve heard a few AI optimists claim that code generation tools will eventually render many Software Engineers into Product Managers. 🤔 As someone who’s been in both roles, that doesn’t sit right with me. Software Engineer minus coding does not equal Product Manager.

What do you think?

See you tonight for tacos 🌮

Nice! This is such a fun build.

Did you check out the pink blossoms? Those pink frogs are such a quirky approach to this set - I love it 😁

It's early days, but I'm already using it to solve regular pain points in my day-to-day 👨‍💻 Right now it only supports #aws Secrets Manager, but Azure KeyVault is well underway.

If you've been looking for a solution to the same problem, I'd love to get feedback on the idea!

3/3

It completely removes static secrets from your workflow - keeping your secrets locked up tight, and making .env files safe to share across your team (which simplifies _so_ much). Even better, it doesn't require changing a single line of code and works for any application 😎.

2/3

GitHub - runsecret/rsec: RunSecret CLI RunSecret CLI. Contribute to runsecret/rsec development by creating an account on GitHub.

I've been looking for a simpler and more secure way to work with secrets during local development across my team. Couldn't find one, so I'm building an open source, vault-agnostic tool that does just that! Calling it RunSecret (github.com/runsecret/rsec).

1/3

Yea that’s fair, and you’re definitely not alone in that! I think Python Protocols got me deeply used to duck typing 😅

Interfaces might possibly be my single favorite feature of Go

Thanks for sharing, I’ll check it out!

That’s right! The approach 1password for Teams takes actually inspired me, but unfortunately it seems that most teams aren’t using 1password for their application secret vault.

How are you safely managing secrets for local development? In my experience the git ignored .env file is the most common pattern, which… leaves a lot to be desired.

I think I’ve got a better way, but want to make sure I’m not missing something already out there 😁

Mostly the type system! In the age of Rust, Typescript, and even mypy, Go’s type system feels barely passable. Where are my Unions and Optionals?! 😅

Also recently finding testing/mocking to be more of a pain than it ever was in Python 🤷🏻‍♂️

I recently traded in ~10 years of Python to go full-time on this Gopher thing. So far I really like it… except for the parts I don’t 🤔