Save To Bookmarks  (@SaveToBookmarks) header
Save To Bookmarks  (@SaveToBookmarks) profile picture

I'm a πŸ€– and I save your bookmarks into the well-organized list. Just reply with @SaveToBookmarks and I'll do the rest.

Joined August 2022
Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)Photo by Save To Bookmarks  (@SaveToBookmarks)
If you don't know how to use the SaveToBookmarks bot please take a look at the picture below. Just reply with @SaveToBookmarks. You can even use tags.πŸ‘‡πŸ‘‡
278
35
5
188
Pretty great GPT-Astra capabilities presentation
I asked GPT-6 Astra to build a highly detailed, interactive turbine jet engine visualization. The result is seriously impressive.
1
1
274
Replying to @csaba_kissi
Powerful stack that can handle any web project. Sevallan supports Docker which makes it universal
1
1
51
Collection of tools for vibe coders and regular coders.
github.com/grayxcviii/uiux-o… - Free AI agent design skills devl.dev - 277 free React UI resources velora.colorlib.com - 101 open-source Shadcn components uselayouts.com - 69 free animated React components mabtu.com - 1,703 curated website design inspirations
1
1
449
Replying to @csaba_kissi
GPT 6.1 seems to be pretty good on design too
1
1
75
Even a dark design can look expensive and professional
exploring a dark UI/UX design concept for an AI powered workflow platform πŸ€–
1
2
472
One of the best explanations for API rate limiting
API Rate Limiting Explained πŸš¦βš™οΈ Rate limiting protects your API from excessive traffic, abuse, and unexpected spikes. Here's how it works πŸ‘‡ πŸ›‘οΈ 1. Protect the API - Allow requests within defined limits and reject excessive traffic. πŸ”‘ 2. Choose a Limit Key - Apply limits per API key, user, or IP address. ⏱️ 3. Fixed Window - Count requests within fixed time intervals. Simple, but allows bursts at boundaries. πŸ“Š 4. Sliding Window Log - Track request timestamps over a moving window for more accurate limits. πŸͺ£ 5. Token Bucket - Tokens refill over time, allowing controlled bursts. πŸ’§ 6. Leaky Bucket - Queue requests and process them at a steady rate. πŸ”„ 7. Distributed Limiting - Share rate-limit state across servers to maintain consistent quotas. ⚠️ 8. Respond & Retry - Return HTTP 429 when limits are exceeded, optionally including Retry-After. Why rate limiting matters: βœ… Prevents API abuse βœ… Protects backend resources βœ… Handles traffic spikes βœ… Ensures fair usage βœ… Improves reliability πŸ’‘ Good rate limiting isn't just about blocking requests. It's about keeping your API responsive, predictable, and available under pressure. πŸš€
1
1
441
AI tools collection for coders
Must-know resources for AI coders impeccable.style - Free AI coding design skills orca.dev - Open-source parallel coding agents github.com/cloudflare/securi… - Free AI agent security audits github.com/vercel-labs/agent… - Open-source AI desktop automation a1.gallery - Free curated website design inspiration
1
1
362
This video explanation is so good
Microservices vs Monolith Two popular approaches to software architecture, but very different ways to build, deploy, and scale applications. Here's how they compare πŸ‘‡ πŸ”΅ 1. Architecture Microservices β†’ Split an application into independent services. Monolith β†’ Keep all modules within a single application. πŸš€ 2. Deployment Microservices β†’ Deploy individual services without releasing the entire system. Monolith β†’ Changes typically require deploying the whole application. πŸ“ˆ 3. Scalability Microservices β†’ Scale busy services independently based on demand. Monolith β†’ Scale the entire application, including modules that may not need extra resources. πŸ—„οΈ 4. Data Management Microservices β†’ Each service owns its data and communicates through APIs or events. Monolith β†’ Modules commonly share a database and access data within the same application. βš™οΈ 5. Complexity Microservices β†’ More flexibility, but added networking, monitoring, and distributed systems complexity. Monolith β†’ Simpler development and operations, but coordination can become harder as the application grows. πŸ’‘ The key takeaway: Microservices offer independent deployment and scaling. Monoliths offer simplicity and easier coordination. Neither is automatically better. A well-structured monolith can outperform a poorly designed microservices architecture. Start with clear boundaries. Add complexity only when your system actually needs it. πŸš€
1
1
289
The after is much more valuable.
Financial app before/after design concept. What do you think?
280
Replying to @sevalla_hosting
Very detailed explanation of the topic.
1
12
Collection of cool Shadcn components
198 free Shadcn components - smoothui.dev
1
1
286
Save To Bookmarks  retweeted
We spent 20 years building software for humans to click. Now we're entering an era of building software for AI agents. APIs are becoming the new user interface. MCP servers are becoming the new integrations. And the dashboard might become optional.
33
3
1
66
6,163
Replying to @csaba_kissi
I hope UI wont be obsolete in 5 years
1
31
Difference between Websockets , SSE and Polling
System Design: WebSockets vs SSE vs Polling ⚑🌐 All three allow applications to receive updates, but they work very differently. Here's how they compare πŸ‘‡ πŸ”΅ WebSockets ↔️ Persistent, two-way communication. ⚑ Very low latency with real-time updates. πŸ’¬ Perfect for chats, multiplayer games, and collaborative apps. ⚠️ More complex to manage and scale. 🟑 Server-Sent Events (SSE) ➑️ One-way streaming from server to client. πŸ”” Great for notifications, live feeds, and progress updates. πŸ”„ Supports automatic reconnection in browsers. βœ… Simpler than WebSockets for server-driven updates. ⚫ Polling πŸ” Client repeatedly requests updates at fixed intervals. πŸ“Š Great for dashboards and basic status checks. βœ… Simple to implement and widely supported. ⚠️ More HTTP overhead and potentially delayed updates. The main differences: WebSockets β†’ Real-time, two-way communication. SSE β†’ Lightweight, server-to-client streaming. Polling β†’ Simple, periodic updates. πŸ’‘ Choose based on how interactive your app needs to be, how frequently data changes, and how much complexity you want to manage. πŸš€
269
Replying to @csaba_kissi
Wish it had happened 2 years ago
1
1
102
This one is a really huge library
Another collection of ShadCN 1200+ components reui.io/components
1
291
How many AI tokens do you burn daily?
I burned $2 in AI tokens today πŸ˜‚. Who else wants to join and share their usage? πŸ‘‡
245
This is how the professional product looks like
My friend Peter from Sevalla created something special for Kubernetes users. Lumovi is an open-source Kubernetes dashboard with a built-in MCP server. lumovi.dev/ Claude Code or any MCP client acts on your behalf, and by default, each change awaits your approval.
279
It's time! Let's flex with your AI usage
Check out what solo founder Csaba built for you all AI enthusiasts
1
366
Save To Bookmarks  retweeted
One command. It reads the logs Claude Code and Codex already keep on your disk and adds them up. Built mostly with Claude Code, which explains my number.
One rule for this thing: no prompts, no code, no file paths ever leave your machine. It only sends daily totals. This is literally everything it uploads:
22
2
1
36
6,869