My only pain point, that I solved with a few lines of elisp, was to go to npmjs, to find the repo link for my dependencies. What's in `node_modules` may be compiled to an inscrutable blob and it's rare to find good library docs.
How's it life changing though? You have to know the package name already to do that. And if you're sitting on npmjs looking at the package already, then you're one click away from Github.
Furthermore... I don't host my packages on Github :-) Don't think that even works for mine.
I'm working on a sewing pattern software to make patterns with code. It has a bunch of useful features like chopping up the pattern into a PDF for printing. But the thing that really made this software nice to use is the timeline I implemented, where you can go back and see how the pattern is constructed with each segment. It makes debugging so much easier. I have it so you can put different curves into groups, so you can see how just the sleeve is constructed, for example.
I will definitely consider adding timelines to future software I make, it's an awesome feature.
I read the Design of Everyday Things and most of it was painfully obvious examples and was overly philosophical.
Design is solving problems so they're intuitive for the user. Obviously a door with a handle shouldn't be a push door, I don't really think you need to write a book about it. And the types of people creating bad design are generally constrained by cost, time, or practicality, not necessarily by education.
> Obviously a door with a handle shouldn't be a push door, I don't really think you need to write a book about it.
It’s common to illustrate principles with examples that appear obvious, i.e. that everyone agrees on, so that after having it conceptualized as a principle, you’ll apply it in less obvious circumstances. Many things are obvious only in hindsight.
> And the types of people creating bad design are generally constrained by cost, time, or practicality, not necessarily by education.
That’s not true, because a lot of flawed design is being promoted and defended in public as the thing to do.
> Obviously a door with a handle shouldn't be a push door, I don't really think you need to write a book about it.
And yet we've all encountered push doors with handles many times.
> And the types of people creating bad design are generally constrained by cost, time, or practicality, not necessarily by education.
Good design is far cheaper and easier than bad design in the long run. Being able to articulate the benefit of good design such that stakeholders provide the resources for good design is perhaps one of the most important reasons to have such an education.
uh, the fact that this is written down and carefully put in frameworks is a good thing. Otherwise you can say any academic book is intuitive. the fact that it sounds obvious means they're getting the message across. because lord knows it was needed and there's plenty of failed products and ideas because of shitty design.
And I would argue speadsheets still created more developers. Analytics teams need developers to put that data somewhere, to transform it for certain formats, to load that data from a source so they can create spreadsheets from it.
So now instead of one developer lost and one analyst created, you've actually just created an analyst and kept a developer.
Snow Peak has high quality clothing that isn't absurdly expensive. It's very nice and fits well. If you want something higher end I also like Norse Projects. If you want lower end look at Champion - specifically Reverse Weave.
I used to use Stylebot but I switched everything over to Tamper Monkey so all my CSS and non CSS related scripts would be in one place.
Tamper Monkey/Grease Monkey scripts are very portable too, I use my scripts in Safari on iOS via the UserScripts extension.
reply