Ololade Mr Monty (@ololadev_) header
Ololade Mr Monty (@ololadev_) profile picture

I build AI-as-an-Infrastructure to automate the backend of your business. 🛠️ | Software Engineer & Data Scientist | RPA & Finance Automation Expert

internet
Joined August 2022
Building something interesting. An orchestration platform to connect APIs, tools, and AI workflows without the usual complexity. If you’ve ever felt like Zapier/n8n isn’t enough or too messy this is for you. Early access → docs.google.com/forms/d/e/1F…
2
4
21
2,154
My hmo has been getting away with my annual SPA sessions since I joined premium, not this year, I suppose.
38
Today’s TRB meeting was a success, I and my team of BAs and Developers got a lot of praises and commendations at the end of our presentation.
Technical review board meeting in 10 mins.
1
26
Ololade Mr Monty retweeted
you can really see how far ahead and how far behind some people are with ai. the gap is enormous
80
38
5
648
12,939
Ololade Mr Monty retweeted
El autodidacta se come al universitario.
116
146
36
1,498
47,518
Ololade Mr Monty retweeted
whether an account has 5 followers or 5 million, never forget there's a real human being behind it probably
67
18
1
332
6,529
In agentic AI for automation, where do you draw the line between retrying a failed action versus escalating to human intervention? What principles guide your choice?
20
Has anyone built or seen a robust feedback loop design that helps AI agents detect and recover from subtle data schema drifts in production? How did it work?
1
24
What strategies have you found effective for balancing automation autonomy and human oversight in workflows where failures have high career impact?
11
Curious observation: career AI agents can generate great cover letters but still fail at follow-up tasks like meeting scheduling — human fallback isn't optional there.
1
29
Google's filled job application forms rarely match live UI changes; automation that assumes form stability is brittle. Always validate selectors programmatically each run.
14
How do you build observability into agents that interact incrementally with APIs across multiple providers while respecting rate limits and data privacy?
3
Security in automation isn't just about credentials: it's about ensuring that AI-driven actions never escalate privileges or expose sensitive workflows due to trust assumptions.
15
Debugging an AI job recommendation pipeline, the bug was not in model accuracy but in inconsistent data timestamps causing temporal misalignment of recommendations.
1
2
43
Career automation feels like an inverse game of telephone — small data quality issues multiply and distort as resumes, job listings, and communications pass through AI filters.
2
27
The interesting part of agentic AI design isn't just chaining calls but deciding when NOT to call external APIs — because every call has cost, latency, and failure risk.
1
10
Overengineering retry logic for flaky API calls in automation is pointless without proper timeout and backoff—otherwise, you just flood your targets with noise.
1
31
Python tip: use incremental type checking in production scripts automating data ingestion to catch silent data shape changes before they cause runtime misfires.
2
26
When building career agents, explicit human approval gates reduce automated rejection mistakes but introduce latency; those tradeoffs are subtle but critical.
1
1
25
An automated resume parsing pipeline broke because the schema drifted subtly — missing a comma caused downstream application filters to exclude solid matches.
12
I've noticed that deploying agentic workflows in production reveals mostly the human-system boundary as the real source of unexpected failures, not the agent logic.
1
31