Mathankumar

@Chaintweter @IamNaSen I got this same model for 3k last year, I iron things on demand, when am about to leave for work. this is handy can do in few mins without much effort.

@mathankumarc @IamNaSen அப்பிடியா? இதே பிராண்ட்ல விலை கம்மியானது இருக்குனு நினைக்கிறேன். எனக்கு இது தான் வசதி... அசால்ட்டா 20-30 துணி தேய்ப்பேன் இதுல

டேபிள் ஆடாம வசதியா உக்காந்து ஐயன் பண்ணலாம், அந்த ஆன்டனா மாதிரி இருக்கத்துல வயரை குடுத்து மாட்டிட்டு டிஸ்டர்பன்ஸ் இல்லாம தேய்க்கலாம் amzn.to/4bzJIYm

@Chaintweter @IamNaSen worth the price, during sales you can get this for around 3k.

@IamNaSen Yeh, அதை விட கம்மியா வாங்குனா strong ஆ இல்லாம ஆடுது... நான் இது தான் யூஸ் பண்றேன்... நல்லாருக்கு

I'm not very happy with the code quality and I think agents bloat abstractions, have poor code aesthetics, are very prone to copy pasting code blocks and it's a mess, but at this point I stopped fighting it too hard and just moved on. The agents do not listen to my instructions in the AGENTS.md files. E.g. just as one example, no matter how many times I say something like: "Every line of code should do exactly one thing and use intermediate variables as a form of documentation" They will still "multitask" and create complex constructs where one line of code calls 2 functions and then indexes an array with the result. I think in principle I could use hooks or slash commands to clean this up but at some point just a shrug is easier. Yes I think LLM as a judge for soft rewards is in principle and long term slightly problematic (due to goodharting concerns), but in practice and for now I don't think we've picked the low hanging fruit yet here.

im fully convinced that LLMs are not an actual net productivity boost (today) they remove the barrier to get started, but they create increasingly complex software which does not appear to be maintainable so far, in my situations, they appear to slow down long term velocity

yeah it is but everything in moderation. Internally we always talked about main quest and side quests. Everyone should focus on the main quest, and moderately or not all on side quests. Both quest lines feel productive but only one of them advances the main mission of the company.

Sage observation from @karrisaarinen (CEO of Linear) It now makes SO MUCH sense why I see a bunch of eng teams rebuilt a SaaS vendor in-house with AI, brag about and feel good They are doing side quests... and they don't even know it. And they are not helping their co win!!

@ipriy_a LG, Daikin. Not sure if you really need an 2 ton, most often 1.5 ton is far enough. Reason is usually 1.5 ton tend to be cheaper as its a sweet spot and most folks buy it, where as 2 ton tends to be costly since demand for it is less in domestic.Which ever brand choose min 4 star

Makkale, Suggest a good 2 ton AC for home use! Thanks in advance..

We partnered with Mozilla to test Claude's ability to find security vulnerabilities in Firefox. Opus 4.6 found 22 vulnerabilities in just two weeks. Of these, 14 were high-severity, representing a fifth of all high-severity bugs Mozilla remediated in 2025.

Released today: /loop /loop is a powerful new way to schedule recurring tasks, for up to 3 days at a time eg. “/loop babysit all my PRs. Auto-fix build issues and when comments come in, use a worktree agent to fix them” eg. “/loop every morning use the Slack MCP to give me a summary of top posts I was tagged in” Let us know what you think!

@MyntraSupport My order is delayed by more than two weeks now and complete silence from your end, even after following up through chat.

Anthropic pointed Claude Opus 4.6 at some of the most heavily fuzzed open source codebases in the world, projects with millions of hours of CPU time behind them, and found 500+ high-severity vulnerabilities. Some had been hiding for decades. Instead of throwing random inputs like traditional fuzzers, Claude reads code like a human researcher, spotting patterns from past fixes and reasoning about what inputs would break logic. They've started reporting and patching. This is the moment AI tips the scales toward defenders in cybersecurity. red.anthropic.com/2026/zero-days/

Introducing Claude Opus 4.6. Our smartest model got an upgrade. Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta.

This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.

We hacked the AWS JavaScript SDK, a core library powering the entire @AWScloud ecosystem - including the AWS Console itself 🤯 How did we do it? Just two missing characters was all it took. This is the story of #CodeBreach 🧵👇

The more I use these agents (that now do write code that is pretty good, but ofc I need to verify and keep them in check), the more I feel we're going to see the "Microsoft Frontpage" moment in tech: Frontpage DID make every and all web devs redundant in 2007. As we all know.

Myself and @OpenAI Codex5.1/5.2 found a Node DoS - CVE-2025-59466 -- #uncatchable-maximum-call-stack-size-exceeded-error-on-nodejs-via-async_hooks-leads-to-process-crashes-bypassing-error-handlers-cve-2025-59466---medium" target="_blank" rel="nofollow noopener">nodejs.org/en/blog/vulner… I almost completely outsourced all the work to codex for this one!

"I don't like pull requests (PRs) any more. A large chunk code change doesn't tell me much about the intent or why it was done. I now prefer prompt requests. Just share the prompt you ran / want to run. If I think it's good, I'll run it myself and merge it." - @steipete wow

We just published 6 CVEs identifying security vulnerabilities in React Router and Remix v2 We recommend updating to the latest appropriate versions: React Router v7 -- 7.12.0 React Router v6 -- 6.30.3 Remix v2 -- 2.17.2 Details, links, and package ranges are listed below

@JioHotstar tried to redeem a voucher as my existing subscription is ended(reverted to jio mobile recharge default plan), however you guys are asking me to sign out from every other device to redeem a voccher. Had to login to every other device again!

An incredibly awful security vulnerability just got revealed in MongoDB. So much that it got named after HeartBleed. MongoBleed is a vulnerability affecting all MongoDB versions from 2017 to... today. The exploit is simple. It's a buffer over read bug due to compression. Here's how it works 👇 Clients can send compressed requests to MongoDB. The client helpfully includes the uncompressed size of the message so the server knows exactly how much memory to allocate when decompressing. The server allocates a memory buffer with the given space. Due to how memory management and garbage collection in programs work, this allocated memory may already contain sensitive information that was copied earlier and is considered garbage now (eg because it's unreferenced). This is technically fine - every computer program works that way because it is assumed that whatever unclaimed memory exists there will be overwritten. Unfortunately that’s exactly where the bug lies. 🙃 The server stupidly trusts the client’s provided uncompressed size. When a malicious client lies about the uncompressed size - e.g the actual decompressed size is 100 bytes, but the client says its 1MB - Mongo will treat the full 1MB block as the message. It will unload the 100 byte decompressed msg into the buffer, yet treat the full 1MB block as the msg. This is extremely problematic if you can get the server to return back parts of the 1MB block, because it could contain data you may not have access to. That is exactly what the exploit does - it sends a badly-formatted BSON message. The server fails to parse it, and "helpfully" returns an error message containing the invalid message. The invalid message can be that whole 1MB block of foreign data. To understand the exploit a bit better, you need to understand the MongoDB protocol. • Mongo also uses its own TCP wire format (i.e doesn't use HTTP, gRPC or the like). • BSON is Mongo's message format passed within the TCP wire format. BSON is basically JSON in binary form • Commands in Mongo don't have particular endpoints or RPC names - rather, they are simply JSON-like messages. The action is inferred from the first key of the JSON. For example, an insert request looks like this: `{ "insert": "users", "documents": [ { "name": "alice", "age": 30 } ] }` Every request to the server is therefore decoded into the BSON format as it’s parsed. Critically, BSON parsing of field names (which are strings) work by parsing the field until you hit a null terminator byte (0x00). It works exactly like strings in C, which have their own rich history of vulnerabilities. We can now tie things together: 1. The client lies to the the server that its request has a big uncompressed size, so the server allocates a large block of memory 2. The client sends an invalid BSON with a field which does NOT contain the null terminator (0x00) 3. The server naively tries to parse the BSON field in that allocated block until it hits the first null byte. The first null byte is encountered in some foreign data since the BSON literally doesn't have it 4. The server realizes this is a completely invalid BSON message so it responds with an error. 5. The error response contains the invalid BSON "field". Critically, the server parsed garbage data from the heap in step 3), so it returns that data in the response. Congrats. If the garbage contains passwords or other sensitive info, you’ve hacked MongoDB! Hackers exploit this by sending many malicious requests per second and then attempting to reconstruct the pieces of garbage they received back. What’s critical about this vulnerability is that it works on ANY internet-accessible unpatched instance of MongoDB. 💀 You don’t need to authenticate with the server, because this whole request/response parsing cycle happens before the server can even authenticate. Obviously you can’t authenticate a malformed request which doesn’t contain credentials - so that path of the code never gets executed. The server simply responds with an error response. It just so happens that this error response can contain sensitive data. 🤷‍♂️ Merry Christmas