25 karma · joined September 22, 2013
The best thing is very boring, but it's the best because I use it all day, every day, and it brings me joy: bringing all my text things to Emacs. Writing, project/task organizing, and email. Never thought I'd end up there.
She had a Windows Phone for years because you could zoom-in the tiles and thus increase touch targets for quick dialing. That eventually broke down, too, because of lack of haptic feedback and, well, we all can hardly imagine how hard it is to navigate a device like that when everything's so blurry you cannot see the space between huge-ass tiles on a, what, 6" screen or so.
She also can barely hear, so giving voice commands might work, but understanding the machine-generated audio feedback doesn't work. Also, she can't fix problems, like accidental activation. It's too overwhelming. And that's while she's technologically curious and adopted mobile phones and smartphones to some extent. She just can't use these things properly.
I bet we will have an easier time with these things because we learned how to use them while everything was fine.
I can imagine a primary source that’s important in your life becomes part of your knowledge, too, because you ... well, got to know it so well. But that really isn’t the point, since mere collecting is the opposite of familiarizing yourself with the material.
Do you have experience with this? Or moral arguments?
The first will incorporate the changes of the current view controller and make it accessible to whoever is interested -- and then the next view controller will show the current "model" state which in fact includes everything that was changed already.
I have another writing projects in the queue, so first, I'd like to get your honest feedback on the topic. There's not a lot of literature on maintaining Cocoa code. I'd like to change that.
What do you think of the book?