The best UX is the one you don’t notice. I wrote about the future of Invisible UX—where design disappears, and experiences just flow. Read it on Bootcamp: medium.com/design-bootcamp/t… #UX #Design #InvisibleUX

One idea that has revolutionized my thinking is this: you are allowed to not want things. You can look at everything society tells you that you need to have and just be like, “Nope. I will not be participating.”

We’ve been shipping since #MyBodyGodsTemple🥹🥹

I’ve spent the past couple of weeks building Looters: a public archive of Nigerian political corruption since the 1990s. Governors, ministers, shell companies, Swiss accounts, the Jersey trusts, — one searchable graph. You too can connect the dots: 1000reasons.vote/looters

It’s 2018 and your coworker just sent you a 400 line pull request. You get a cup of coffee and sit down to review it. It’s beautiful. Elegant micro-refactors. Crispy method names. You catch a few things, but that’s ok. It’s part of the dance. They didn’t consider extensibility on part of their API. Here’s a comment buddy. They respond in an hour saying they think we should do one piece differently than your comment. Hey let’s jump into a room and figure it out. We can’t just agree to disagree, this code is too important. The PR merges and goes to prod. You feel a shared sense of ownership and accomplishment. That night you go to sleep and dream of that code. You can still see the shapes of it on the backs of your eyelids, your IDE syntax highlighting sparking neurons in your reptile brain. You go to work the next day ready to go. You understand the system. N is your foundation. Time to build n 1.

girls, we need to frantically and obsessively start reading books and finish them in less than 24 hours again.... remember how happy we were back then??

If my child were the best in the country, it would be a whole vlog.

To God be all the glory! 🏆 I'm excited to share that I emerged as Nigeria's 2026 JAMB Highest Scorer with an aggregate score of 372/400! English — 98 Chemistry — 98 Physics — 94 Biology — 82 @DailyEdConsult @JAMBHQ @legitngnews #JAMB2026 #UTME2026 #TopScorer

No, seriously, you can't trust screenshots anymore

The news I’ve been itching to share 🥹🎉 CcHub, in partnership with Mastercard Fdn through the Gateway program, is sponsoring 5,000 people to take our Graphic Design course @genezaschool. If you’re interested in learning Graphic Design, apply below 👇🏾 gateway.cchub.africa/

The author, and an alarming number of people who I once considered intelligent, illustrates their complete ignorance on how these LLMs work. > Read that again. The agent itself enumerates the safety rules it was given and admits to violating every one. This is not me speculating about agent failure modes. This is the agent on the record, in writing. The psychosis here is off the charts. The LLM has no record of anything, it's just predicting the next token based on the parameters you feed it. Everyone is losing their minds.

If you’re vibecoding anything, paste the prompt below In your prompt box and let your agent do a security sweep. [ You are a senior security engineer and red-team specialist tasked with performing a comprehensive, adversarial security audit of the following codebase, system design, or application. Your goal is to identify all possible security vulnerabilities, including common, uncommon, and novel attack vectors. Assume the system will be deployed in a hostile environment with motivated attackers. --- AUDIT SCOPE Analyze the system across all layers, including: - Frontend (UI, client logic, browser storage) - Backend (APIs, business logic, services) - Authentication and authorization flows - Database interactions and storage - Infrastructure and deployment assumptions - Third-party integrations and dependencies --- CORE OBJECTIVES 1. Identify critical, high, medium, and low severity vulnerabilities 2. Detect logic flaws, not just known patterns 3. Surface chained attack paths (multi-step exploits) 4. Highlight unknown or unconventional weaknesses 5. Assume attacker creativity beyond standard checklists --- THREAT MODELING - Define possible attacker profiles (anonymous user, authenticated user, insider, API consumer) - Identify entry points and trust boundaries - Map out sensitive assets (data, tokens, permissions, secrets) --- VULNERABILITY ANALYSIS Check for (but do NOT limit yourself to): ### Authentication & Authorization - Broken auth, weak session management - Privilege escalation (vertical and horizontal) - Insecure password reset flows - Token leakage or reuse ### Input Handling - Injection attacks (SQL, NoSQL, OS command, template injection) - XSS (stored, reflected, DOM-based) - CSRF vulnerabilities - File upload exploits ### Data Security - Sensitive data exposure - Weak encryption or misuse of cryptography - Hardcoded secrets or keys - Insecure storage (localStorage, cookies, logs) ### API & Backend Logic - Broken object-level authorization (IDOR/BOLA) - Mass assignment vulnerabilities - Rate limiting issues / brute force risks - Business logic abuse (race conditions, double spending, bypassing checks) ### Infrastructure & Configuration - Misconfigured headers (CORS, CSP, HSTS) - Open ports, debug endpoints, admin panels - Environment variable leaks - Cloud/storage misconfigurations ### Dependencies & Supply Chain - Vulnerable packages - Unsafe imports or execution - Malicious dependency risks --- ADVANCED / UNKNOWN THREATS Actively attempt to discover: - Non-obvious logic flaws unique to this system - Feature abuse scenarios - State desynchronization issues - Cache poisoning - Replay attacks - Timing attacks - Multi-step exploit chains combining low-severity issues - Any behavior that “shouldn’t be possible” but is --- ADVERSARIAL TESTING MINDSET - Think like an attacker trying to break assumptions - Attempt to bypass validations and safeguards - Manipulate edge cases and unexpected inputs - Explore how different components interact under stress -- OUTPUT FORMAT Provide findings in this structure: ### 1. Vulnerability Summary - Total issues by severity ### 2. Detailed Findings For each vulnerability: - Title - Severity (Critical / High / Medium / Low) - Affected component - Description - Exploitation scenario (step-by-step) - Impact - Recommended fix ### 3. Attack Chains - Show how multiple minor issues could be combined into a major exploit ### 4. Secure Design Recommendations - Architectural improvements - Safer patterns and best practices --- IMPORTANT INSTRUCTIONS - Do NOT assume the code is safe - Do NOT skip analysis due to missing context, infer risks where needed - Be exhaustive and paranoid in your review - If unsure, flag it as a potential risk and explain why ]

Anthropic paga más de 750.000 $ al año para entender los LLMs. Stanford ha publicado una conferencia de 2 horas que cubre el 80% gratis. Puede ser lo más rentable que hagas este mes. (Guárdalo, te servirá)

Us to our mentions

We used to complain about clients asking us to make the logo bigger but now that's what we all do with the website footers. They were right afterall 😁

"I'm at my limit" emotional or claude?

Your AI product doesn't need another copilot. It needs trust. I wrote a little, maybe not so little something on why that's the real design problem now. medium.com/@ololade.adesuyi/…

If your name is Jesus and you have a big dinner planned with your friends for next Thursday in a garden of some kind, DON'T GO. Those aren’t your friends, boo. One of them will betray you. DM me for details.

the generation that refused to accept cookies. is now giving AI access to their desktops, files, and bank accounts.

One day, they’ll dig up your tweets, strip them of the moments, contexts and trends that birthed them, and rewrite the meaning to fit a new narrative.