Vinícius Lourenço

Semana passada desenvolvi um bot simples aqui pro Twitter que posta vagas relacionadas a área de T.I. E o que difere ele de outros perfis que fazem isso, de maneira automática ou não? Ele é alimentado pela própria comunidade, tipo o Waze. Viu uma vaga? Marque: @ViUmaVaga

Talking to smarter folks than me, I'm convinced many of the AI folks in my timeline are full of shit. Nobody is "running 20 agents over night" and building stuff for actual users. Maybe some are building internal tools or disposable software. Maybe. But building software people like using? That doesn't get hacked on day one or blow up after the 3rd user? Nope. I don't even understand what that's supposed to look like. Do you work out a 57 pages document that perfectly describes what you want to build and then summon 14 agents and have them run wild for 6 hours? And what comes out on the other end isn't a broken pile of shit? Nope. Not buying it. PS: it may also be that I have an IQ of 82 and can't figure it out.

Nova ferramenta do @Google @googlebrasil para quem está estudando IA, Cloud e Tecnologia! 🚀 Acabei de conhecer o Google Cloud Skills, e fiz um vídeo pra vocês. Use de forma gratuita: skills.google/?locale=pt_BR

There are 4 types of people saying "AI will replace Software Engineering" in 6 months 1. they own a company that benefits from replacing engineers (ceo, stockholders etc). they need to justify the amount invested into them 2. Company that made big cuts and they want to attribute it to whatever and AI is good excuse 3. People who never worked as as/with Software Engineering and have no clue the work is not just typing 4. Burned out engineers who don't want to do that job anymore

its me...

@farmDev79 faltou a peça

Negócio aqui tá a milhão hoje

I didn't want to comment on OpenClaw. Usually, when there's so much noise in the media, it's some ordinary stuff just hyped well. So I took time to learn how it works thanks to open source. I was right. OpenClaw is 2% of ordinary stuff and 98% of hype. To put it very shortly, in case you were wondering, there are two things in it: 1. You can chat with an LLM via a text messenger. Not anything new. 2. The LLM can use tools that run on your computer. Not anything new either. Most of the "magic" mentioned in the media is about its ability to use the browser. But it's not *its* ability. It's Playwright's ability. Playwright is a library made by Microsoft which allows you to programmatically run a browser. It uses a built-in vision model made by Microsoft that converts the browser's screen into a textual description for LLMs. Again, Microsoft has built Playwright exactly for what OpenClaw is using it. So, OpenClaw's typical workflow: 1. The user types in a text messenger "Buy me a flashlight on Amazon." 2. OpenClaw blindly dispatches this message to an LLM which has access to some tools, including Playwright. 3. The LLM, trained not by OpenClaw folks, decides that Playwright is the right tool (of course it is) and Amazon is the URL to navigate to. 4. Playwright, built not by OpenClaw folks, runs the browser, which navigates to Amazon, and returns the textual description of what Amazon's home page looks like. 5. OpenClaw blindly returns to the LLM this textual description. 6. The LLM (again without any help from OpenClaw) decides that one should type "flashlight" into the search field and press Search, so it calls the Playwright tool with the search parameters. 7. OpenClaw calls Playwright because the LLM told it to and types "flashlight" and then presses Search (it's all part of what Playwright does out of the box). ... In the end of this LLM-controlled scenario, the order is submitted. OpenClaw just listened to what the LLM told it to do via tool calls. I tried hard, and I haven't found anything else worth mentioning in the source code. There's also a part that keeps "memories" about past conversations, but it's all basic stuff. These memories are stored in text files and grep (controlled by LLMs trained to use grep, and trained not by OpenClaw folks) is used to search in them. It's a nice hobby project, just like Cursor or Perplexity are nice hobby projects, but there's nothing there to look for, except for the hype and 2% of unoriginal plumbing code.

🦔 Sam Altman: "A kid born today will never be smarter than AI, ever… We will think how bad those people of the 2000's had it." My Take This is a guy selling AI telling you AI will be smarter than every human who will ever be born. Take the source into account. There's a difference between knowledge and intelligence. AI can retrieve and pattern-match faster than any human. It can pass exams and write code. But intelligence isn't just processing speed and information access. It's judgment, creativity, understanding context, knowing when the answer isn't in the training data. A calculator is better at math than you are. That doesn't make it smarter. Wikipedia knows more facts than any person alive. Nobody calls it intelligent. Altman needs this narrative. OpenAI is burning $9 billion a year, doesn't expect profitability until 2029, and just watched Nvidia back away from a $100 billion deal because even the company selling the shovels has concerns about the business model. The pitch has to be that AI is inevitable, transformative, worth any cost. If you question that, you just don't understand what's coming. It's the same energy as every tech bubble before it. The product might be real. The hype around it is doing a lot of heavy lifting for the valuation. Hedgie🤗

AI is for people that want to be good at things without GETTING good at those things. Its pathetic.

Vibe coding reminds me of crypto. Everyone is trying to be a creator/builder, and no one actually uses the products. That being said, I think vibe coding is 100x more useful and definitely game-changing. But it’s funny how everyone makes content about it because it’s trendy, while no one actually uses the apps that come out of it.

This is what we're up against if we allow AI vibe coding to go unsupervised. Strong proof that LLM-generated code can cause more harm than good in unskilled hands. I stand by 100% of the points in this post. Hiring software developers is going to become a much bigger pain than it used to be, since recruiters cannot make a justified decision just by glancing at their GitHub profile. Open-source projects will be harder to manage due to the higher costs of reviewing PRs to prune AI slop. This is probably the best quote from the post that sums it all up: "AI multiplies what you already know. - 10 years of experience × AI = 10x output - 0 years of experience × AI = 10x slop" The skill is not yet dead. webmatrices.com/post/vibe-codi…

😂😂😂😂😂

This year has made me more of an internet collapse accelerationist. Social media used to feel social, but most days logging on feels like walking into a hoarder house cluttered with ads, rage bait, panic and AI slop. Just a total junkyard.

the JavaScript ecosystem be like:

I think going into 2026, as a developer, you'll have to accept that AI is "a thing" and won't go away. Take advantage of it or ignore it (if you can) but don't hope for it to disappear. I think there's a bubble that will burst at some point but that does not imply that the technology will disappear. It does have its use and it does change things. But just to be clear: AI is NOT that thing that will make you as a developer obsolete. Vibe coding is not the future for devs. It may be good for one-off, throwaway software but that's it. Instead, I convinced using & controlling AI assistants is the future. Just as we've used auto-completion before AI. Obviously, the amount of usage will differ on the problem you're tackling and it's easy to rely on AI too much. I've said it before: Don't limit your skill level to that of the AI you're using. Instead, combine your skill & knowledge with AI assistants. At least, that does work for me.

AI gives non-technical people the illusion of being technical.

Don't listen to the AI grift. Experience absolutely matters and is what separates a software engineer from a vibe coder.

Fale isso para o seu ceo/gestor não técnico: "Vamos combinar prioridades. Quando eu começo uma tarefa, o custo de parar no meio do caminho porque você trouxe outra tarefa é muito alto. Vai ser o tempo jogado fora, o custo de oportunidade de não ter colocado a feature no ar antes e o tempo que terei para lembrar do onde parei. "Então é importante você entender que, se a tarefa que você trouxer não for crítica, eu vou anotá-la e fazer logo quando eu terminar o meu trabalho em andamento. "Podemos seguir assim? "Se você não concordar, então que fique claro que a responsabilidade é sua de uma fila grande no desenvolvimento. E uma fila grande na engenharia acarreta em atrasos no desenvolvimento e, em algum momento, podemos demorar dias para mudar o botão de lugar no App."

Definitivamente hahahaha

Just met a company that vibe coded an entire CRM to avoid paying for HubSpot or SFDC over the last year. It’s now become a burden to maintain and missing key functionality / third-party interoperability as they scale… They’re now migrating to HubSpot. App layer is fine.