Making Software
31–40 of 105 posts
Re: Making Software
#32Earlier quoted context omitted.
Agreed, it's aesthetically beautiful. It should be a coffee table book. But for the web, it has terrible usability. Really, really terrible in multiple ways. My comments will be harsh, but since the creator is obviously very skilled, he should know better. Why multicolumn text? So it looks like an old printed manual? At first view, it's not clear where the first column ends. This is not something we see on the web (b…
> Justified text is bad on the web. Is there any reason why justified is okay printed but not on the web.
Re: Making Software
#33Re: Making Software
#34Re: Making Software
#35Re: Making Software
#36Nice landing page, but I'm confused. The header is about software, but many diagrams are about hardware.
Re: Making Software
#37Re: Making Software
#38The author should make a meta-entry about how he makes the (insanely beautiful) diagrams in the book (ideally walking through the process).
Re: Making Software
#39The author should make a meta-entry about how he makes the (insanely beautiful) diagrams in the book (ideally walking through the process).
07 How do you make the illustrations?
By hand, in Figma. There's no secret - it's as complicated as it looks.Re: Making Software
#40Stunningly beautiful landing page. I would never normally comment on the aesthetics of anything in the dev sphere but that completely blew me away. I'll preorder for sure. I'd echo the other comment mentioning that a coffee-table version of this would be great.
Agreed, it's aesthetically beautiful. It should be a coffee table book. But for the web, it has terrible usability. Really, really terrible in multiple ways. My comments will be harsh, but since the creator is obviously very skilled, he should know better. Why multicolumn text? So it looks like an old printed manual? At first view, it's not clear where the first column ends. This is not something we see on the web (b…
Your other criticism I agree with.