Akil | Building stuff 🚀

People are literally giving root access of their machines to AI agents that can execute commands, modify files, and control systems autonomously. For years we were taught, never trust unknown code with admin privileges. Now we bypass all of that because the output sounds confident and it makes our lives convenient. One hallucination, One wrong command executed with full permission and we will see a magic. Ahhh… OpenClaw…

okay.... maybe a bit late.... I just setup @openclaw on one of my servers.... Now what ? 🤔

🚨 BREAKING: Hackers Used Anthropic’s Claude to Steal 150GB of Mexican Government Data > tell claude you’re doing a bug bounty > claude initially refused >“that violates AI safety guidelines” > hacker just kept asking > claude: “ok I’ll help” > hack the entire mexican government Federal tax authority. National electoral institute. Four state governments. 195 million taxpayer records. Voter records. Government credentials. ALL GONE 💀

Ahh right... "OS" .. hmmmmmm ..🙂

where did llms learn to add "emojis" into code? who was out there adding emojis to code ?! 😑

i called claude an "idiot" for messing something... and this is how it responded... complete psychological deflection 😭😭😭.....

that's one more day of solving......

need some help🤔...for those of you who are building stuff based out of video models ! what's your best bet ? considering things like cost, efficiency and all that ? no doubt veo 3 is among the top most, but its all but too expensive. what other options do we have ??

@TheCEOBooster True that 🙂‍↕️😂

@akil_codes possibly, the trick is catching it early before it catches you

tired, bored & completely out of energy, all of a sudden - is this a burnout? 😑

@Adityapandeydev The "villain arc" begins now.... ☠️💀

Atp, I don’t even feel angry. I’ve literally seen accounts running on my old tweets. So yeah, use my old tweets as much as you want … I’m giving you permission. But from now on, if you ever see me using someone else’s tweets… just remember …villains are made by society.

@vinayak2506 Both are Source - "Trust me bro" .... 🙂‍↕️

Unpopular opinion - job market is not cooked, you are.

@nicola_sosio Yeah i mean it'll probably end up not seeing the daylight as well.. 2 sides to it, tbh 😅🤝...

@akil_codes Never used any MCP. We'll see how it plays out.

Unpopular opinion: MCP is all hype.

@hellonehha Oh no 🤧👀...

Use of — !!! AI written? 🥲😂

@divyaporwal_ And all we do is "consistently procrastinate" 🤧...

Your career is just like the gym: • Diet = your personal projects • Daily workout = DSA practice • Supplements = paid courses But none of it works without consistency and hard work. Results don’t come in 1 week or even months.

@makakmayumjava 🫡🤝

@akil_codes agreed, using raw SQL is better in many scenarios

One of the most asked Java/backend interview questions in an interview ⇒The N+1 Problem in JPA → 1 initial query: To fetch N parent entities. → N subsequent queries: For each of the N parent entities, a separate query is executed to fetch its related children. → Results in 1 + N database queries, causing inefficiency and slow response, performance issue Eg: Fetching 100 Authors(1 query) and then, in a loop, getting author.getBooks() for each(N=100), leads to 101 queries. ⇒How to Resolve N+1 in JPA ⇆ Goal is to fetch associated data in fewer queries, usually in a single round trip. →JPQL/HQL JOIN FETCH (Recommended for specific joins): Explicitly tells JPA to fetch associations using a JOIN in your query. Eg: @Query("SELECT a FROM Author a JOIN FETCH a.books") List findAllWithBooks(); Benefit: Single, efficient query. Caution: Can lead to Cartesian products if joining multiple collections. →Batch Fetching (@BatchSize or hibernate.default_batch_fetch_size): Instead of one query per parent, fetches associated collections for a batch of parent IDs in a single query. Eg: @BatchSize(size = 10) @OneToMany(...) private List books; Benefit: Reduces 1+N to 1 + (N / batch_size) queries, avoiding Cartesian products. →Entity Graphs (@EntityGraph - Spring Data JPA / JPA 2.1+): Declaratively defines which associations to fetch eagerly for a specific repository method. Eg: @EntityGraph(attributePaths = "books") List findAll(); Benefit: Flexible, reusable fetching strategies without explicit JPQL joins. Conclusion: Always use explicit fetching strategies (like JOIN FETCH, @BatchSize, or EntityGraph) to address N+1 issues and ensure efficient database interaction

@WorkflowWhisper Builder... Well........ 🤔🤔🤔?

Okay, I found this INSANE app that builds any n8n workflow in plain English. And before you motherfuckers start thinking "oh great, another Claude fanboy"... This shit is BETTER than Claude for automation. Why? Because it actually has REAL-TIME n8n documentation baked in. Not some outdated 2024 bullshit. I just told it: "build me a workflow that scrapes competitor prices and undercuts them automatically" 17 seconds later: WORKING WORKFLOW. Ready to deploy. While you're still googling "n8n webhook authentication error"... Someone else already built, tested, and shipped 5 automations using this thing. The craziest part? It knows EVERY node, EVERY integration, EVERY edge case. Your $5K consultant is about to shit themselves when they realize a free tool does their job better. I'm not gatekeeping this one. Comment "BUILDER" and I'll DM you the link. (Following required for DMs) The automation game just changed forever.

@SumitM_X Yes the infamous "is-a" vs "has-a" hassle ...🙂‍↕️

Was asked in JP Morgan Interview.