SanDiegoNick

Whhaaaat

@ubong_ephraim Cool! tried it, could have users point it to their linkein for understanding qualifications,etc. or drop a resume

6 months ago, I got an email I wasn't expecting. And just like that I became jobless after 4 years of stable work. I won't lie, part of me was relieved. But that relief doesn't pay rent. When reality hit, I went back to job hunting. And I remembered why I hated it. So I built something with Agent 4 on @Replit I called it Watson. Watch the video. You'll want to know the full story.

A first one for me

DevOps is easy. People are what's difficult...

@jasondoesstuff hmmmm want to try this for a newsletter scheduled job I run for my wife (PharmD.) but I have it sending to her email now. Any ideas? wrote about it here. fromhomecoffee.com/project/pharma…

PROMPT // Create a 14-page horizontal-swipe editorial magazine as a single HTML file. E-ink aesthetic: monochrome only, Playfair Display for headlines, Source Serif for body, IBM Plex Mono for metadata. Page 1: Dark cover. Page 14: Dark back cover. Pages 2-13: The 12 most trending GitHub repos in the last [CHANGE TO DAY or WEEK] (search for them). Alternate light/dark pages. Each repo slide is a 55/45 split layout. Left: giant ghosted rank number, category tag, editorial headline, repo path, description. Right: star count at 6.5vw+, language tag, then a visible callout box (background tint + 4px left border) with a personalized "How to use this" note explaining how I should think about applying this repo to my work. Rules: 100vw x 100vh pages, CSS transform-based horizontal pagination, no scroll Arrow key + swipe + wheel + dot navigation Huge fonts. Headlines at 5vw+. Star counts at 6.5vw+. Body text at max(17px, 1.5vw). Nothing small. High contrast on dark pages. Body text at .85 opacity minimum. Callout text at .8. Nothing overlapping. Generous margin-bottom between all elements. 10vh bottom padding. Full-bleed edge-to-edge. No floating cards. No padding boxes. Think Monocle magazine.

Problem: New github repos drop too fast and I don't have time to figure out if they're relevant to me. Solution: Have Claude build me a "magazine" that summarizes most popular repos 📈 of the last week AND how they could be applied to my businesses ✅. Prompt below...

The difference between a cool Text To Speech demo and something I'd actually use is accessibility. If I can convert what I'm readying via TTS nearly instantly, I'm going to be a repeat user. Create friction or a pay wall and you lost me.

What makes a serious home AI setup great? What are you integrating together. Are you testing? Benchmarking?

@nyk_builderz I use deep research with Chat GPT, dump into .MD, then feed Opus for designing PRDs, requirements and testing, then sprints for incremental features to pass coding agents. I passed a 13-sprint plan to codex and apart from secrets input for APIs, it absolutely crushed it.

@Nick__Losee Imo Claude has to be the brain and orchestrator - codex is good for implementation but lacks reasoning

I’m running both Claude and Codex heavily, and one thing is clear: Usage limits are now a product surface, not a billing detail. If your workflow depends on one model, you don’t have an AI stack yet. You have a single point of failure. What’s your fallback stack today?

@Palak3312 Ask for UI from codex and you’ll still be turning back to Claude

Unpopular opinion: $20 on Codex goes a long way, but $20 on Claude is gone before you even notice.

@HowToAI_ @HowToAI_ What do you think are the implications of pointing agents at this tool with arduino guides/textbooks for reference? Custom Computer Vision use cases would be cool

I just found a website that lets you create, program and test electronic hardware. It even has pre-built projects to experiment and learn before building them in real life. 100% free.

@techhdive @bekacru I appreciate this take

design taste matters, but design curiosity might matter more. engineers who think they lack taste just haven’t spent enough time noticing why something feels off. with ai, you can now describe a problem, generate multiple solutions, and refine your judgment through iteration. it is something you can learn much faster now than before.

I never realized how rare good design is in software. If you’ve good design taste, you’ve incredible edge with AI

@Bhavani_00007 Claude: this sprint plan should have an MVP by week one and 4-6 for the remaining features Claude code: 😏

No Claude, this isn’t a 3-month project. We will finish it today☺

@devoznunes Free Speechify + Audible = VoxCast

Drop your startup 👇 I’ll pick the best and promote them for free to my 9k+ members community

@staysaasy @staysaasy I was there a bit ago, now noticing it more and more. What’s your next move?

It takes some real mfuckin courage to drop an obvious AI slop document on your manager's manager's desk. Respect to the person who just did it to me. This isn't gonna go particularly well for them, but respect all the same.

My wife asked why there’s not a claudette

@ashpreetbedi @ashpreetbedi I studied Systems Engineering and 100% agree… handoff to agents comes with more peace of mind if you build and give it SE design documentation, requirements and models for them to run with

New post: Systems Engineering Coding agents have lowered the barrier to writing code, but they haven't lowered the requirements of production software. Agentic software is just software. The agent replaces business logic. Everything else is the same. ashpreetbedi.com/articles/syste…

How are Businesses on Enterprise accounts mitigating risks for things like cowork and what this is?

@BawsaXBT Yes. Just depends if you’re building for others or self In production systems, updates shouldn’t get pushed immediately to Prod. Updates might sit on Dev server for days/weeks before being tested thoroughly and features are smooth. Regardless things might slip through cracks….

if you're new to vibe coding, this post is for you: i've been vibe coding for 4 months now. my only method of testing? testing locally. if it looks good, it works, cool. push to production. but, not once did AI tell me: "hey, you should probably stop doing that." so i finally setup a staging environment this month. > separate vercel + supabase > separate branches > separate database here's what it's changed for me: > localhost isn't testing. it's a demo for yourself. > staging is where you actually catch breaks. > shipping to real users with no middle step? that's gambling, not building. vibe coding gets you to "it works on my machine." but it doesn't get you to "it works for everyone." tldr; build a staging environment asap.

@NitinthisSide_ Genuinely liking the graphics for added info/subject overview

@Nick__Losee Sureee

🧵 Day 1/30 — #SystemDesign Most systems don’t fail because of bad code. They fail when traffic increases and architecture can’t handle it. Let’s start with the foundation of scalability: Sync vs Async systems.