Vincent Shen

I use Claude Code to ship my engineering tasks in weekdays, but its potential goes far beyond just refactoring or debugging code. I recently built a workflow where I can publish a complete song to YouTube using Claude Code from the CLI. The entire pipeline, lyrics composition, local AI music generation, cover art design, video assembly, and YouTube publishing,  runs from a terminal with a prompt and minimal human interaction.  What used to require coordinating across multiple tools, multiple skill sets, and multiple hours now takes minutes from a single interface.  But here's the bigger picture: this pattern applies everywhere. The same approach of chaining AI capabilities into end to end workflows is transforming content creation, marketing, research, design, and operations across industries.  We're entering an era where the competitive advantage isn't just knowing how to use individual tools. It's knowing how to orchestrate them into workflows that collapse entire pipelines into simple interactions.  What workflows in your industry are ready for this kind of transformation?  https://lnkd.in/gN_tR6tz PS: This post was generated using AI, and the quality of song could be better using models with more parameters, and better prompting maybe? but I used distilled model due to resource constrains.  #AI #FutureOfWork #Automation #ClaudeCode #MusicGeneration #Innovation #Productivity

16

This is fantastic news. The number of mysteries and performance problems caused by poor allocators (glibc malloc) is mind boggling. So in practice, many systems critically rely on jemalloc or tcmalloc and it was very sad to hear about meta abandoning the open development of jemalloc. It's great to hear that this decision has been reverted, and that there will be continued competition in the production-hardened allocator space 🎉.

60

2 Comments

Someone at work asked how I host my site & PWA on AWS. Do I run API GW? EC2? They were shocked how dirt cheap & simple it is. 📌 Steps: 1️⃣ Buy a domain (e.g. .dev on Google) 2️⃣ Route53 → create hosted zone → add AWS name servers in Google 3️⃣ npm run build → upload to S3 (static site) 4️⃣ Make bucket public (test via S3 URL) 5️⃣ CloudFront → point to S3 → add ACM cert for your domain 6️⃣ Route53 → point to CloudFront

23

6 Comments

CocoaPods is not deprecated, but Swift Package Manager (SPM) is clearly the future. While CocoaPods continues to work and is still supported, Apple has been consistently encouraging developers to adopt Swift Package Manager as the preferred dependency management solution. SPM is deeply integrated with Xcode, requires no additional tooling, and offers a simpler and more native workflow for managing dependencies. As a result, many modern iOS and cross-platform projects are gradually migrating away from CocoaPods. CocoaPods remains relevant for legacy projects, but for new development, SPM is the recommended path forward. #iOS #SPM #COCOAPODS

14

If coding agents struggle to work with your code so will humans. Agent friendly code bases, are also human friendly. Human co-pilots use agents to make your code base more agent and human friendly.

44

2 Comments

Hardware engineers right now: business as usual. Software engineers right now: refreshing LinkedIn every 30 minutes. AI can generate code. AI can't manufacture chips. The irony: the people building AI infrastructure have job security. The people using AI tools to be more productive are getting cut. Physical constraints protect jobs. Digital abundance doesn't. The market is telling you where to invest your skills. Visibility matters. Relationships matter. Having options before you need them matters most. Source: https://lnkd.in/gahzATXv

3

Two Things I'd like to have on 𝗚𝗼𝗼𝗴𝗹𝗲 𝗙𝗶𝗿𝗲𝗯𝗮𝘀𝗲 𝗔𝗽𝗽 𝗛𝗼𝘀𝘁𝗶𝗻𝗴. Firebase App Hosting is the new Google solution for deploying Node.js apps, I’ve been using it and I love it. It simplifies deployments on Google Cloud (forget about Cloud Run), and is almost one shot to deploy, AI, env vars, secret management and full integration with any cloud. But as a new product, there are a couple of things that could be improved in benefits of developers, here we go.. 1️⃣ 𝗔𝘂𝘁𝗼 𝗴𝗿𝗮𝗻𝘁 𝘀𝗲𝗰𝗿𝗲𝘁𝘀 𝘁𝗼 𝗮 𝘀𝗶𝗻𝗴𝗹𝗲 𝗯𝗮𝗰𝗸𝗲𝗻𝗱: When a secret is added to a single backend using the CLI, it grants permissions to all backends, which is a blanket access issue. 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: The grant could be added in the first step, to a single backend, and keep it as a least privilege. 2️⃣ 𝗕𝘂𝗶𝗹𝘁-𝗶𝗻 𝘀𝗲𝗰𝗿𝗲𝘁𝘀 𝗶𝗻𝘁𝗲𝗿𝗽𝗼𝗹𝗮𝘁𝗶𝗼𝗻: We need to repeat the secret values many times, for example dbUser, dbPassword are repeated in dbUrlString. 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Add support for secrets interpolation, it simplifies a lot. dbUrlString='${dbUser}:${dbPass}/myDb' 3️⃣ 𝗖𝗼𝗼𝗸𝗶𝗲 𝗶𝘀𝘀𝘂𝗲 𝗼𝗻 𝗙𝗶𝗿𝗲𝗯𝗮𝘀𝗲 𝗦𝘁𝘂𝗱𝗶𝗼:  When running the Node.js app on Firebase Studio, it doesn't handle cookies correctly and it makes it unstable for session management. When running the app after deployment it works correctly, ping me and I can demo it. 💬 Have you used Firebase App Hosting yet? Share tips below! ----- ♻️ Helpful? Repost! 👍 Follow Carlos Echeverria. #ai #agent #prompts #LLM #developer Google Firebase Studio Firebase

2