Abdulbasit @dev_abdulbasit

@Oh_Sahs Good morning sir, please what’s your name on LinkedIn sir ? 🙏

Oracle CEO just ten minutes before announcing mass layoffs 😭😀

@SirPelzBuilds @esteeedev @victorachede @grok Ahh😭😂 and he has blue tick o

@prime_sui 😭😭

Error: JSON parameter needs to be valid JSON I just dey moody since morning 😭

@samkenny365 @officialABAT @grok It will take you nothing to read tho😂

At this point I’m trying to kill 2 birds with no stone😂😭

@MichealCodes God i see what you’re doing for people 🤲

@konspire_cz @Teehanz005 Can I send a DM too ?

I created a super fun game for the Scrolly X Superteam No-code Jam. Game name: EmoMaze. Similar to Pac-Man, you have 2 minutes to navigate the correct path in the maze to get the emoji home. #ScrollyGameJam @Scrollyfeed @SuperteamUK

@Sam_Dumitriu This is absurd.

You finally did it. You dockerized your entire app. Your Node API, your React frontend, your Postgres DB all neatly packaged. Your docker-compose file brings it all up perfectly on your machine. You feel like a genius. Then comes production. You need reliability. You need scale. So you think, "I'll just run my containers on a few servers." Suddenly, the simplicity vanishes. - How do your frontend containers find the API containers when their IPs keep changing? - What happens when a server dies at 3 AM? Who restarts those containers? - How do you update your API image without bringing everything down? Manually scripting this across multiple machines turns into a nightmare, fast. Your beautiful Docker setup is now tangled in SSH scripts and hope. You've heard of Kubernetes (K8s). Maybe you think it's just Docker Swarm but way more complex or something only huge companies need. That's missing the core idea. Kubernetes isn't just about running containers. It's about managing them automatically, at scale. It's an orchestrator. The fundamental shift is this: You stop telling servers what to do (imperative). You tell Kubernetes what you want the end result to look like (declarative). You define your application's desired state in YAML files: - I want 3 replicas of my API container running image v1.2. - They need to be reachable via a stable network name called api-service. - They need 500MB of RAM each. You give this to Kubernetes. Its entire job is to constantly watch the actual state and force it to match your desired state. This is how it solves all those production nightmares: Automatic Bin Packing & Scheduling: - K8s looks at your servers (Nodes) and figures out the best place to run your containers based on available resources. You don't manually assign containers to machines. Self-Healing: - A container crashes. K8s notices. Actual state (2 replicas) doesn't match desired state (3 replicas). - It automatically starts a new container to replace the failed one. No human intervention needed. Horizontal Scaling: - Traffic spikes. You need 10 API containers, not 3. - You change one line in your YAML file (replicas: 10). K8s handles the rest, starting new containers across your available servers. You can even set it to autoscale based on CPU or memory usage. Service Discovery and Load Balancing: - How do containers find each other? You create a Kubernetes 'Service'. - K8s gives this service a stable internal IP and DNS name (like api-service). - When another container calls api-service, K8s automatically routes the traffic to one of the healthy API containers, balancing the load. No more hardcoded IPs. Automated Rollouts (and Rollbacks): - Need to update your API to v1.3? You update the image version in your YAML. - K8s performs a rolling update by default: it gradually starts new v1.3 containers and stops old v1.2 containers, ensuring zero downtime. - Update goes wrong? K8s can automatically roll back to the previous stable version. Kubernetes isn't just running containers. It's the automated, resilient operating system for your entire distributed application. It lets you manage complexity declaratively, so you can focus on your code, not on firefighting servers.

Implemented API rate limiting by IP address. 1000 requests per hour per IP. Perfect protection against abuse. Next week: Legitimate customer hit rate limit. Complained their service was broken. They were behind corporate NAT. 500 employees sharing one IP address. Hit limit in 20 minutes. Changed to rate limit by API key instead. Problem solved. Week after: Bot attack. 50,000 requests per hour. Different API keys. Free tier abuse. Changed to rate limit by both IP and API key. Problem solved. Week after: DDoS from 10,000 different IPs using 10,000 different free tier API keys. Rate limiting was useless against distributed attacks. Real solution: - IP-based rate limiting for unauthenticated endpoints - API key rate limiting for authenticated endpoints - Behavioral analysis for suspicious patterns - CAPTCHA challenge for suspicious traffic - CloudFlare in front for DDoS protection - Cost limits on free tier There's no single rate limiting strategy that works. You need layers. IP, user, account, behavior, and external DDoS protection.

@jideabdqudus I feel your pain bro😂

Is there anyone else who still favors reading physical books over e-books?

'You bring great energy to the team' - As per generator or solar system? 'You're a valuable asset to the company' - What does this even mean 🤣🤣🤣 'You always go above and beyond' - Mental health, hello? How about going above and beyond on what matters, not stuff nobody cares about? 'You have excellent potential for growth' - I don't know whether to cry or laugh. 'Your contributions are truly appreciated' - this one is the most useless one. How are they appreciated? 'You're doing amazing work, keep it up' - which part of the work was amazing? is it everything? 'You're really making a difference here' - Quite rubbish if you ask me. 'You have such a positive attitude' - Are you a toddler? 'You're an inspiration to work with' - Which of my behaviours inspire you? Give me an example. You consistently exceed expectations - what does that translate to?

Idris Ayinde, FCA, CFA @hedrees_ayinde

11 months ago

Don’t get carried away by feedback that focused on just your personalty without actionable actions that you can improve on. Phrases like “you are a joy to work with” etc fall within this category. Even when they say you are ticking all the boxes, ask questions on how you can

1 8 117 21K 35

@misteryomi Aiit calm

One day, the work I’m putting in will pay off, and when it does, this tweet will be the proof I always knew it would happen.