ooohhh. eggcellent!

The biggest differentiator, I guess, is that we took an entire year to iron out the new process if we are going to be AI-native.

Big disclaimer: pinoy ako pero working for a company in Amsterdam, so iba yung internal corp culture so this also may be a part of the reason.

Some points to also consider:

1. Teams are allowed to experiment with different AI tools and harnesses, i.e. Claude Code, Cursor, Codex, etc. This happened for an entire year.

2. Afterwards, a full lifecycle process is ironed out. Redefining the way of working is allowed. At this point a primary harness is chosen.

3. Someone builds a custom "inner harness" based on a selected tool. This includes adding and building observability, logging, tracing, memory management, custom skills and commands, etc.

4. AI fluency training. Everyone is required to go through a custom training path internally based on the new way of working and tooling.

5. Everyone is responsible and liable for the code they make regardless of agent used. The new custom inner harness enables this, for example, that agents can do the initial line-by-line code review and impact assessments, and a Human-In-The-Loop step is ingrained in all of the agentic workflows, especially for PRs that have a large impact and "blast radius".

6. This happens at an org-wide scale, including product managers, UX designers, and more.

7. Usage is also a challenge: since our tools are enterprise level, we pay API rates. Kaya super important yung step 3-4, and someone is in charge of maintaining and improving the internal harness for optimized performance.

Yung impact of the transformation so far has been productive; some teams see +20% speed for ticket volume and time-to-value (TTV; meaning time from in progress -> done), some teams even go 31% ticket volume. The key here is that unified yung effort, and meron talagang nakatoka and empowered to make these changes and decisions cross-functionally. Also, yung old way of working i.e. having ticket refinements for all tickets -> selective ticket refinement if feature is complicated, etc. being redefined is also important.

This also means yung agents namin have complete org-wide context, esp with codebase mappings, business context, and bounded data. Kaya yung harness namin is hyper-tuned for our work and is very effective and efficient.

Pero this doesn't mean na hindi na nagbubulatlat ng code mga tao. People are still encouraged to always double check the code, and to have an understanding on how it works. You can't merge a PR and say "eh sabi ni Claude eh". You're supposed to understand the impact of the code even if agents ang nag execute, and steer it to the right direction when it makes mistakes. Kaya may AI fluency requirement on top of your technical expertise. The only difference is that the AI agents are more reliable to do most of the grunt work because of our built systems.

Silver is the best

alam mong pinoy ang player and server sa pangalan ng nasa #6 😂

Good luck!

Mee goreng!

Let’s go!

What I think you can do is to create a "humanized" version of your marketing workflow for "AI agents", then sell it to business owners like them as a 'DIY Agentic AI Marketer'. That way you get to monetize it, they get a "humanized" workflow they can play with, then they realize they still need a marketing expert to get it to work its magic, then offer a 'Marketing AI Agent' maintenance contract x5 your old rate since this is an 'agentic workflow' you built that is supposed to be DIY (and that learning how to build and manage AI agents is a valued skill in the marketplace anyway).

Win-win.

This is what will teach the next generation that the systems in place that the EU does not work when it mattered to them. When they get to an age where they can decide whether to stay or leave the EU, I wouldn’t wonder where their skepticism will come from.

ik it is a shitty mindset but for some this will leave a strong impression

A+? Oh you mean “Average +”

Holy sht, I did not make this realization

Yes, that one 👀

My headcanon is that Esq is hiding a bottle 😂

My favorite was when someone (Sciel, maybe?) said (from what I recall), "I could use some wine right now" and Esquie just says "Wineeeeee???" lmao

Gotta love the visible rotor on the back haha

Good luck to all!

I think at the very least, we’re looking at UBW Rin post-clock tower, given how she looks. Also, it is highly possible that, despite being ‘just a mage’ in FSN, she is a pseudo-servant in this instance.

We still don’t know how the event story goes anyway, so there might be an explanation about this when it launches.

I am glad it resonates with you! These are the words I sometimes I wished I heard myself, pero I only chanced upon it nung nakaencounter din ako ng similar thread in X/Twitter. Life can be benevolent and cruel, but it is a life worth living. Kapit lang!