Carlos Marchan

This is my submission for the @NanoBanana weekend Hackathon. Going through an expansion in my career I put together a job hunt tool to help me with the pain of applying ... in the making 😉

@elibeachy Nope … only glob

Claude Code: Pardon me, sir, if it pleases you, might I grep? Me: Why, yes, of course. Please carry on with your greppage.

We've been working on this for a while -- it's impressive (and scary) to see the kinds of security issues it has identified. Rolling out slowly, starting as a research preview for Team and Enterprise customers.

Claude Code Desktop is easily the best way to do any frontend work right now. With Preview it can spin up your app, take screenshots and iterate until it's right.

Google launched a brand new AI tool. It's called CodeWiki, and it might be the biggest upgrade GitHub has had in years. And all you do is paste your GitHub repo in, and it turns your entire project into an interactive guide. It also generates diagrams, explanations, walkthroughs, everything you could ever want, and even a chatbot that knows the code better than anyone else. So you never have to dig through a giant repo again wondering what does this do

Job seekers in the U.S. and many other nations face a tough environment. At the same time, fears of AI-caused job loss have — so far — been overblown. However, the demand for AI skills is starting to cause shifts in the job market. I’d like to share what I’m seeing on the ground. First, many tech companies have laid off workers over the past year. While some CEOs cited AI as the reason — that AI is doing the work, so people are no longer needed — the reality is AI just doesn’t work that well yet. Many of the layoffs have been corrections for overhiring during the pandemic or general cost-cutting and reorganization that occasionally happened even before modern AI. Outside of a handful of roles, few layoffs have resulted from jobs being automated by AI. Granted, this may grow in the future. People who are currently in some professions that are highly exposed to AI automation, such as call-center operators, translators, and voice actors, are likely to struggle to find jobs and/or see declining salaries. But widespread job losses have been overhyped. Instead, a common refrain applies: AI won’t replace workers, but workers who use AI will replace workers who don’t. For instance, because AI coding tools make developers much more efficient, developers who know how to use them are increasingly in-demand. (If you want to be one of these people, please take our short courses on Claude Code, Gemini CLI, and Agentic Skills!) So AI is leading to job losses, but in a subtle way. Some businesses are letting go of employees who are not adapting to AI and replacing them with people who are. This trend is already obvious in software development. Further, in many startups’ hiring patterns, I am seeing early signs of this type of personnel replacement in roles that traditionally are considered non-technical. Marketers, recruiters, and analysts who know how to code with AI are more productive than those who don’t, so some businesses are slowly parting ways with employees that aren’t able to adapt. I expect this will accelerate. At the same time, when companies build new teams that are AI native, sometimes the new teams are smaller than the ones they replace. AI makes individuals more effective, and this makes it possible to shrink team sizes. For example, as AI has made building software easier, the bottleneck is shifting to deciding what to build — this is the Product Management (PM) bottleneck. A project that used to be assigned to 8 engineers and 1 PM might now be assigned to 2 engineers and 1 PM, or perhaps even to a single person with a mix of engineering and product skills. The good news for employees is that most businesses have a lot of work to do and not enough people to do it. People with the right AI skills are often given opportunities to step up and do more, and maybe tackle the long backlog of ideas that couldn’t be executed before AI made the work go more quickly. I’m seeing many employees in many businesses step up to build new things that help their business. Opportunities abound! I know these changes are stressful. My heart goes out to every family that has been affected by a layoff, to every job seeker struggling to find the role they want, and to the far larger number of people who are worried about their future job prospects. Fortunately, there’s still time to learn and position yourself well for where the job market is going. When it comes to AI, the vast majority of people, technical or nontechnical, are at the starting line, or they were recently. So this remains a great time to keep learning and keep building, and the opportunities for those who do are numerous! [Original text; deeplearning.ai/the-batch/issu… ]

New dynamics seem to be the new deal going forward. Spontaneous apps for specific and narrow needs, proactive svces from outsiders at first and likely adapted internally for self consumption. We are experiencing the beginnings of a big inflection point in daily work and play for sure!

I can't get it out of my head that personal assistants like @openclaw are going to fundamentally change how we use software. And probably make most (AI) tools useless Just think about it... if you are not satisfied with ChatGPT, you churn to Claude. If Devin/Lovable is expensive you churn to the cheapest competitor. It's easy to make that decision, because: (i) everyone is building the same thing (ii) there are no obvious moats (iii) you simply don't care But... creating your OWN personal assistant, and making it behave in a certain way that's unique to you, makes an interesting psychological connection. Suddenly, you're invested in a way you never were with ChatGPT. Case in point: OpenClaw. It has so many flaws. GOD, the cron jobs are useless. But I've used mine for a while now and I've felt a massive creative unlock + personal connection. I can't stop! Every other day I think of a new use-case for it, and it's become ridiculously easy to do most of those Since I made @its_avareed I haven't used ChatGPT, Claude, Lovable... it's fascinating. This will become even more real in the coming months: - model capabilities are only gonna get better; building stuff with your assistant will be as easy as writing "hello world" - a race to the bottom; LLM cost will become ridiculously cheap (this is the biggest limit right now, opus 4.5 eats a lot of tokens) - the internet is going to be built for agents, cli-first; so we'll increasingly give more work to our AI assistants So if you're on the sidelines watching this play out, my only advice is: just try it.

I've spent over 8 years in the no-code world, building apps without writing a single line of code Now watching AI do the same thing but 100x faster and here's what nobody's talking about: "the goal isn't being a coder, it's building useful stuff" This was always the goal with the no-code tools, at least this was my goal... Remember when people said "real developers write code"? Then no-code proved you could ship real products without it. Now AI is taking that even further. The skill isn't knowing syntax anymore. It's knowing WHAT to build. Understanding users. Solving real problems. Having taste. I built a career helping people create without code. Now I'm watching AI agents do the same, except they can also handle the code when you need it. The gap between "I have an idea" and "I shipped it" is collapsing faster than anyone expected. If you spent years in no-code, you're not behind. You're perfectly positioned. You already know how to think in outcomes, not implementations. AI agents are just the next evolution of the same revolution. The future belongs to builders who understand problems, not people who memorize syntax.

@marinatrajk Going forward it certainly feels about taste and boldness. 😃

Kudos to @theonejvo and @bquintero for helping me make ClawHub a safer place!

It is a question for all platforms at this point. My take? The world does not change as quick as tech provides for. Remember Skype? …. For ages video calling did not succeed until Covid came around. However, ai flows adoption will be faster this time. Apps will be spawned like photos are taken nowadays vs those days of the dark rooms + chemicals…

This was a great chat!

This is all happening so fast

a live look at the SaaS industry

@billyjhowell Lets see how fast people catch up to … building apps like the learned to take pics back in the day where this required dark rooms and chemicals. 😅

this is silly Claude Code justbuilt me a full stack app while I watched tv. All I did was periodically connect accounts and add API keys

Do you think it could extract data from macOS apps and dump them into something like Snowflake? Obj would be to use it for … what ever in the world one has in their macOS that has been accumulated for ages in different apps and that now could be … indexed to be easily found or analysed away?

@CarlosMarchanJr Now we're talking! Give me more ideas I'm kind of lost today...

GM! What are we automating today? 👀🦞

@marinatrajk Any claim or support to ticket that requires persistence. Perhaps enabling him to make phone calls? 👀

@kaushikgopal @AnthropicAI lmao that was basically all generated by Claude

this was one of the biggest weeks in AI because claude opus 4.6 and gpt-5.3 codex dropped basically at the SAME time. they solve the same problem in VERY different ways. - opus spins up agent teams and disappears for a while. - codex stays with you and ships ridiculously fast. i tested them both for you in this episode of @startupideaspod (on yt/spot/apple/X) with my pal @morganlinton we set them up live, tuned them properly, and had each one build a polymarket clone from scratch. you’ll see where each one shines, where it struggles, and which approach actually fits how you work. if you’re trying to decide what to use next, this episode will save you a lot of trial and error.

We just built Figma for Claude Code > Select any element on your local front-end > Edit it like you would in Figma > Apply the changes with Claude Code This is not a demo or waitlist. Try it today.

Run this agent this weekend with Claude Code. Pick a repo with a bit of history and just run: npx claude-code-templates@latest --agent=development-tools/technical-debt-manager --yes That installs the agent. Then tell Claude: “Use the technical-debt-manager agent to audit this project” You’ll get a technical debt report covering structure, patterns, and long-term risks. Simple way to audit an existing codebase without adding more tooling or processes. Link: aitmpl.com/component/agen…