Jason Parrott

[Thorsten Ball @thorstenball]

One of the most unteachable, you-have-to-experience-it-yourself lessons:

You can just delete your backlog or your TODO list and nothing bad will happen. You won't forget the important things. They will resurface.

[Gergely Orosz @GergelyOrosz]

Even easier to get promoted putting out a fire not started by you. But it leads to poor perf reviews/promotions to take on conflicts when there is no visible fire.

Which leads to a perverse incentive to do nothing when you see a small fire start. Wait till it gets bigger to act.

[Mitchell Hashimoto @mitchellh]

@jessfraz For real. Negativity around people shipping is so exhausting. Never good enough, not what I expected, you should've done X instead, Y is still garbage, I prefer Z. Ship something better yourself or shut the fuck up.

[Vic 🌮 @VicVijayakumar]

[private message on work slack]

friend: hey buddy how do i <do thing>, i can't find it in your team's docs and i feel super dumb

me: hey buddy! it doesn't exist. please re-ask this question in our public help channel so whoever is on-call can answer you.

[public help channel]

friend: hi team, our service needs to <do thing> because of <legit reasons>. we're wondering what the right way to do it is. thanks!

me (also the on-call): hello, this is not possible at the moment, but we'll add a ticket for it and prioritize it in our upcoming sprint.

[Thorsten Ball @thorstenball]

Sometimes I remember that "Scaled Agile For Enterprises (SAFe)" exists and I google the diagram and then I just marvel that this exists and that people look at this diagram and think "yup let's do it" and then they spend years (!) trying to implement it.

And then I stop myself.

[Cory House @housecor]

I review a LOT of React code every day. Half my job is repeatedly saying two things:

1. "This state isn't necessary. The values can be derived from other state/props."

2. "This useEffect isn't necessary. The values can be derived on each render instead."

[Bryan Cantrill @bcantrill]

In preparation for tonight's discussion, we have made a couple of relevant RFDs public:
https://t.co/Mxty2gkhuq https://t.co/XIOcF00Cci
https://t.co/EijcEdvAuc
https://t.co/EiMmnPKhzF

Join us live at the top of the hour!

[Cory House @housecor]

Doing a code review without running the code is like doing a quality check blindfolded.

🚩I have to use my imagination.
🚩I have to run the code in my head.
🚩I have to envision what the UX might be.

This severely limits my effectiveness, and makes my job as a reviewer harder.

The solution is simple: I run pull requests as part of my review.

[Jack @Jac5Connor]

@rauchg Joel Spolsky talks a lot about how easy, fast runtimes is a quality of life issues for devs, and helps attract top talent.

[Corey Quinn @QuinnyPig]

Okay, I've been dancing around it for years--it's time to call it:

There's no economic story around using the cloud for steady-state HPC workloads. It's not even close to cost competitive.

[Guillermo Rauch @rauchg]

If you’re building a better product with fewer features, be patient.

“Multiple studies have shown that before using a product, people judge its quality based on the number of features it has. It's only after using the product that they realize the usability issues too many features create”

https://t.co/L0ug5mEz0r

[dax @thdxr]

here’s an example of how corporate leadership values get things wrong

if you ask managers what they do when a conflict between two people occurs they’ll have roughly the same answer

they’ll talk about “getting them both in a room” and “mediating the conversation” and getting it to a place where both acknowledge mistakes

everyone wins a little, everyone loses a little, and manager can pat themself on the back for diffusing the situation

the problem is this is the lazy, easy thing to do

in many conflicts, on the surface, both actors will be acting outside the range of what’s acceptable

but if you dig deeper there is often a clear antagonist - often times it’s even the person coming across more reasonably

dragging the other person who was pushed past their limit into a mediation session is not good for long term morale. they’re probably even ashamed of the conflict and will self-flagellate

being a good leader means sniffing out where the problem is, explicitly taking a side and snuffing out the bad behavior aggressively

it means someone will be mad at you, it means you’ll have to take a bet, it means you’ll come across unreasonable to people watching from the sideline

and that’s what being a leader takes

[J☁e Duffy @funcOfJoe]

We used IaC to get rid of ClickOps.

So that we can build custom platforms using IaC that enable ClickOps.

… 🤔

[Darren Shepherd @ibuildthecloud]

It is so difficult to create cost effective k8s clusters and it's so difficult to create multi-tenant k8s clusters. No wonder AWS loves EKS. It must print EC2 dollars.

[Mitchell Hashimoto @mitchellh]

Fucking Yikes. This branding is... unfortunate. Don't get me wrong, Copilot is great, but there's still so much room for improvement on the "Social Coding" platform (remember when that was GitHub's tagline?). The homepage now is "AI-Driven Developer Platform". Ah, fuck.

[buildpacks_io @buildpacks_io]

✈️ We're heading to Chi-town next week and can't wait to see everyone at #KubeCon!

We have an in-person project meeting, a kiosk in the project pavilion, and a maintainer track session.

All the details on when/where to join us can be found in this blog👇 https://t.co/C9eM8I2PS5

[Lewis Menelaws @LewisMenelaws]

GPT-4 is getting smarter

[tim is different now🥰 @elchefe]

When people just accept that all platform engineering is essentially trying to rebuild heroku, a lot of the allure goes away, and it should.

[Tom Barber 🐀 @torbar]

Until the sun makes its way either upstairs or downstairs, it gets to act as a side table. It really ties the room together

[Matt Simmons 🚀🛰️ @standaloneSA]

They really under-sell the major benefit of Kubernetes, which is the inexhaustible number of things to try when it's broken.