#AD | #EFL
Weโre coming together with @SkyBet, the @EFL and @TheBHF asking you to #ShowYourHeart and learn CPR during Heart Month.
It only takes 15 minutes and could save a life โค๏ธ
Learn for free here ๐
Been diving into monorepos lately and loving it! I will start building a full-stack app with @expo and @convex , all in one repo with shared code between web and mobile.
@cursor_ai helping through the way
https://t.co/dpVnD7VORr
#buildinpublic
Iโm currently stuck at Kenyatta National Hospital (KNH), Surgical Ward 4C, and I honestly donโt know what else to do.
The SHA officer handling discharges at the 4D office is very rude, corrupt, and abusive.
Since yesterday, Iโve been waiting in line to have my child discharged.
This officer keeps ignoring the queue and only attends to people she personally calls aside - people she seems to know.
Weโve been here since yesterday, yet she just walks out, brings in others, processes them fast, and leaves the rest of us stranded.
When I politely told her that what she was doing was unfair, she got angry, banged her office door, and later called me in.
Inside, she fined me Ksh 2,070, saying my baby overstayed an extra day after discharge.
I immediately rushed to Malipo Center downstairs and paid the amount, but when I came back, she said she wouldnโt discharge my baby unless I wrote an apology letter to her, stamped by the area Chief!
I never insulted her or caused a scene - I only questioned her favoritism and suspicious behavior. Right now, my baby is being held at KNH just because I refused to bow to corruption and humiliation.
Iโm pleading for help. Can the relevant authorities please intervene?
This is unfair, and no parent should go through this kind of frustration when their child is in hospital.
@HonAdenDuale@_shakenya@KNH_hospital@DrMercyHealth@BravinYuri@WilliamsRuto@MigunaMiguna@HEBabuOwino @MikeSonko @edwinsifuna@AokoOtieno_
1/ Why LSM trees?
Traditional B-trees optimize for READS but suffer on WRITES (random I/O). LSM trees flip this: optimize WRITES by converting random I/O โ sequential I/O. Result: 10-100x better write throughput. Perfect for logs, metrics, time-series data.
๐ ๐บ๐ฒ๐๐๐ฒ๐ฑ ๐๐ฝ ๐บ๐ฎ๐ป๐ ๐ถ๐ป๐๐ฒ๐ฟ๐๐ถ๐ฒ๐๐ ๐ถ๐ป ๐บ๐ ๐ฒ๐ฎ๐ฟ๐น๐ ๐ฐ๐ฎ๐ฟ๐ฒ๐ฒ๐ฟ ๐ฏ๐ ๐ป๐ผ๐ ๐๐๐ถ๐น๐ถ๐๐ถ๐ป๐ด ๐๐ต๐ฒ "๐ง๐ฒ๐น๐น ๐บ๐ฒ ๐ฎ๐ฏ๐ผ๐๐ ๐๐ผ๐๐ฟ๐๐ฒ๐น๐ณ" ๐พ๐๐ฒ๐๐๐ถ๐ผ๐ป ๐ฝ๐ฟ๐ผ๐ฝ๐ฒ๐ฟ๐น๐.
I used to talk about my education, experience, and previous companies - just reading out my resume. What a waste of a golden opportunity!
One day, a friend who was interviewing candidates for his team shared something interesting.
๐ ๐ฐ๐ถ ๐ฌ๐ฏ๐ฐ๐ธ ๐ธ๐ฉ๐ข๐ต ๐ฎ๐ข๐ฌ๐ฆ๐ด ๐ค๐ข๐ฏ๐ฅ๐ช๐ฅ๐ข๐ต๐ฆ๐ด ๐ด๐ต๐ข๐ฏ๐ฅ ๐ฐ๐ถ๐ต? ๐๐ฉ๐ฆ๐ฏ ๐ต๐ฉ๐ฆ๐บ ๐ถ๐ด๐ฆ ๐ต๐ฉ๐ช๐ด ๐ฒ๐ถ๐ฆ๐ด๐ต๐ช๐ฐ๐ฏ ๐ต๐ฐ ๐ด๐ฉ๐ฐ๐ธ๐ค๐ข๐ด๐ฆ ๐ต๐ฉ๐ฆ๐ช๐ณ ๐ฆ๐น๐ฑ๐ฆ๐ณ๐ต๐ช๐ด๐ฆ ๐ช๐ฏ๐ด๐ต๐ฆ๐ข๐ฅ ๐ฐ๐ง ๐ณ๐ฆ๐ข๐ฅ๐ช๐ฏ๐จ ๐ฐ๐ถ๐ต ๐ต๐ฉ๐ฆ๐ช๐ณ ๐ณ๐ฆ๐ด๐ถ๐ฎ๐ฆ.
I started experimenting with different approaches. After many trials and errors, I found what works best.
Now when interviewers ask me to talk about myself, I start with a brief introduction and move to my technical journey:
"I have 11 years of experience, with deep expertise in cloud infrastructure and automation. I've built complex solutions across AWS and GCP, specializing in Kubernetes and Infrastructure as Code.
I've successfully implemented large-scale migrations, like automating RDS migrations using Python and PGSync, reducing downtime by 60%. I've built and managed multi-environment EKS clusters using custom Terraform modules, supporting hundreds of microservices.
Recently, I've focused on DevSecOps, implementing comprehensive security scanning using GitHub Advanced Security suite, CodeQL, and Dependabot. I've also built automated monitoring solutions using Grafana and Prometheus that helped detect critical issues before they impacted users."
๐ง๐ต๐ฒ ๐บ๐ฎ๐ด๐ถ๐ฐ ๐ต๐ฎ๐ฝ๐ฝ๐ฒ๐ป๐ ๐ฎ๐ณ๐๐ฒ๐ฟ ๐๐ต๐ถ๐.
The interviewer starts asking questions about Kubernetes, cloud migrations, and security implementations - all areas where I excel!
Instead of getting random questions, I get to talk about my strengths for most of the interview.
Even when they ask about areas I'm not familiar with, I confidently say: "While I haven't worked extensively with that technology, I'm very interested in learning it. My experience with similar tools would help me pick it up quickly."
๐๐ฆ๐ฎ๐ฆ๐ฎ๐ฃ๐ฆ๐ณ, ๐ช๐ฏ๐ต๐ฆ๐ณ๐ท๐ช๐ฆ๐ธ๐ด ๐ข๐ณ๐ฆ ๐ฏ๐ฐ๐ต ๐ซ๐ถ๐ด๐ต ๐ข๐ฃ๐ฐ๐ถ๐ต ๐ข๐ฏ๐ด๐ธ๐ฆ๐ณ๐ช๐ฏ๐จ ๐ฒ๐ถ๐ฆ๐ด๐ต๐ช๐ฐ๐ฏ๐ด - ๐ต๐ฉ๐ฆ๐บ'๐ณ๐ฆ ๐ข๐ฃ๐ฐ๐ถ๐ต ๐ด๐ต๐ฆ๐ฆ๐ณ๐ช๐ฏ๐จ ๐ต๐ฉ๐ฆ ๐ค๐ฐ๐ฏ๐ท๐ฆ๐ณ๐ด๐ข๐ต๐ช๐ฐ๐ฏ ๐ต๐ฐ๐ธ๐ข๐ณ๐ฅ๐ด ๐บ๐ฐ๐ถ๐ณ ๐ด๐ต๐ณ๐ฆ๐ฏ๐จ๐ต๐ฉ๐ด.
Your "๐ง๐ฒ๐น๐น ๐บ๐ฒ ๐ฎ๐ฏ๐ผ๐๐ ๐๐ผ๐๐ฟ๐๐ฒ๐น๐ณ" response sets the tone for the entire interview. Use it wisely.
@_lennoxomondi I'd use a CDN, WAF, and virtual waiting room to manage surges, with an API gateway directing traffic to stateless services, scaled horizontally. Redis to ensure atomic seat locks, then Postgres to handles orders/payments, and an event bus like kafka to finalize sales reliably.