Let's work on a thread for Dotnet beginners and enthusiasts? Let's share links/resources that has helped us in our journey? What advise do you have for anyone planning to start their Dotnet journey?
I'll update from time to time. :)
I've gone through all the suggestions and learned a couple of things, so here's my takeaway strategy:
The plan:
1. Buy VPS from Hetzner (I have no idea 😂)
2. Install/connect it to Coolify (I have no idea)
3. Deploy my Next.js app (frontend + backend) (I have no idea)
4. Deploy PostgreSQL → migrate data from Neon (I'm good at this 😃)
5. Deploy Redis → replace Upstash (I have no idea)
6. Deploy ClickHouse → replace ClickHouse Cloud (I have no idea)
7. Configure domains/SSL (I'm good at this)
8. Put Cloudflare in front (I'm good at this)
9. Configure off-server automated backups (I have no idea)
10. Set up monitoring/alerts (I have no idea)
11. Test restoring everything from backup (I have no idea)
12. Run the new setup alongside my current infrastructure (I'm good at this)
13. Switch traffic only after I'm confident (I'm good at this)
So basically, I know what I want to build. I just apparently need to learn how to run the thing 😂
@DaveyHert Oh so sorry for the loss.. for the question, the problem is most Nigerian hospitals are not emergency ready
They are mostly there for malaria typhoid and pregnancies…
If you want to make money with AI:
• Don't vibe code a SaaS
• Don't start a personal brand
• Don't sell AI automations to businesses
Start an agency and let AI help you do the work.
Here's exactly how it works:
i'm sorry, Claude can WHAT?
it can take your website link, find people who need your product, email them and book the calls?
since when?? i've been doing this by hand for a YEAR.
ok. testing it: $30 free 👇
https://t.co/VPalOJjjU7
If you’re building or integrating Fintech payment systems, bookmark this thread.
I’m covering 18 real-world edge cases that quietly destroy authorizations, settlements, refunds, ledgers, and customer trust, plus the practical, production-hardened solutions that actually work.
These are the failures that only appear under real load, real networks, and real money. Lessons hard-earned from systems that move millions daily.
Let’s dive in.
GITHUB JUST CREATED AN OFFICIAL CERTIFICATION FOR THE MOST IN-DEMAND DEVELOPER ROLE OF 2026.
It is called Agentic AI Developer.
GH-600.
And it is the first formal signal that running AI agent teams is now a recognized engineering discipline with a credential behind it.
Not a prompt engineer.
Not a vibe coder.
An Agentic AI Developer.
The person who operates, supervises, and integrates AI agents across the entire software development lifecycle.
The person who knows where agents fail in production.
The person who understands how to build autonomous workflows that do not introduce catastrophic failure modes into CI/CD pipelines.
The person every engineering team is going to need and almost none of them have right now.
GitHub certifying this role changes the hiring conversation permanently.
Before GH-600: "Do you work with AI agents?" is an interview question with no standard answer.
After GH-600: the credential tells the hiring manager exactly what you know and what you can do before the interview starts.
The engineers who get certified in the first wave of GH-600 will have a credential for a role that has more demand than supply for the next 3 to 5 years.
The engineers who wait until it is mainstream will be competing with everyone who moved first.
If you are already working with GitHub Copilot or building agent-driven workflows you are already doing this job.
GH-600 is how you prove it.
Bookmark this.
Follow @cyrilXBT for every AI certification worth your time the moment it drops.
@doll_lenses@Morris_Monye The way I see it. This is the future. More like people who prolly believed that learning to use a computer in the past would make them loose something. So question is, what would you gain from totally leveraging AI?
Most engineers index their entire table.
Then writes slow down. Index size balloons.
Quick PostgreSQL trick. Partial indexes:
CREATE INDEX idx_orders_pending
ON orders(created_at)
WHERE status = 'pending';
Only covers rows you actually query. Smaller. Faster. Cheaper.
@_ctordev DDIA (Designing Data Intensive Applications) first.
Then real eng blogs. Stripe, Cloudflare, Discord.
The way they explain tradeoffs teaches you more than any course.
Stop burning tokens on Claude Code.
Use this instead 👇
A free GitHub repo (80K⭐) that turns your CLI into a high-performance AI coding system.
Link → https://t.co/ItSXlxdPax
Why it’s different:
→ Token optimization
Smart model selection + lean prompts = lower cost
→ Memory persistence
Auto-save/load context across sessions
(No more losing the thread)
→ Continuous learning
Turns your past work into reusable skills
→ Verification loops
Built-in evals to make sure code actually works
→ Subagent orchestration
Handles large codebases with iterative retrieval
Most people think Claude struggles with complex repos.
It doesn’t.
They’re just not using the right setup.
This fixes that.
Bookmark this for your AI stack. ♻️
#AI #Claude #AIAgents #LLM #GenAI #DevTools