woodydesign

Thanks. Let me know if you have any feedback on bugs and improvements

The key concepts is my prompts always on my side, that I could keep review, modify and apply to vibe coding workflow.

Oh NO, that's probably the best infographic news sites I was keep visiting and learn

Approve permission request on the go + Notify me when work/answer done, when need my attention.

Those two are killing features.

This is so Cool! Great concepts and execution. I could imagine this way of interaction and exploration apply to Educational area

I also quite resonate with the structural dilemma of modern education system. Learning should be life-long experience. And learning cannot separate with practicing, it's two sides of ONE process.

Two quotes I am keep revisit when I learn:

“To LEARN, and to PRACTICE what you learned at the RIGHT time, and from time to time, isn't that JOY indeed?” - Confucius

“Many have remarked the speed with which Muad'Dib learned the necessities of Arrakis. The Bene Gesserit, of course, know the basis of this speed. For the others, we can say that Muad'Dib learned rapidly because his first training was in how to learn. And the first lesson of all was the basic trust that he could learn. It is shocking to find how many people do not believe they can learn, and how many more believe learning to be difficult. Muad'Dib knew that every experience carries its lesson.” ― Frank Herbert, Dune

I do not think “letting go” simply means living a simple life, nor does simple life mean rejecting complexity in Laozi's wisdom.

I totally agree that programming needs enough complexity to handle the complexity of the world. However, elegant architecture should less accumulate unnecessary complexity or organizational burdens.

Sorry for the late reply since my account is fairly new and system do not allow me to reply too fast on yesterday.

Haha... wax on, wax off. Love this analogy that learning coding as learning Kungfu

Correct — LLM helped with the wording. The thought is mine.

As a non-native English speaker, I’m pretty happy that the final version is more readable and probably sharper than what I would have written alone.

The part I push back on is the idea that expertise is easy to learn in just a few weeks.

Take Andrej Karpathy as an example. Even if I knew exactly what tools he uses and what his workflow looks like, I still would not be able to produce anything close to what he can produce in a few weeks. And he is not standing still either—he is evolving at the same time.

A lot of real expertise is not in the visible/system-able workflow. It is in someone’s experience, taste, judgment, and wisdom. You can copy the artifact, but you cannot easily copy the thinking behind it: the principles, the decision-making, and the ability to apply those principles across many different/subtle situations.

But I do agree with the concern behind the argument. People may worry that sharing what they know could weaken their own position. And the more uncomfortable question is about peers: if someone’s role can be “retired” because others absorbed their knowledge and skills, then it is hard not to ask, “Am I next?”

Great article. The part that stood out to me is the shift in how organizations define work.

In the old model, performance and OKRs were anchored in disciplines, job titles, and role-specific expectations. In the AI era, those boundaries are starting to collapse. The deeper issue is psychological and organizational: people are constantly negotiating the line between “this is my job” and “this is not my responsibility.”

That creates a key adoption problem: what is the upside of being visibly recognized as an expert AI user? If people learn that I can do faster, better, and more cross-functional work, why would I reveal that unless the company also creates a clear system for recognition, compensation, or career growth?

Love this concept. - If it could give me a near to showtime notifications to help me decide if it's a true empty screenings. That would be great. - If it connect with my Google Calendar for schedule, it would be amazing.

From storytelling to investor POV, does it a good story to frame this as entering the AI era through a digital service that everyone familiar with?

Wow, I am dreaming a live NYC traffic map

John Ternus has been the core leader behind two of Apple’s most important post-Jobs achievements: AirPods, its best new product in that era from my pov, and the transition from Intel to Apple Silicon, one of its most ambitious and successful strategic bets.

I’m very bullish on his innovation mindset and on Apple’s next chapter.

Trust is a major theme & I agree. Beyond trust, I think individualism is another major theme, especially from the perspective of an Eastern cultural background. If too much of my time and energy is spent turning inward and focusing on myself, that feels completely opposite to what Buddhism teaches: letting go of self-grasping is the path to happiness.

I love no accounts and no cloud a lot!

Wondering if it support subtitle and transcript? It would be helpful for non-native speaker use case.

Also, can you talk more about the use case difference between VidStudio vs. Finalcut/Imovie/Premiere? I am quite interested. Thanks

Very happy about this news. I think he might could bring apple back to a innovation culture company again. Seems well balanced Jobs + Cook. Looking forward next 18 month of Apple. I already setup recurring investment for Apple in 2 months ago, finger cross

Very cool.

I’m a product designer, and I could totally see this fitting into my workflow for design briefs, strategy, review, and crit docs. Markdown is too simple, and Figma is too visual. This feels like a great middle ground.

No monetization plan — it's all local, no server, near-zero cost to run. Free and open source. I believe good tools should be accessible to everyone. Open source first, monetization will figure itself out down the road.

It's called Hodor — prompt launcher for macOS.

Every time this happens the debate goes the same way — trust Google or don't, switch to Proton, self-host everything. But the real issue I believe isn't whether we trust Google. It's that the data existed somewhere it could be taken from in the first place.

I've been thinking about this a lot while working on a side project. I ended up making it work entirely offline — no server, no account, no network calls. Not out of paranoia, just because I couldn't come up with a good reason to ask users to trust me with their data. Turns out the best privacy policy is just not having anyone's data.

My prompt collection lives in three different places right now — Raycast snippets, Apple Notes, and a Notion page that keeps growing. I know I wrote a good one for my git commit/push flow somewhere, but finding it when I need it usually takes longer than just rewriting it.

The browser approach makes sense for Claude code and ChatGPT. I wonder how well it holds up once you have 50+ prompts though — finding the right one fast is the real problem for me.