Jagdev Singh

@SuperDuperInvst You are much better than all stock recommendation subscriptions

$ESLT $900 now 🤑

@BradoCapital Not able to DM you as I am not verified

Are you a cracked engineer and live in 🇨🇦 ? We're growing really damn fast. DM me.

@SumitM_X congratulations Sumit

After 7 months of interior work , finally I am moving in my new home today...

@SuperDuperInvst Shy followers

I feel like I’m talking to myself here. Very little coverage to show my tweets to others despite being a premium X member. None of my followers are fake or paid ones still I barely get any visibility 🤔 My follower base has been stagnant for so long while I see young models showing off their bodies on OnlyFans having way larger quickly growing followers 😂 Am I in the wrong business? Or to blame my shy followers? What’s wrong? Please do something as my content is helpful to X. What can help @X @elonmusk Will greatly appreciate favorable assistance. TIA 🙏🏼

@therealdanvega Saying video not available

If you're using Claude with Spring AI and not using prompt caching, you're overpaying. Here's how to set it up. youtube.com/watch?v=oBJQ_Y…

Debugging Lombok feels like debugging magic. Project Delombok turns that magic into real Java code you can inspect and debug. Even better: IDE plugins can show generated code instantly. Use Lombok for speed. Use Delombok for sanity. 🔧 #Java #BackendEngineering

@milan_milanovic I think send query arrow should be in another direction as user request data from read database. Response flow is correct.

𝗛𝗼𝘄 𝗖𝗤𝗥𝗦 𝗪𝗼𝗿𝗸𝘀 Most teams' stuff reads and writes into the same model. Then they scratch their heads when dashboards run slow and simple updates block each other. 𝗖𝗤𝗥𝗦 (Command-Query Responsibility Segregation) solves this by splitting a single model into two. Commands handle writes. Queries handle reads. Here's how you wire this up. 𝗧𝗵𝗲 𝗤𝘂𝗲𝗿𝘆 𝗦𝗶𝗱𝗲 You send a query to a 𝗤𝘂𝗲𝗿𝘆 𝗛𝗮𝗻𝗱𝗹𝗲𝗿. The handler fetches data from a 𝗥𝗲𝗮𝗱 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲, typically a denormalized store such as Redis or Elasticsearch, designed for fast lookups. No business logic lives here. You return data shaped for the UI, nothing more. 𝗧𝗵𝗲 𝗖𝗼𝗺𝗺𝗮𝗻𝗱 𝗦𝗶𝗱𝗲 You send a command to a 𝗖𝗼𝗺𝗺𝗮𝗻𝗱 𝗛𝗮𝗻𝗱𝗹𝗲𝗿. The handler validates the request, runs it through the 𝗗𝗼𝗺𝗮𝗶𝗻 𝗠𝗼𝗱𝗲𝗹, where business rules execute, and then persists it to the 𝗪𝗿𝗶𝘁𝗲 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲. This is typically PostgreSQL or another relational store built for transactions. The domain emits events to an 𝗘𝘃𝗲𝗻𝘁 𝗦𝘁𝗼𝗿𝗲. 𝗦𝘆𝗻𝗰𝗵𝗿𝗼𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻 A 𝗠𝗲𝘀𝘀𝗮𝗴𝗲 𝗤𝘂𝗲𝘂𝗲, such as Kafka or RabbitMQ, carries events from the write side to the read model. This is eventual consistency. The read side lags by milliseconds. Fiverr runs this exact setup: MySQL for writes, MongoDB for read-optimized views, and domain events flowing through RabbitMQ. 𝗪𝗵𝘆 𝗦𝗲𝗽𝗮𝗿𝗮𝘁𝗲 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲𝘀? When reads outnumber writes by 100:1, forcing both through a single pipe creates bottlenecks. Netflix used CQRS with Kafka and Cassandra for their Tudum fan site. They separated content ingestion from content discovery, so each could scale on its own terms. 𝗪𝗵𝗲𝗻 𝗖𝗤𝗥𝗦 𝗪𝗼𝗿𝗸𝘀 CQRS shines when read and write patterns diverge sharply. Think dashboards with heavy reads and rare writes. Think systems where queries need denormalized views but writes need transactional integrity. E-commerce catalogs fit. Analytics platforms fit. 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗦𝗸𝗶𝗽 CQRS introduces unnecessary complexity, and most systems don't need it. If you're building a straightforward CRUD app, you're overengineering. Apply CQRS to specific 𝗕𝗼𝘂𝗻𝗱𝗲𝗱 𝗖𝗼𝗻𝘁𝗲𝘅𝘁𝘀, not an entire system. The pattern pairs naturally with 𝗘𝘃𝗲𝗻𝘁 𝗦𝗼𝘂𝗿𝗰𝗶𝗻𝗴, where you store events rather than the current state. But that's another layer of complexity. Start with the separation. Add Event Sourcing only when you need the full audit trail.

@0xlelouch_ transaction rollback

You deployed a new feature that adds a row to the database, but 10% of rows are missing in production even though logs show successful inserts. What could cause this? [Real production mystery at Netflix]

@philippemnoel Hi @philippemnoel , I am available to work from February 23rd. I can work remotely from Vancouver. Here is my LinkedIn linkedin.com/in/jagdevsingh…

ParadeDB is hiring someone to come help build integrations. ORMs, RAG frameworks, PaaS, etc. Remote within US/Canada timezones, preference for PST. You'll work directly with me. It's the perfect time to join just ahead of the 1.0 later this year.

@SumitM_X I faced similar situation, for every object in json it was returning 200 attributes.After analyzing, found other system need only 4 attributes, it was a catalog data from a e-commerce application. Same time they don’t need entire catalog so added a filter.

As a frontend dev , You see 50 -100MB JSON responses from backend API. What's your next step ?

@SumitM_X If you skip first column of composite index, you skip the index, simple

Table has an index on (user_id, created_at). Query : SELECT * FROM orders WHERE created_at > '2025-01-01'; Will the index be used or not ?

@SumitM_X Yes , this is possible

Can an exception be thrown from a static block?

@karpathy Could you please share the names of the tools you are using?

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.

@SumitM_X I think this is due to missing order by clause.

As a developer , Have you ever thought : Why does SELECT * FROM orders LIMIT 10; return rows in different order each time?

@milan_milanovic Love the analogy !! History repeats

Strong engineers create C C creates good times Good times create Python Python creates AI AI creates vibe coding Vibe coding creates weak engineers Weak engineers create bad times Bad times create strong engineers

@SahilBloom Totally agree but nowadays hiring process doesn’t align with it!!

Underrated career advice: There's nothing more valuable than someone who can just figure it out. Do some work. Ask the key questions. Get it done. Repeat. If you do that, people will fight over you.

@SuperDuperInvst Agree, tax is hard earned money by rich people to help the nation and people in need. Every tax dollar should be spent wisely.

I am always happy to pay taxes contributing to the nation's progress. Again this year I be paying HUGE amount in income & capital gains tax but not happy at all given my hard earn money gets wasted in funding many of the fraudulent govt programs that offers freebies/grants/subsidies to undeserved people like the one for example we have been hearing recently about the outrageous scams by Somalis in MN & OH. I also don't like money getting wasted by the government in many unncessary ways including unnecessary wars. Do you all agree?

@jrouldz What do you think about $EPOW

After looking into solar, robotics, data and energy sectors last month I ended up adding $ONDS $TE $CRWV to the long term port And averaged up a bit on $TSLA (as it hit every category) I think this fit the bill pretty well and I feel better positioned headed into 2026 But I’m still, as always, searching for more opportunity I see everyone throwing out lists of (often the same) sectors and tickers for next year These lists seem to draw a lot of engagement 😅 I’ve really always been a money-where-mouth-is guy. So I’ll stick to talking about stocks I actually own on the main page If you want to see what I’m researching for new investments, it’s in the sub 😆

@SuperDuperInvst Happy holidays 🎄🎅

Happy Holidays & Merry Christmas 🎄 🎅 🎁 ❤️

@jrouldz Free rides

Unpleasant effect of living in a high rise: I can feel the building sway and shake in high wind 😵‍💫 my friend on higher floor has it even worse