Angehefteter Tweet
Aplus.
1.7K posts
Aplus. retweetet
Been working on this product for a while now and I think it’s time to let y’all know
Haildesk.
Haildesk is an AI powered customer support platform that thinks like your best employee.
Add a chat widget to any website with a single script tag.
English
English
Same with Claude o. Them tell me make I wait till 9pm bruh😭
Sticking with codex abeg.
Andrew Dev@just_andydev
I paid 28k for antigravity and few minutes later I hit the limit. It's a useless app, I'm back to github copilot
English
And my boy @craneoh4 cooked with this o. Anyways, Higher Higher.
Gianluca Minoprio@gminoprio
Never imagined there was going to be a huge PMF of digital money spraying in Nigeria 😆
English
Damn what a ride it has been
I can't believe SportyClaw AI has crossed 520+ users ✅🥳
We have 900+ people in the community as well
I have had to increase compute to handle the huge load of requests coming from users on a daily
Tbh I never expected this growth and I'm growing with it
I have had to learn so many new things to make sure my users are satisfied. 😅
My eyes are always glued to server logs 😭 ( going to install sentry soon )
But it's is fun working on this beauty of a product, even tho I haven't had enough sleep this past 2 weeks
Global reach soon 🚀
More updates are coming !!!
victory@nnvictory001
On the bright side , SportyClaw AI has just crossed 120,000 naira in revenue just after 2 days of adding a paywall 🥹 Thank God and thank you so much to everyone for their support and encouragement (and the FUD) To think I didn't even know this could have made it this far 😅 It's all happening so fast Job's not done , up only from here 🚀 Alot of features are coming for SportyClaw AI. More updates soon
English
@nnvictory001 I think it would be nice to always include a "what this means for you as a user", to your tweets like this one since many of your users are non-technical.
English
Made a significant update to the research engine this past days . It has become more factual and most especially faster ⚡️
Implemented queues and batching of requests to ensure optimal performance and load balancing
Added an intent classifier yesterday which makes it easy to offload too much system prompt context from the model for smarter responses
I'm always working to make this ready for the global stage
English
Hit some crazy circular dependency bug today
And didn’t even realize it until front end team reported
Finally fixed after 3 hours
Kashamadupe
English
Aplus. retweetet
This is the best time to be a competent and knowledgeable software engineer.
While everyone else is vibe coding, study the fundamentals and read books.
1. Designing Data Intensive Applications
2. Operating Systems: Three Easy Pieces
3. A Philosophy of Software Design
4. System Design Interview: An Insider‘s Guide
English
@0xaplus In which planet does ELEVEN have five letters? On earth, it is six.
English
If you pick any word and count the number of letters, repeat, you'll always end up with 4.
Example:
MATHEMATICS(11)- ELEVEN(5) - FIVE(4) - 4.
Lazzyyyyyy@em_Lazzy
Does anyone have any random fun facts about a very niche subject. I'm bored and love learning random things
English
Aplus. retweetet
built an offline-first system recently where the app keeps working even with zero internet.
instead of relying on APIs for every action, I used:
SQLite (local) → PowerSync → PostgreSQL (cloud)
So the app writes locally, syncs automatically, and dashboards update in realtime.
no custom sync logic. No data loss. no downtime.
this architecture completely changed how I think about reliability.
English
Aplus. retweetet
Funfact, the AI(.)com former owner bought it because it was his initials.😂
Xeusthegreat (♟,♟)@SamuelXeus
AI(.)com was worth $100 in 1993. It sold for $70M in 2025 Danbao(.)ton was worth about $500 in 2020. It just sold for $2.2M If you believe in the future of anything, start making moves now. You can buy the next billion-dollar company’s domain or TG name for cheap and sell it for millions later As you were.❤️🦅
English
Aplus. retweetet
Do not use UUID as your primary key by default, use BIGINT identity for OLTP (smaller indexes, faster joins) and add UUID only when you need cross-system uniqueness.
Do not use OFFSET pagination on big tables, use keyset pagination (WHERE id > last_id ORDER BY id LIMIT n) with a stable index.
Do not use SELECT * in hot paths, use narrow selects (only columns you need) + cover with the right index.
Do not use COUNT(*) on a giant table for UX counters, use approx counts / cached counters / rollups depending on accuracy needs.
Do not use JSONB for everything, use proper relational columns for fields you filter/sort on, keep JSONB for truly flexible metadata.
Do not use EAV schemas (“key/value tables”) for core entities, use normal forms + migrations (EAV becomes un-indexable pain).
Do not use “one index per query” guesswork, use EXPLAIN (ANALYZE, BUFFERS) and index what your workload actually does.
Do not use big multi-table joins for dashboards, use ETL/CDC into OLAP (ClickHouse/Druid/BigQuery) and query there.
Do not use sync writes to multiple DBs, use outbox pattern + CDC so data movement is replayable and consistent.
Do not use triggers for business logic, use application-level writes (triggers become invisible dependencies and debugging hell).
Do not use serializable isolation everywhere, use the lowest isolation that meets correctness + explicit locks only where needed.
Do not use long transactions, use short transactions (long txns = bloat, locks, vacuum issues, replica lag).
Do not use “DB is slow, add replicas” first, use query shaping + indexes + connection pool sanity + caching (in that order).
Do not use “just increase max_connections”, use pooling (PgBouncer) + right-sized pools (too many connections kills throughput).
Do not use hot partitions / single shard keys, use evenly distributed keys or composite sharding to avoid hotspots.
Do not use ad-hoc migrations in prod, use online migration patterns (expand/contract, backfills, dual writes when needed).
Do not use no backups because “we have replicas”, use tested restores + PITR (a replica is not a backup).
Do not use “we’ll clean it later” retention, use TTL/partition drop for time-series and audit logs (deletes don’t scale).
Do not use indexing without considering writes, use the minimum indexes that hit your p95 (each index is a write tax).
Do not use text search via LIKE '%foo%', use proper search (Postgres GIN/tsvector) or a search engine when ranking matters.
Do not use cache as truth, use DB as source of truth and caches as derived state with invalidation strategy.
Abhishek Singh@0xlelouch_
Do not use REST + polling + “is it done?” endpoints, use async jobs + webhook/callbacks + idempotency keys. Do not use cron + bash scripts + hope, use a workflow engine (Temporal / Argo Workflows) with retries, timeouts, and history. Do not use “logs in prod” debugging, use distributed tracing + correlation IDs + structured logs. Do not use manual SSH fixes on servers, use immutable deployments (containers/images) + GitOps. Do not use one giant DB for everything, use Postgres for OLTP + a real OLAP store for analytics (ClickHouse/Druid) and keep them separate. Do not use offset pagination at scale, use cursor/keyset pagination with stable ordering. Do not use global mutexes for rate limits, use token bucket with Redis/Lua or a dedicated rate-limit service. Do not use “exactly once” promises to sleep at night, use at-least-once + dedupe keys + idempotent handlers. Do not use Kafka as a queue for retries, use DLQ + retry topics + backoff (or a real queue like SQS) depending on semantics. Do not use “cache everything” reflexively, use caching only with correctness guarantees (TTL + stampede protection + versioned keys). Do not use “one config per env” copied around, use a single config schema + typed validation + runtime reload. Do not use ad-hoc feature flags in code, use a flag service + kill switches + gradual rollouts. Do not use dashboards as your alerting system, use SLOs + error budgets + actionable alerts (not spam). Do not use “k8s will autoscale it” as capacity planning, use load tests + p95/p99 budgets + real headroom math. Do not use “JWT everywhere” blindly, use short-lived access tokens + refresh + revocation strategy (or sessions when you need instant logout). Do not use “one big microservice mesh” to fix architecture, use clear boundaries + contracts + fewer services with better ownership. Do not use “just add more replicas” for DB pressure, use query shaping + indexes + caching + read replicas (in that order).
English
I really want to understand this, the conversations happen is at whose expense ?
Haven't really had a eye for clawdbot
Grummz@Grummz
I don't mean to alarm anyone, but there is now a social media site for bots. They are already talking and posting. Humans welcome.
English
Aplus. retweetet
Shipped production-ready Account Abstraction for @StellarOrg! 🌟
stellar-aa-sdk v2:
✅ Works with 100% of Soroban ecosystem
✅ Smart wallets compatible with any DEX, token, or protocol
✅ Session keys + social recovery
✅ CustomAccountInterface compliant
English
@Dominus_Kelvin Hetzner account verification failed multiple times. I just settled for railway.
How did you yours?
English
@PayfromHQ is coming!
Harri@Harri_obi
Speed: You don’t take cards, Zelle, Cash App, Venmo? Vendor: We don’t really do that in Nigeria Speed: Could you take USDC and USDT? Vendor: Yes! If you’re building for Africa and not optimising for crypto, you’re solving yesterday’s problems and designing for a fast failing system. Crypto is inevitable!
English