{"content_list": [{"text": "My thoughts on relying on AI workflows, end to end\n\nYes, it\u2019s not good in high impact cases\n\ni'm referencing a post that can be found here: [https://x.com/tnvmadhav/status/2113144717911490947?s=12](https://x.com/tnvmadhav/status/2113144717911490947?s=12)", "title": "My thoughts on relying on AI workflows, end to end", "slug": "my-thoughts-on-relying-on-ai-workflows-end-to-end", "description": null, "updated_at": "2026-10-22T05:50:02.858Z", "media": []}, {"text": "I've been using OpenAI's codex has my agentic harness application for personal use and at work too. And, I must say I've been tired of downloading new updates every single day on multiple devices.\n\nIt's like they ship something twice or thrice a day (at-least on the macOS desktop app). And, I've been wondering ever since.\n\nHow do they ship at this cadence?\nI get it that they have a large engineering team but still...\n\nSurely, they're doing something right.\n\nThat led me to question \"What does their SDLC look like?\"\n\nI asked this question into Codex itself!\n\nThe answer is not in this PDF but it's breadcrumb trail to the answer:\n\nhttps://cdn.openai.com/business-guides-and-resources/building-an-ai-native-engineering-team.pdf", "title": "I read about OpenAI's Native Engineering Practice", "slug": "i-read-about-openais-native-engineering-practice", "description": null, "updated_at": "2026-10-19T15:05:33.214Z", "media": []}, {"text": "I bought myself a copy of book on mobile engineering.\n\nBuilding Mobile Apps at Scale! by Gergely Orosz.", "title": "I bought myself a copy of book on mobile engineering", "slug": "i-bought-myself-a-copy-of-book-on-mobile-engineering", "description": null, "updated_at": "2026-10-04T11:38:53.506Z", "media": ["https://cpx.tnvmadhav.me/content/image/content-images/image_s10vFSm.png"]}, {"text": "First things first, I would like to open a file or folder in xcode, I need to do the following:\n\n```sh\nopen -a xcode \n```\n\nNow, that's out of the way, I need to figure out what the hell xcode does on top of your existing project...\n\nI see that a folder contains a `.xcodeproj` file? folder?.\n\nI always get confused with that is or why is it ever required.\n\nIf we open it using vs code, it turns out that it's a folder.\n\n```sh\nopen -a Visual\\ Studio\\ Code .xcodeproj\n```\n\nSo, an xcodeproj folder is context managing folder for your xcode.\n\nif you don't use xcode to build and distribute your apps, then this is entirely not necessary.\n\nAll of my personal iOS and macOS apps I have built in the past have been done so using Xcode, so I simply can't remove or drop the related .xcodeproj folder if I wanna keep the development and release flows same.\n\nInside a xcodeproj file, I found 3 more files and folders:\n\n1. Project.pbxproj\n2. xcsharedata folder\n3. project.xcworkspace\n\nProject.pbxproj is a 1 file containing the config context on files, references & dependencies etc. \n\nIf this is wired wrongly, then when xcode builds your app for release, things could go wrong.\n\nProject.pbxproj settings and config is responsible for how the files and folders are wired and show up in the xcode UI in our projects.\n\nand finally, Project.xcworkspace inside .xcodeproj should never be tampered with.\n\nIt contains information for running your xcode workspace and mainly won't contain changes to be commited to apps.\n\nHowever, swift package manager lock files should be commited.\n\n`swiftpm/Package.resolved`\n\nthis can change when adding or removing dependencies using swift package manager. \n\nall this, for doing something that go.mod and go.sum files do.\n\nfor a novice, this seems like a declarative hell. honestly.\n\nI really wish this isn't normalized.", "title": "Dealing with xcode \ud83e\uddd1\u200d\ud83d\udcbb", "slug": "dealing-with-xcode", "description": null, "updated_at": "2026-10-04T11:37:24.607Z", "media": []}, {"text": "I wouldn't say I was really proficient with github comments formatting but today I learnt how to create a collapsable section.\n\nand, it's pretty straightforward!\n\n```html\n
\nMore details:\n**the usual markdown gore**\n
\n```", "title": "TIL how to add collapsable section in a github comment", "slug": "til-how-to-add-collapsable-section-in-a-github-comment", "description": "", "updated_at": "2026-10-04T09:58:36.072Z", "media": ["https://cpx.tnvmadhav.me/content/image/content-images/image_vqD9e8L.png", "https://cpx.tnvmadhav.me/content/image/content-images/image_ZrwGEpE.png"]}, {"text": "I'm reading the Pragmatic Engineer Pulse newsletter...\n\nhttps://newsletter.pragmaticengineer.com/p/the-pulse-ror-creator-sparks-new\r\n\r\n\r\nThis edition talks about the following:\n\n1. The shock of DHH's positioning and words ofc (I agree with DHH overall positioning)\n\n2. The angst in small, medium and big tech where nobody knows or owns decisions (I too feel the same recently, I'm trying to change the way I work)\n\nThis hit me specifically. \n\nAt first, in early 2026, I felt that using AI for work would mean spend less time doing design and development and spend more time living life.\n\nNow that I'm leading a team, I am backtracking this thought right now. \n\nNo! When you are responsible in multiple areas, quality and speed, the work has increased significantly. More effort goes in to quality analysis. \n\nSo, for slow learners & fragile adopters of new tech, this is a warning call.\n\nMore effort needs to be put into place for getting this productivity in code generation in the right path to higher ROI.\n\nIt's a Gold Rush out there for people successfully navigating this wave and keeping their sanity while realising huge return of interest.\n\nOne thing I'm noticing, people who have maintained high standards in product quality through diligent integrity and practices aren't affected much by this. In fact, they are the ones riding this monstrous wave.\n\nThose who have been building software the \"right\" are way more resilient from facing downsides right now.\n\nThe Antifragile live on.", "title": "Reading the Pragmatic Engineer Pulse newsletter...", "slug": "reading-the-pragmatic-engineer-pulse-newsletter", "description": null, "updated_at": "2026-10-04T09:08:32.830Z", "media": []}, {"text": "Shopify is doing a migration to from legacy react native system to native builds for android and iOS.\n\nhttps://x.com/TnvMadhav/status/2098265718831890565?s=20\r\n\r\n\r\nsource: https://shopify.engineering/back-to-native", "title": "On shopify\u2019s codebase and feature migration to native builds", "slug": "on-shopifys-codebase-and-feature-migration-to-native-builds", "description": null, "updated_at": "2026-09-11T04:25:45.601Z", "media": []}, {"text": "shopify acquires tailwind \ud83d\ude26\nhttps://tailwindcss.com/blog/tailwind-is-joining-shopify\r\n\r\n\r\n", "title": "Tailwind posted that they\u2019re joining shopify", "slug": "tailwind-posted-that-theyre-joining-shopify", "description": null, "updated_at": "2026-09-10T04:15:56.959Z", "media": []}, {"text": "I had a nice meal last night \ud83d\ude0b #foodblog", "title": "I had a nice meal last night ", "slug": "i-had-a-nice-meal-last-night", "description": null, "updated_at": "2026-08-22T11:12:25.823Z", "media": ["https://cpx.tnvmadhav.me/content/image/content-images/IMG_7563.jpeg"]}, {"text": "> It will have strong privacy and security options so you can trust it to handle all of your personal content knowing that no one else can access your information, similar to how encryption works on WhatsApp\r\n\r\n\r\nhttps://www.meta.com/thefutureisforeveryone/#:~:text=It%20will%20have%20strong%20privacy%20and%20security%20options%20so%20you%20can%20trust%20it%20to%20handle%20all%20of%20your%20personal%20content%20knowing%20that%20no%20one%20else%20can%20access%20your%20information%2C%20similar%20to%20how%20encryption%20works%20on%20WhatsApp.", "title": "Zuck on Meta AI", "slug": "zuck-on-meta-ai", "description": null, "updated_at": "2026-08-11T05:02:21.597Z", "media": []}], "user": {"username": "tnvmadhav", "img_url": "https://pbs.twimg.com/profile_images/2048284096229670912/3n1wdkfP_normal.jpg"}}