I do most of my work these days just in my notes - writing self reflecting questions, planning, using the a lot question "if this will go wrong - what will be the reason?" (inverting the problem) Once the notes are written, I manually extract a general product spec from it again in notes. Then I take the product spec to the LLM and it just implementes, quite quickly all the things that it might have taken me a week+ to think about. Something that helps with planning is having the llm build mockup pages - just so that it will be easier for me to imagine and think how the solution might look like and what imporatnt, underlying factors or details i might have missed

Totally spot on. It sometimes feels normal that we can talk to a computer and it responds intelligently, but just 3 years ago that was fantasy.

Num. 2 especially relatable. A good mark of high quality professional is if he presents his plan before execution to hear feedback and comments - even if they are totally against his original idea, and he can then take this feedback and incorporate effectively in a re-design.

This does not always work.

Often, the group members presented to, do not have the required knowledge to critique the design document.

I have seen people proposing (demanding even) changes based on vague feelings and their need to be seen as contributing.

Once they say something, it is out there, now it is the poor presenter who has to refute it or accept modifications to the design.

If they don't have the required knowledge before coding, how are they going to have the required knowledge if you skip the design and just hand them the finished code?

For me the term users sometimes sounds similar to traffic. I prefer customers - that you serve with your product.

The term "user" maybe made sense before any software was commercialized. It differentiated the programmer of the software from the non-programmer that used the software. Even then it was sometimes used derogatorily (especially when people were sneered at as "Lusers"). In the original Tron the Good Guys had to fight for the users.

Customer is a much nicer term. Words do matter.

Even in a commercial context they aren't the same. The user is who sits in front of the screen, and the customer is who you have to please to make money.

You're right. But, nowadays these terms get more context meaning. For example - a user is someone who platforms sell their data to customers. Or a user is someone gullible you trick into making decisions that are good for the business. The literal term of someone who is using your system/product has evolved.

Interesting, thanks

Interesting, thanks for the reference. I wonder what other products do this

1000 true fans and Seth Godin's approach to marketing - that you should focus on the smallest group of people in your market and amaze them

These concepts helped me a lot with marketing to consumers and SMBs

Also, follow @mtlynch's content - even though he says he's not an expert, I feel that atleast regarding marketing to devs and builders - he is one of the best out there

Thanks for your work Michael!

You mean Vulkan? In the blog post there is reference to all vulkan supported platforms

If you mean ffmpeg build with whisper - from memory I didn't see ffmpeg-builds for mac, so you will probably need to compile yourself

This is a 3 part series, the first one discusses the new native whisper integration. And correct, for the first post - the point is to show that you can only use ffmpeg to transcribe and embed subtitles in a video

While there's appeal in having one tool do several things I'm more a fan of the traditional UNIX philosophy that a tool should do one thing, do it extremely well, and allow for chaining of several tools together to achieve a multi-step process.

I tend to agree. The thing I like most about version 8 is actually pad_cuda - nice performance boost for resizing video with an Nvidia GPU