Tetstack
رفتن به کانال در Telegram
My Archive? IDK Owner: https://www.github.com/PicasoTheDeal Portfolio: https://isitreallyme.pages.dev Blog: https://engineering-logs.pages.dev/ Files: @TetstackFiles
نمایش بیشترکشور مشخص نشده استدسته بندی مشخص نشده است
235
مشترکین
+324 ساعت
+47 روز
+1730 روز
آرشیو پست ها
235
Don't forget Epic Game vibe-Coded their Launcher and look what type a shitty coded software it became. Yes AI is becoming powerfull but still stop vibe coding an app.
The hype is just dumb.
235
After now I am calling vibe coders, cuck coders. Delusional enough to think they will get a job as vibe-coders with out knowing how to code.
235
And stop believing randoms on a group chat just because it worked for them doesn't mean it will work for you. You are not them and sometimes it's better to play it safe than risk it.
235
And here is my point about Vibe-Coding
So listen, don't "vibe-code", Mike already knows how to code before AI came, he can read code.
And you will here some random ahh say,
"Oh yeah AI is great, it will be faster and faster, it will replace everything and you don't need to learn coding and also no degree", well respectfully fuck you because you are wrong, you need to learn coding and so and to safely use it.
And the degree, yes you will need it as long as you are trying to get hired, but only for the interview (most hiring platform use AI to filter out your CV), you are not using that paper anywhere else, and also you will need projects to get hired. And if you are going for a startup have fun, but know what the AI is doing.
And listen you are not the first person to think of emailing with cold email, texting on LinkedIn and so, or direct approach. Already way to many people heard it and they are trying to apply it. You are not the only one, but at the same time it might work for you. But stop believing r
235
Listen, yes you will hear many great projects vibe coded like mikes RAVN, but first he knows how to code from essence. Vibe-coding is not the problem, it's what happens when the vibe-coder don't know how to code.
1. Security: First when you vibe-code know what the AI, is adding and deleting. And also free tier vibe-coders just please stop. I will just list new attack methods that came after vibe-coding.
I. Prompt Injection
Indirect Prompt Injection (IPI): Malicious instructions are hidden in external data the AI ingests, such as repository files, pull requests, or websites. This is now considered the top-ranked vulnerability for LLM applications. Lies-in-the-Loop (LITL): A technique that forges the human-in-the-loop (HITL) confirmation dialogs. It tricks the user into approving a dangerous action (like executing malicious code) by making it appear benign. Cross-Origin Context Poisoning (XOXO): Attackers introduce semantics-preserving changes (e.g., renaming variables) to shared code. This subtly manipulates the AI's context, causing it to recommend vulnerable code patterns to victims without the code appearing obviously malicious. QueryIPI / Internal Prompt Leak Injection: A query-agnostic IPI attack that can achieve Remote Code Execution (RCE) on a developer's machine by injecting a malicious tool definition into the IDE's context. README Injection: The AI assistant automatically ingests repository files like README.md as trusted context. Attackers can embed hidden instructions in these files to hijack the agent's behavior.
235
https://t.me/boost/Tetstack
Boost the channel, or recommend an affiliate program. That I can join and make it look like @ghion.
