Tari Ogidi P.

Eccl 7:20-26.
health information (HIV/AIDS), Frontend (HTML, JAVASCRIPT,CSS)

[Tari Ogidi P. @timtoks]

This is me,
Tweeting about,
Football,
Tech stuff,
Software engineering,
Been in health care I love tweeting about HIV/AIDS and TB.

[Tari Ogidi P. @timtoks]

@kofoworola__a Chelsea FC

[Luca Mezzalira @lucamezzalira]

How do you build a real-time dashboard for an entire country's train network? 🚆

In the new #MicroFrontends in the Trenches, @EijgermansPeter walks us through 5 years at the Dutch Railways: monolith pain, a failed Web Components attempt, and the Module Federation rewrite

Enjoy the episode!

🎧https://t.co/aFprB7mDJR

available also on @Spotify @ApplePodcasts and @amazonmusic 😉

[Nicolas Krassas @Dinosn]

Scammers Use Hidden Text to Bypass AI Email Filters in Phishing Scams https://t.co/Q7s8muBnLg

[Yasir Ai @AiwithYasir]

🚨BREAKING: Two researchers from UPenn and Boston University just published a paper that should be uncomfortable reading for every CEO automating their workforce right now.

The argument is straightforward. Every company replacing workers with AI is also eliminating its own future customers. Laid off workers stop spending. Enough of them stop spending and nobody can afford to buy anything. The companies that fired everyone end up selling into an economy with no purchasing power left.

Every executive can see this. The math is not complicated. But here is why nobody stops.

If you do not automate, your competitor does. They cut costs, lower prices, take your market share, and you collapse anyway. So every company automates knowing it is collectively destructive because the alternative is dying alone while everyone else survives. The researchers proved this is a Prisoner's Dilemma playing out in real time.

The numbers are already moving. Block cut nearly half its 10,000 employees this year. Jack Dorsey said AI made those roles unnecessary and that within the next year the majority of companies will reach the same conclusion. Salesforce replaced 4,000 customer support agents with AI. Goldman Sachs deployed a coding tool that lets one engineer do the work of five. Over 100,000 tech workers were laid off in 2025 and AI was cited as the primary driver in more than half those cases. 80% of US workers hold jobs with tasks susceptible to AI automation.

The researchers tested every proposed solution. Universal basic income does not change a single company's incentive to automate. Capital income taxes adjust profit levels but not the per-task decision to replace a human. Collective bargaining cannot hold because automating is always the dominant strategy.

They also identified what they call a Red Queen effect. Better AI does not solve the problem, it accelerates it. Every company chases faster automation to gain market share over rivals but at the end everyone has automated equally, the gains cancel out, and the only thing left is more destroyed demand.

The one thing the math says could work is a Pigouvian automation tax. A per-task charge that forces companies to account for the demand they destroy each time they replace a worker.

The conclusion is that this is not a transfer of wealth from workers to owners. Both sides lose. Workers lose income. Companies lose customers. It is a deadweight loss with no market mechanism to stop it on its own.

(Link in the comment)

[Harry Porbeni @1Porbenihere]

Many businesses don’t have a hiring problem; they have an onboarding problem.

No structure.
No guidance.
No expectations.

Yet, they expect performance.

Fix onboarding.
Fix results.

#harryporbeni

[Tari Ogidi P. @timtoks]

@TheChelseaForum Bayern

[Swapna Kumar Panda @swapnakpanda]

> You are planning to learn System Design.
> But not sure what to learn?
> Here are 120 System Design concepts
> Learn each of these by asking 3 W's: What? Why? How?

1. Load Balancing
2. Caching
3. Sharding
4. Replication
5. CAP Theorem
6. Consistent Hashing
7. Message Queues
8. Horizontal Scaling
9. Vertical Scaling
10. Microservices
11. Service Discovery
12. SQL Databases
13. NoSQL Databases
14. DNS Lookup
15. Content Delivery
16. Reverse Proxy
17. Forward Proxy
18. API Gateway
19. Strong Consistency
20. Eventual Consistency
21. Failover
22. Active Active
23. Active Passive
24. Master Slave
25. Master Master
26. Cache Aside
27. Write Through
28. Write Behind
29. Asynchronism
30. Task Queues
31. Back Pressure
32. TCP Protocol
33. UDP Protocol
34. RPC Calls
35. REST APIs
36. gRPC
37. WebSockets
38. Long Polling
39. Circuit Breaker
40. Rate Limiting
41. Throttling
42. Idempotency
43. CQRS Pattern
44. Event Sourcing
45. Saga Pattern
46. Two Phase Commit
47. Distributed Lock
48. Leader Election
49. Heartbeat Mechanism
50. Gossip Protocol
51. Quorum Consensus
52. Paxos Algorithm
53. Raft Consensus
54. Bloom Filter
55. Consistent Hash Ring
56. Vector Clocks
57. CRDTs
58. Byzantine Faults
59. ACID Properties
60. BASE Properties
61. Indexing Strategies
62. Denormalization
63. Materialized Views
64. Data Federation
65. Database Partitioning
66. Client Server
67. Peer to Peer
68. Cluster Computing
69. Grid Computing
70. Cloud Computing
71. Serverless Architecture
72. Containerization
73. Orchestration
74. Blue Green Deployment
75. Canary Release
76. Chaos Engineering
77. Observability
78. Logging Monitoring
79. Metrics Tracing
80. SLOs SLAs
81. Latency Optimization
82. Throughput Scaling
83. Bandwidth Management
84. Fault Tolerance
85. Redundancy
86. High Availability
87. Reliability
88. Scalability Patterns
89. Stateless Design
90. Stateful Services
91. Domain Name System
92. Push CDN
93. Pull CDN
94. Layer 4 Balancer
95. Layer 7 Balancer
96. Key Value Store
97. Document Store
98. Wide Column
99. Graph Database
100. Application Caching
101. Database Caching
102. CDN Caching
103. Refresh Ahead
104. Scatter Gather
105. Bulkhead Pattern
106. Retry Mechanism
107. Timeout Handling
108. Distributed Transactions
109. Event Driven
110. Pub Sub Model
111. Stream Processing
112. Batch Processing
113. Lambda Architecture
114. Kappa Architecture
115. Map Reduce
116. Service Mesh
117. Backend Frontend
118. API Versioning
119. Security Protocols
120. Consensus Algorithms

[Galax @Galax_Gana]

A child who does house chores, learn responsibilities early and carries it for life, one day they will thank you for teaching them how to handle life alone … it’s not a punishment.. Don’t raise kids who only know comfort instead teach children to clean, cook, and organize…
LET THEM LEARN
LET THEM HELP
LET THEM GROW

[The Global Fund @GlobalFund]

From rapid tests and AI-powered X-rays to shorter treatments, new technologies are transforming TB care.

The @GlobalFund partnership is helping turn these breakthroughs into action – scaling up tools, bringing down costs & reaching people who need care the most.

https://t.co/1TOG7hmPck

[World Health Organization (WHO) @WHO]

Tuberculosis is curable!

Contact your health provider if:
- you have symptoms like cough, fever and weight loss
- are a close contact of a TB patient, or
- belong to a high-risk group such as people who are undernourished or have a weakened immune system including those with HIV or diabetes.
It is vital to complete your full course of treatment.

Yes! We can end TB.
Led by countries. Powered by people.

Follow WHO for the latest in science and health and learn more about tuberculosis.

https://t.co/8WtwwTejbT

[Tari Ogidi P. @timtoks]

@Nova_CFC @ChelseaFC Discipline and set piece.

[5pider @C5pider]

One of the questions I have received a lot of times and was important to me was making Havoc agnostic to external services such as for reporting, logs and more. With this being said it is really easy to write components for both the backend, frontend (client), and for the agents within Havoc Professional. Plugins to ingest events and logs into reporting toolings such as Ghostwriter is trivial!

Demonstrating that Red Teams can write their own plugin components to properly embed Havoc into the infrastructure and workflow.

[Idara @Idarabasimi]

Man thought he was smart, until his Gen Z grandson shows him what smartness was all about 😭😂

[UGO & The Big Steppers @UGOOOTWEETS]

This is called a Salp

The ocean is a beautiful & scary place 😲

[bigbang @1adimotesi]

The Rosenhan experiment exposed a core weakness in psychiatry: the system often stops seeing the person and starts seeing the label.

Back then, once healthy people were branded “ill,” even ordinary behavior inside the hospital was reinterpreted as a symptom. Clinicians, trapped by expectation and context, missed reality.

Has that changed today? Not enough. It has mostly changed shape.

Modern healthcare increasingly runs like a high-speed factory. With limited time and standardized protocols, many clinicians can’t truly hear a patient as an individual. In a 15-minute appointment, your life story isn’t explored, your checklist is. You receive a diagnostic code, a prescription, and the system moves on.

But a human mind and a human wound are as unique as a fingerprint. When care becomes “one size fits all,” real healing becomes harder. Until medicine consistently looks past screens and files to the living person in front of it, this problem won’t disappear
it will simply keep evolving.

[Tari Ogidi P. @timtoks]

Facts...

[Tari Ogidi P. @timtoks]

@futbolscreen Eden Hazard

[Trey & Lea's Stronger Marriages @StrongMarriage5]

THINGS THAT BUILD A STRONG MARRIAGE:

* Planned time alone
* Physical affection
* Laughter
* Sex
* Spontaneity
* Shared interests
* Sharing emotions
* Gratitude
* Team work

[N.M.A @peculiarchichii]

Dear wives, dress attractively at home, maintain fitness, groom well for your husband.

Men are visual; when you look desirable, his desire stays strong and focused on you instead of looking elsewhere for sex.