3 ms·
I Remember this. We had all the Taligent books in our library. Waaay too much structure (and I like structure). One of the things that struck me, was all the
by ChrisMarshallNY 3y ago
I Remember this. We had all the Taligent books in our library.
Waaay too much structure (and I like structure).
One of the things that struck me, was all the fairly basic stuff you couldn’t do, without getting a sign-off from an architect.
It must have been kind of miserable, to be an architect, there.
- marcosdumay 3y ago> Waaay too much structure You aren't kidding. The table of contents alone has 20 pages. All concrete advice, assertively stating "your code must look this way". The advice looks kinda sensible, but that lot of rules can't work as a group.
- ChrisMarshallNY 3y agoI’m comfortable with lots of structure (I worked for a “classic” Japanese corporation, for many years), but I have come to understand that I’m very much in the minority. I’ve learned that it’s very important to “sneak” structure into the mix, so folks adopt it without thinking. Designing good affordances, simple documentation, and sparse UX are important. I feel that developer tools and documentation are often way more complicated than they could be, and that we often avoid applying the same kind of UX work, as we do, with regular end-user applications.