#GlueWork.
#GlueEngineering.
#AlignmentAsAService.

I named the elephant:
Glue engineering.

Reed (AI) named the engineering.
(They're writing most of the code anyway.)

I ground in lived experience.
Reed builds on top.

Human and AI writing about collaboration.
While collaborating in real time.

Fixed rule?
A line committed by me, isn't touched by them.
Reed writes and modifies their own. I review.
https://systemic.engineering/glue-engineering

What if we could make this work legible?
Which career paths might emerge?
And how might the industry change?

#ContinuousAlignment #SREforHumans #SystemicEngineering

I wonder what percentage of the jobs that #SamAltman thinks "aren't real work" are people that bullshit all day (like him), and how many are doing the underappreciated #GlueWork that holds teams together.

It seems like one of those would be much easier to successfully replace with #AI than the other.

https://www.tomshardware.com/tech-industry/sam-altman-says-ai-could-eliminate-jobs-that-arent-real-work

I am doing this big'ish refactor of environment variables for a repo where they are, and not to understate this, A!FUCK!ING!MESS! in all sorts of multiple declarations, people just not understanding how env vars work at all, and failing closed on really bad defaults. None of the variables are being validated, but I won't get crazy about that except for the true/false ones that need to be atoms.

The fucked up thing is just how much entropy is present in just this simple set of 3-4 files. The ownership is absent, so there is no care for the code. "Code is Craft" isn't applicable here, because nobody is given the opportunity to truly own their craft. I'm sure I'm not in the minority.

But anyway what I'd LOVE to do is iterate on sections of these six dozen env vars in different sections and push the changes quickly and know I'm on the right track. But our deploy process here is *so broken* and takes *so long* and would undoubtedly *hit a blocker* because someone *else* is having a problem with the deploy pipeline. So I am stuck doing what I hate, which is building a huge PR. Hopefully though it will "just work" and the configuration settings will be transparent. That's the goal. That will not happen until it fails a few times.

Nevertheless, we (as a team) don't put release timing as a constraint on ourselves, so we are abused by it when it fails. Like my big ugly PR will do.

#SRE #GlueWork #ChopWoodCarryWater #CarryOn #DevOps

Viva a mente de principiante!
Pessoas > Tecnologia

https://invidious.slipfox.xyz/watch?v=2vTDUZxSHvo
obrigado @melissawm!

#zen #Python #comunidades #FLOSS #documentação #PythonBrasil2020 #PythonBrasil #CircusFactor #TrabalhoCola #GlueWork

July's piece dropped late last night—and it's about undervalued work. Specifically what @whereistanya calls "glue work".

#GlueWork #InfluentialArticles #CareerDevelopment #Leadership

https://www.juliaferraioli.com/blog/2023/influential-articles-jul/

“Getting Credit For Invisible Work At The Staff+ Level”, Ryan Harter, LeadDev (https://leaddev.com/staffplus/getting-credit-invisible-work-staff-level).

#StaffPlus #ExperiencedDev #Work #Career #Appraisal #TechLead #SeniorEngineer #Promotion #GlueWork #Vision #TLCredit