Timo
@timohere.bsky.social
📣 Orkit.ai - Voice Assistant Platform
📆 On pause dayvy.com - Next-Gen Calender
👨💻 Sharing parts of my ride, thoughts, progress, learnings
🧑🎨 Former life as Ads/VFX Director
🌍 Roundtrip: Hamburg, London, Berlin, Countryside
📆 On pause dayvy.com - Next-Gen Calender
👨💻 Sharing parts of my ride, thoughts, progress, learnings
🧑🎨 Former life as Ads/VFX Director
🌍 Roundtrip: Hamburg, London, Berlin, Countryside
I would feed the links (or texts, not sure if the Apple docs are parseable by AIs yet) to an AI and start asking questions.
What are the most important X. And why and where. How do people Y? Why does Apple want us to pay attention to Z?
What are the most important X. And why and where. How do people Y? Why does Apple want us to pay attention to Z?
June 15, 2025 at 8:24 AM
I would feed the links (or texts, not sure if the Apple docs are parseable by AIs yet) to an AI and start asking questions.
What are the most important X. And why and where. How do people Y? Why does Apple want us to pay attention to Z?
What are the most important X. And why and where. How do people Y? Why does Apple want us to pay attention to Z?
Also, Emily Chang is a really good journalist. And she doesn’t quote Musk as „Elon“.
May 25, 2025 at 6:07 AM
Also, Emily Chang is a really good journalist. And she doesn’t quote Musk as „Elon“.
What is going on with Apple?
April 28, 2025 at 6:43 AM
What is going on with Apple?
Naming is so hard - in overcrowded namespaces everywhere.
I do really like this name. Many criteria fulfilled. Short, rememberable, story-telling, etc.
I do really like this name. Many criteria fulfilled. Short, rememberable, story-telling, etc.
April 25, 2025 at 10:51 AM
Naming is so hard - in overcrowded namespaces everywhere.
I do really like this name. Many criteria fulfilled. Short, rememberable, story-telling, etc.
I do really like this name. Many criteria fulfilled. Short, rememberable, story-telling, etc.
I actually write a lot of code, too.
Prompt results are often too far away from a working or efficient solution. Architecture becomes messy too soon.
Very close, but too often just not functional.
But in Typescript it becomes more of a rewriting or changing based on a good basis.
Prompt results are often too far away from a working or efficient solution. Architecture becomes messy too soon.
Very close, but too often just not functional.
But in Typescript it becomes more of a rewriting or changing based on a good basis.
April 13, 2025 at 7:10 AM
I actually write a lot of code, too.
Prompt results are often too far away from a working or efficient solution. Architecture becomes messy too soon.
Very close, but too often just not functional.
But in Typescript it becomes more of a rewriting or changing based on a good basis.
Prompt results are often too far away from a working or efficient solution. Architecture becomes messy too soon.
Very close, but too often just not functional.
But in Typescript it becomes more of a rewriting or changing based on a good basis.
Probably the most difficult aspect of working in different programming eco systems in parallel:
Dependency hell.
AIs are really good at taking over these parts.
Dependency hell.
AIs are really good at taking over these parts.
April 13, 2025 at 6:59 AM
Probably the most difficult aspect of working in different programming eco systems in parallel:
Dependency hell.
AIs are really good at taking over these parts.
Dependency hell.
AIs are really good at taking over these parts.
I work in 4+ languages now. With control and arch decisions still 100% on my end.
Will release two complex products this year.
Simply not possible 2 years ago. 🤯
Looking forward to this episode!
It’s easy to step into the not-yet-possible trap - happens to me all the time.
Will release two complex products this year.
Simply not possible 2 years ago. 🤯
Looking forward to this episode!
It’s easy to step into the not-yet-possible trap - happens to me all the time.
April 13, 2025 at 6:56 AM
I work in 4+ languages now. With control and arch decisions still 100% on my end.
Will release two complex products this year.
Simply not possible 2 years ago. 🤯
Looking forward to this episode!
It’s easy to step into the not-yet-possible trap - happens to me all the time.
Will release two complex products this year.
Simply not possible 2 years ago. 🤯
Looking forward to this episode!
It’s easy to step into the not-yet-possible trap - happens to me all the time.
In my recent particular work in Swift, being 8 years into it, the AIs were perfect discussion partners for me, even better in complex UIKit matters, than in SwiftUI.
Never really delivered working code architecture for me.
Typescript, Python, even Golang:
Entirely different story.
Never really delivered working code architecture for me.
Typescript, Python, even Golang:
Entirely different story.
April 13, 2025 at 6:56 AM
In my recent particular work in Swift, being 8 years into it, the AIs were perfect discussion partners for me, even better in complex UIKit matters, than in SwiftUI.
Never really delivered working code architecture for me.
Typescript, Python, even Golang:
Entirely different story.
Never really delivered working code architecture for me.
Typescript, Python, even Golang:
Entirely different story.
And that applies to phone carriers, too.
April 11, 2025 at 12:32 PM
And that applies to phone carriers, too.