Ken Kocienda

@kocienda
4.6K Followers
114 Following
648 Posts
Building TUG: AI-assisted software construction. Past: Founder at Infactory, 15 years at , inventor of iPhone autocorrect, author of “Creative Selection”.
projecthttps://tugtool.dev
tonight's beyond burger bolognese was pretty tasty
@jsnell Let me know if can help. Feel free to get in touch.
@jsnell I agree that the the definitive insider history of the creation of the iPhone hasn’t been written yet. Maybe you or I should buck up and write it. 😉
@jsnell Thanks for the mention of my book! ✌️

Quality matters more than quantity when it comes to code, but even so...

today was 🔥

156 files changed, 8828 insertions(+), 6847 deletions(-)
86 commits

Mac OS X Shipped 25 Years Ago - 512 Pixels

Apple Newsroom, back in 2001: “Mac OS X is the future of the Mac, and we hope it will delight our customers with its unrivaled power and ease of use,” said Steve Jobs, Apple’s CEO. “The Public Beta has generated incredible feedback and support from Mac users and developers, which has helped us to make […]

512 Pixels
pizza for dinner!

@gruber So many notes. Where to start? Let’s even forget the transparency. I wonder, is it:

- Dec 13, 2025
- 12/13/2025 (with looser letter spacing)
- 12/13/2025 (with tighter letter spacing)

@stroughtonsmith No autocorrect. Understood. Even so, from an ergonomic standpoint, I think that touching within the keyboard bounds should always “do something”. Touches are intent, even when coupled with inaccurate targeting.
@stroughtonsmith What happens if I touch or tap in those empty spaces between the keys and groups of keys? For touchscreen keyboards, I think that touching inside the keyboard rectangle should always produce a key click. In other words, it should be impossible to “miss”. Mouse-driven virtual keyboards can relax this, since targeting is so much more accurate.