My technical background helped me transition easily to AI automation and ops
Here’s a demo I built for a Canadian agency. Internal Agency Dashboard that tracks:
• Leads
• Meetings
• Close Rate
• Churn, etc.
Also generates internal updates daily. Built with airtable and n8n.
Over 50% of media buying agencies struggle with bad ops because their data is spread across spreadsheets, Slack messages, and ad platforms
This chaos wastes hours
Built a simple Airtable interface to centralize spend, revenue, leads, ROAS, and campaign performance in one place
An airtable MVP that I built a month ago. This one works specifically for marketing agencies that work with service-based businesses.
It helps to reduce no-shows and improve personalized follow-ups.
The automation layer was simple so I just skipped n8n and used Make instead.
Deployed this smol tool a few days ago.
It's a wallet tracker that tracks and updates eth balances every five minutes or when queried.
This is V1. More chains and updates to come.
Check it out https://t.co/xSZcBfj9fk
You shouldn't limit yourself to just RESTful APIs.
There's a simpler and powerful type of API most beginners ignore.
I recently worked with Alchemy's Ethereum node API, and it completely shifted how I think about API design.
Instead of the usual RESTful approach, Alchemy uses JSON-RPC which is a protocol that's both simpler and surprisingly powerful.
Here's how it works:
1️⃣ Send a JSON object to a single endpoint.
2️⃣ Specify the method you want (like eth_getBalance).
3️⃣ Pass your parameters (wallet address, block number, etc.).
4️⃣ Get back a clean, structured JSON response.
That's it. One endpoint. Multiple methods.
❌No /users, /posts, or /comments routes.
❌No juggling between GET, POST, PUT, and DELETE.
✅ Just one URL with different methods behind it.
This experience taught me something important:
→ REST isn't the only way to build APIs
→ Sometimes simpler is better than "standard"
→ Different problems need different solutions
If you're learning backend development or working with blockchain APIs, JSON-RPC is worth exploring. It's especially common in Web3, where you'll find it in Ethereum nodes, Bitcoin Core, and many other blockchain implementations.
Not every API needs to be RESTful and that's a good thing.
Taking on tough data engineering and backend development projects have taught me to think differently.
I've been hardening the ingestion layer of my Ethereum wallet balance API, and honestly, it's taught me more about building real systems than any tutorial ever could.
The problem is simple: external APIs fail. Networks timeout. Rate limits hit. Providers go down. If you don't plan for this, your entire pipeline just... crashes.
Here's what I added:
-> Request Timeouts (10 second hard limit): Without this, a single hanging request blocks everything. Now if Alchemy doesn't respond in 10 seconds, we cut it loose and move on.
-> Exponential Backoff Retries (3 attempts: 2s, 4s, 8s): Most network issues are temporary. Instead of giving up immediately, we wait progressively longer between retries. This handles like 90% of transient failures without hammering the API.
-> Crash Isolation (try/catch per wallet): One bad wallet address shouldn't nuke the entire poller. Each wallet gets processed independently. If one fails, the other 99 keep running.
-> Graceful Degradation: When all retries fail, we log it and keep going. The pipeline stays alive. We don't store corrupted data. The system degrades gracefully instead of just dying.
-> Structured Logging: Every failure gets logged with full context: which wallet, which attempt, what went wrong. When things break in production (and they will), I need to actually know why.
The mental shift from "does it work?" to "how does it fail?" completely changed how I write code.
Still building.
@Invaluablemoi Did you even read the report?
20k videos on a porn site and now you’re claiming it’s in an online community.
Instead of focusing on the real issue you’re the one inflating numbers just to deflect and fit your feminist agenda. Keep playing
@bodybyzedd But that’s literally the definition of God. There has to be a starting point for creation and that point is God. What would you say is the starting point?
As someone who studied mathematics, I never just believe things because I’m told to. I need proof.
While living in sin, I set out to prove that God didn’t exist so that I could keep serving myself. I researched deeply and I couldn’t keep denying the evidence pointing towards the existence of God and the personhood of Jesus Christ.
If you really need evidence, you can find it especially with historical proof of the life of Jesus, His death and His resurrection. It’s all recorded history beyond the Bible itself.
If you believe with evidence, you understand God for yourself and your faith becomes a lot stronger.