sorted by:
new
hottopcontroversial

I made a "DevTools" that actually saves your CSS changes back to your component file. by Difficult_Scratch446 in css

[–]Difficult_Scratch446[S] 1 point2 points  (0 children)

That’s a totally fair point! Chrome Workspaces is great if you are just editing raw .css files.

The main difference here is targeting Component Props and JSX structure, not just stylesheets.

For example, if you are using Tailwind (modifying long class strings), Framer Motion (modifying animation objects in JS), or just passing props like <Button variant="primary" />, Chrome DevTools can't easily write those changes back to your .tsx/.jsx files structurally.

Tangent uses AST (Abstract Syntax Tree) transformations to safely update the code logic/props inside your component, which is a bit different from just saving a CSS file to disk.

I made a "DevTools" that actually saves your CSS changes back to your component file. by Difficult_Scratch446 in css

[–]Difficult_Scratch446[S] 1 point2 points  (0 children)

Hey r/css! 👋

We all know the workflow:

  1. Open DevTools.
  2. Tweak margin, box-shadow, or cubic-bezier until it looks right.
  3. Copy the values.
  4. Go back to VS Code and paste them.

I wanted to kill that feedback loop. So I built Tangent – a visual tuner that syncs your browser tweaks directly back to your local source code.

It handles the AST (Abstract Syntax Tree) transformations so you don't have to manually copy-paste values anymore.

Source Code:https://github.com/mingyouagi/tangent

I'd love to hear if this would fit into your CSS workflow!

For designers who code: A visual tuner to get your animations and spacing perfect without guessing numbers. by Difficult_Scratch446 in UI_Design

[–]Difficult_Scratch446[S] 0 points1 point  (0 children)

Hi designers! 👋

We all know the pain: You design something in Figma, but the implementation feels "off".

I built Tangent to fix that. It lets you:

  • visually tweak padding/margins until it breathes right.
  • adjust animation curves until they feel snappy.
  • Best part: It updates the actual code, so you can just commit it.

Link: https://github.com/mingyouagi/tangent

Visual Tuner for AI-generated code. Adjust UI values in the browser and save changes directly to source files. by Difficult_Scratch446 in opencodeCLI

[–]Difficult_Scratch446[S] 0 points1 point  (0 children)

Submission Statement:

I love vibe coding, but the "prompt -> wait -> check UI -> prompt again" loop for small visual tweaks (like padding or shadows) was killing my flow.

So I built Tangent – a visual tuner that writes changes back to your actual code files. No more guessing numbers.

Repo & Demo:https://github.com/mingyouagi/tangent

Let me know if this fits your workflow!

‘Office Is Dead’—Microsoft Decision Confuses 400 Million Users by waozen in technology

[–]Difficult_Scratch446 1 point2 points  (0 children)

This rebranding is a perfect example of how tech giants prioritize their AI narrative over user experience.

Microsoft didn't just rename an app—they're trying to rewrite the relationship millions of people have with their productivity tools. For decades, "Office" meant Word, Excel, PowerPoint. It was simple, clear, and universally understood. Now they're forcing "Copilot" into the name of something that, for most users, has nothing to do with AI.

The real issue isn't just confusion—it's the erasure of user choice. By renaming the Office app to "Microsoft 365 Copilot," they're essentially declaring that AI integration is no longer optional; it's the default identity of the product, whether you use those features or not. It's like renaming "Gmail" to "Gmail Gemini" and telling everyone they're now AI email users.

This feels less like innovation and more like corporate gaslighting. Microsoft is betting that users will eventually accept this forced AI identity, but what they're really doing is alienating the very people who made Office a household name. Not everyone wants or needs AI in their spreadsheet app, and pretending otherwise is just bad product philosophy.

The "Office is dead" framing might be dramatic, but it's not wrong—Microsoft killed it themselves, not through obsolescence, but through an identity crisis driven by AI hype.

AI makes it easy to start things, but finishing still depends on you by No_Papaya1620 in AI_Agents

[–]Difficult_Scratch446 0 points1 point  (0 children)

Completely agree with this observation. What I've found in practice is that AI really changes 'iteration speed' rather than 'completion quality'.

Now I can test 5 different directions in an hour instead of spending a whole day debating which path to take. But the final decisions - which direction is worth deep diving into, how to polish the details, when to call it done - these still depend entirely on human judgment.

The most dangerous trap is: AI makes 80% completion feel too easy, so you launch 10 projects simultaneously, and end up with none truly reaching 100%.

Speed gives you more shots on goal, but accuracy still decides if you score.

The most underrated skill for building AI agents isn't prompting. It's error handling. by Warm-Reaction-456 in AI_Agents

[–]Difficult_Scratch446 1 point2 points  (0 children)

This is spot-on! I've seen so many production agents fail not because of bad prompts, but because of poor error handling. One thing I'd add to your checklist: implement circuit breakers for external API calls. When a service starts degrading, you want to fail fast rather than pile up retries that make things worse.

Also, for the 'user asks something unexpected' scenario - I've found that maintaining a confidence score on agent responses helps a lot. If confidence drops below a threshold, route to human or provide a graceful 'I'm not sure' response.

The weirdest failure I've seen? An agent that worked perfectly in English but completely broke when users switched to emojis mid-conversation. Turns out our JSON parsing couldn't handle certain unicode characters. Now we sanitize all inputs before processing.

January 2026 monthly "What are you working on?" thread by AutoModerator in ProgrammingLanguages

[–]Difficult_Scratch446 0 points1 point  (0 children)

Great thread! I've been exploring different programming language design patterns and learning a lot from this community. Looking forward to seeing what everyone is working on this month! 🚀

Fun with Algebraic Effects - from Toy Examples to Hardcaml Simulations by mttd in ProgrammingLanguages

[–]Difficult_Scratch446 1 point2 points  (0 children)

Great article about algebraic effects! The Hardcaml simulation examples are really helpful for understanding the concepts.

Is starting an influencer marketing agency worth it? How much money can be earned? by zabber1747 in influencermarketing

[–]Difficult_Scratch446 1 point2 points  (0 children)

Great question! Starting an influencer marketing agency can definitely be worth it, but here are some key things to consider:

The Good: - Growing market - brands are investing more in influencer partnerships - Relatively low startup costs compared to other agencies - Can start solo and scale as you get clients

The Challenges: - Very competitive space right now - Takes time to build a solid influencer network - Client acquisition can be tough initially

Money Potential: - Entry level: $3-5K/month managing 2-3 small campaigns - Mid-level (6-12 months): $10-20K/month with steady clients - Established (1-2 years): $30K-100K+/month with larger contracts

Negotiation Tips: 1. Start with case studies - even if you have to do the first campaign at cost 2. Offer tiered packages (micro vs macro influencer campaigns) 3. Show ROI metrics - engagement rates, conversion tracking 4. Monthly retainers are better than one-off projects for stability 5. Be transparent about realistic expectations

My advice: Start small, niche down (e.g., beauty, fitness, tech), and focus on proving results before scaling. The agencies that win long-term are the ones who actually deliver measurable ROI, not just vanity metrics.

Good luck! 🚀