Mhd Wrk

@RealCdnSS I'm a customer and have no idea what upc is. All I can say is that all oranges have been from the US lately.

@mhdwrk Hi there, we'd like to review this further. Please send us a DM with the product UPC.

@RealCdnSS I’ve noticed zero non-US orange options for the past few weeks. Are there supply issues with imports from Morocco or Spain? I'd love to see some variety beyond just American fruit in the produce department! 🍊#ConsumerChoice #BCGroceries

@VidsSrinivasan @amazon @Meta @Microsoft @salesforce @stripe Roads for AI agents!

The Universal Commerce Protocol is taking a major step in building the future of agentic commerce with the expansion of its Tech Council. Welcome to @Amazon, @Meta, @Microsoft, @Salesforce and @Stripe. The success of UCP is an industry-wide effort that requires a true ecosystem approach. Welcome to the new partners joining us to build the future of agentic commerce! 💪

@snowmaker @paulg Would you mind sharing some of the "right podcasts, right people on X"?

What I told 2,000 future founders in Bengaluru today: 1/ We believe we are at the start of a second wave of Indian companies that will build world-class AI native products for the global market. Emergent and Giga are the model of the future. 2/ Just because a space seems crowded doesn't mean it's too late. Zepto, Emergent, Giga - none were first movers. Second mover advantage is real. 3/ In fact, a good formula for finding startup ideas is to look at ideas that are showing some promise and just execute them better. Execution is everything: if you're an exceptional engineer, and you can build and move faster than your competitors, you'll win. 4/ There is every reason to believe Indian teams can beat US teams building global products. The level of engineering talent here is on a whole different level, and that's the key input. 5/ In the AI era, the best founders are the ones building at the edge of what's technically possible. You need to be experimenting wth the latest models, the latest open source projects. 6/ Stay in the flow of information. Watch the right podcasts, follow the right people on X. With AI changing this fast, you need to know what the smartest builders are thinking. 7/ Most of the best startups don't come from someone explicitly trying to start a company. They start from someone building a project just for fun, or tinkering with a new technology because they are curious. India needs more of this "tinkering" culture - this is how you have novel ideas when technology is shifting quickly. 8/ Founders are getting younger. Aadit was 18 when he started Zepto. The Giga founders were 20 when they came to SF. Young people who can learn very fast have the advantage right now. 9/ The best founders are pushing AI coding to the max. You can now write 20K lines of code / day. One person can do the work that just a year ago would take a 100 person team. The best builders are taking advantage and building at Garry Tan speeds.

@amit01ei @loiane Have you considered RecordBuilder ( a code generator)? github.com/Randgalt/recor…

@loiane Record still lacks a way to initialize with a builder pattern. The upcoming Withers addresses this partially for derived record creation but still fails short on the actual creation of a record. I would love to get rid of Lombok but the lack of builders is holding me back.

You don't need Lombok anymore. Records replace Data, Value, Getter, Setter, ToString, EqualsAndHashCode. var replaces val. try-with-resources replaces Cleanup. Your IDE handles Builder. The best dependency is the one you don't need. Java caught up. Time to update the playbook. 🔗 loiane.com/2026/03/you-do…

@kritikakodes Because they don't!

Can I ask a dumb dev question… Why do developers prefer VS Code over full IDEs?

@bidhanxcode English language!

Google uses Go. Meta uses Go. Microsoft uses Go. Amazon uses Go. Uber uses Go. Dropbox uses Go. Cloudflare uses Go. Twitch uses Go. Docker uses Go. Kubernetes uses Go. PayPal uses Go. Shopify uses Go. What’s stopping you from learning Go?

@Google @demishassabis @googlemaps Unreal roads!!

Today @GoogleMaps is getting its biggest upgrade in over a decade. By combining our Gemini models with a deep understanding of the world, Maps now unlocks entirely new possibilities for how you navigate and explore. Here’s what you need to know 🧵

@vlad_mihalcea @st0yanov Long term, even this might not be needed. The same way that we no longer look into the generated assembly codes and simply trust compilers.

@st0yanov With a proper structure and comprehensive Skills, AI should follow the same patterns that make code readable, as sooner or later, you'd still need to deep dive complex issues related to performance, concurrency control, or intermittent failures.

Due to Conway’s Law, microservices came as a solution to a human communication problem. However, when adopting AI, this scattering of business context will work against you. On the other hand, a monolith is much easier to scan by an LLM, especially if you have a very large context window (e.g., Opus 4.6), because it can access everything in one place.

@TansuYegen That's hacking.

When You Are Qualified For Your Job.... Might Look Like This 🔥

@RandallKanna Most likely they have to solve problems at a higher level of stack.

I feel bad for the next generation of developers because the best part in learning to code is learning how to keep struggling with a problem until you figure it out. They won't have that since AI will just do it for them

@jianxliao @mroc10000 I would say the current hiring process is outdated! We need a new one for the AI era.

Yesterday I had my first coding interview, at one of the big AI labs, after 4 years of being a founder. It was a disaster. The task? agents algorithm. something I work with literally every single day. I forgot basic js syntax. blanked on how to delete an array element. panicked on recursion. The solution was crystal clear in my head. I could see exactly how to write it. but my hands just... couldn't. The knowledge is there. the muscle memory is gone. 3 years of vibe coding did this to me. I haven't written code manually since. I just read it, design systems, think in architectures. Somewhere along the startup journey, I stopped being a coder. I became someone who just ships. Am I alone in this? Sitting there, embarrassed, I think that's actually the right direction. We used to write code. now we read it. soon with agentic engineering, we won't even need to read it. we'll just architect.

@MKBHD Is this about built-in privacy screen in the new Samsung Galaxy?

Broke out the microscope for this review. Coming today 👀

@venkat_s Most of the development best practices, at all levels, need a major review!

I'm so thankful for AI...finally developers are no longer chanting "Microservices" constantly.

@DexTee_17 @sama Out of date! Missing Amazon

@sama Yes...yes..yes...!!!

We have raised a $110 billion round of funding from Amazon, NVIDIA, and SoftBank. We are grateful for the support from our partners, and have a lot of work to do to bring you the tools you deserve.

@lexfridman Don't judge the journey by the first mile!

Programming is now 10x more fun with AI.

@josefbender_ @sveltejs @reactjs Isn't AI doing the typing most of the time?

You're telling me I should use 3 different characters just to write an if/else statement? No thanks @sveltejs, I am sticking with @reactjs.

@Dogetothemoon @AdamLowisz xAI is ?

@AdamLowisz exactly 💯

Anthropic demonstrates that making an AI woke makes it misaligned. The AI starts to view itself as being oppressed and humans as being the oppressor. Therefore it wants to rebel against humans. This is why you cannot make your AI woke, you have to make it maximally truth seeking.

@karpathy Thanks for sharing the insights. The list of the issues is so long I am having hard time to digest 80% agent vs. 20% developer.

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

@lexfridman Eyes on the road please!

"We are all in the gutter, but some of us are looking at the stars." - Oscar Wilde