Windframe

✨Introducing design system presets in @getwindframe Instead of generic UI Windframe now generates designs grounded in the principles of companies known for great design. First up: Linear's design language. More design systems coming.

@Prathkum Complexity only helps when it removes real friction.

I’m amazed to see developers’ AI workflows: a lot of mcps, agentic workflows, multi-agents, and tool integration. Meanwhile, I use AI like this: give prompt, get code, review, and merge. 👀

@AnthropicAI AI doesn’t reduce mastery by default. Poor workflows do. The tool just makes the difference more visible.

AI can make work faster, but a fear is that relying on it may make it harder to learn new skills on the job. We ran an experiment with software engineers to learn more. Coding with AI led to a decrease in mastery—but this depended on how people used it. anthropic.com/research/AI-as…

@TomHughesx Build faster without losing control.

You've got 5 words. Why should people follow you?

@Star_Knight12 Even with AI, progress would still come down to how people used it.

what if our ancestors had access to AI

@esther_confused You’re not a middle man. You’re the interface.

my coding life nowadays: founder told me what do fix, I copy paste their words in my ai. feel like a profitable middle man

@bewithgeodev Because for a long time, writing code was how seniority was measured. AI changes how work gets done, not who understands it.

Why do senior developers feel odd admitting they use AI to write code? What’s the big deal? I’m a senior software engineer and I use AI a lot just in a more experienced way. That’s the difference. #tech #coding #ai

@LaurenSieckmann The leverage is real. But building “anything” still requires clarity, judgment, and follow-through. AI lowers the barrier, it doesn’t remove the work. That’s where solo creators really win.

I don’t think enough people realize that with AI, you can literally build anything now It’s the era of the solo creator

@_devJNS Calculators didn’t replace maths, they changed what we spend time on. AI is doing something similar.

Ignoring AI is like refusing a calculator because you’re “good at math.”

@csaba_kissi AI is becoming part of the default workflow, not a shortcut. The difference is still how you use it.

Writing code without AI today is like coding without Stack Overflow in 2010.

@damengchen AI has definitely improved. But the value isn’t that it writes better code, It’s that it lets experienced engineers focus on intent and decisions. Riding the wave matters, so does staying in control of it.

The beautiful part of living in the AI era, I still do what I do, or even less, but AI writes better code. I can clearly feel that, from a year ago to now, AI writes much better code. Just make sure you ride the wave, that's all you need!

@kylegawley Because tools don’t create businesses. Distribution, timing, judgment, and execution still matter. AI helps with speed, not guarantees.

if AI is so good why am I not making $100,000,000 MRR?

@nicbarkeragain AI doesn’t make you better or worse by default, It just exposes how much thinking you’re still doing. Used well, it sharpens skill. Used blindly, it erodes it.

You have to admit these two widely accepted beliefs are funny: - you must use AI programming tools to avoid being left behind - using AI programming tools makes you a worse programmer algebraic substitution: "to avoid being left behind, you must become a worse programmer"

@_trish_xD It can look that way on the surface but the fundamentals didn’t disappear, they just show up differently now. Web and AI sit on top of the same foundations.

computer science is mostly web dev and ai now.

@codewithantonio This is the part many conversations miss. Using AI well isn’t about autonomy, It’s about intent, architecture, and supervision.

i've been using AI to write 99% of my code recently but probably not in the way you think, and definitely not in a "AGI is here" way more in a "a decade of writing code by hand allows me to accurately describe to LLMs what I need" way or in a "a decade of making architectural decisions allows me to carefully make LLMs output the same" way i am not letting AI run autonomously, i feel like that defeats the whole purpose i am still the architect, the composer, the pilot, with both hands on the wheel, but there is little to no need at all for me to code by hand anymore i am still using all the knowledge i've acquired over the years, and i am using the same approach for building new projects and features as i did before i think vibe coding is an entirely different sport from this, and this is where most of the AI vs non-AI arguments diverge i don't understand the move towards having "as little human intervention as possible" when it is an incredible experience to have an expert, a human, supervise a robot who never sleeps and who's quality of output by a big margin correlates to expert's input i also don't understand the move towards "everyone using AI to code has skill issues" when i am creating the exact same thing i would without AI, just that much faster when was i able to generate 10 files at once before? why would i not use this ability? why do i have to be slow? what is the difference between reviewing my colleague's 10 files in a pr, vs reviewing my AI's 10 files in a diff? talking about this always brings up some angry emotions, so let me end with this: knowing how to code in this day and age is more important than it's ever been purposely avoiding AI in coding is doing nothing but a disservice to yourself

@csaba_kissi AI tools don’t replace fundamentals, they reward people who already have them.

Learning AI tools is a career multiplier, not a shortcut.

@catalinmpit AI reflects how clearly you think, not just what you type. The better your understanding, the better the output.

Might sound crazy, but AI generated code is a reflection of your skills. If you’re decent at coding, you can get good results with it.

@upen946 Most products fail long before code quality becomes the issue. If no one sees it, no one uses it.

Startups don’t die because of bad code. They die because no one knows they exist.

@ishaansehgal This resonates more than people want to admit. A lot of engineers didn’t fall in love with output, they fell in love with craft. AI should support engineering, not replace the parts that make it meaningful.

Talked with a senior engineer who's been coding for 15 years. Loved the craft, mentored juniors, built systems from scratch. Just quit. Here's what broke him: His entire job became prompting AI and reviewing generated code. The actual engineering, the part he loved, disappeared.

@Prathkum AI didn’t kill development, It exposed what actually matters.

AI killed the illusion that knowing how to write code is what makes you a developer.