Software factories. Evals. Code Quality. Jev.
These were some of the topics covered at the @aiDotEngineer NYC conference last month. The conference was directed mainly at the engineers and builders who are trying things on the edge.
1
1
48
๐๐ฒ ๐ญ๐๐ค๐๐๐ฐ๐๐ฒ: the C-suite are simply dealing with a different set of problems than the engineers, unsurprisingly. Cost control, change management, risk.
1
3
๐โ๐ ๐๐๐ค ๐คโ๐ ๐๐๐ ๐ก๐๐๐๐ ๐๐๐ก๐ ๐๐๐ก๐ค๐๐๐ ๐๐๐๐๐ก ๐๐๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐ ๐๐๐ ๐กโ๐ ๐๐๐-๐ค๐๐๐ ๐๐๐๐๐๐๐๐ ๐ค๐๐๐ ๐ค๐๐ ๐กโ๐ ๐๐๐ฆ.
3
๐ซ Customermaxxing > Tokenmaxxing. It's the unsexy compliance/security processes that gets AI to production faster at banks. 3 pillars are CVE remedation, disaster recovery, and zero leakage. Grateful for the opportunity #AIEngineerNY @aiDotEngineer @swyx youtube.com/watch?v=Bz1HFxQAโฆ
Last time I saw myself in the paper was when my middle school jazz band played at our local senior citizens center. Coolest conference swag @aiDotEngineer @swyx @karasilverman
๐ฅ Current thinking, skills, and open questions for capturing relevant customer context into a wiki ๐งต
1
152
On the engineering side, we've already set up a system to automatically update the README on our repos with mermaid diagrams and architecture based on latest commits. I think something like this should exist for customer context, but a repo doesn't feel like the right substrate.
1
13
Experimenting with OpenWiki from @LangChain and DeekWiki from @cognition to see how these frameworks may be able to help.
14
These are the typical places where bugs, feature requests, and nuances about the customer's k8 cluster and deployment are discussed. But stepping back a bit, GItHub PRs and Claude sessions where our engineers and PMs are investigating customer issues, drafting specs, and making
1
9


