mpetrovich
https://gist.github.com/mpetrovich/b3e4ec291d21bbdbe17b1adf4...
However, it was equally important that I had a support structure & tools to replace what the SSRI was doing. For me that was mindfulness and therapy.
If the founder had started by talking with people in the problem space, he could have discovered what problems were actually worth solving before investing any money and effort into a product.
Everything after that happened were downstream effects of creating something without a defensible reason why and for whom.
Maybe you’ll find it helpful
Looks interesting, best of luck!
It uses puppeteer and chrome headless behind the scenes.
Seems like a matter of crawling the former to get all the images and then tagging them and serving them via your API.
Anyway, I think your approach is great and only wanted to propose a possible approach to the original feedback above :)
“Hold on, there’s a bee on my arm”
They can be terribly leaky abstractions. It seems that many ORMs end up re-implementing SQL in their own domain-specific language.
However, an understanding of SQL is often needed to debug and optimize ORM queries.
So why not just use SQL directly then?
I prefer improving things rather than creating them from nothing. I’ve come to a similar conclusion as the author as far as how to get out of the fog of greenfield: Satisfice instead of optimize.
In this context, optimizing refers to choosing the best among N options. In contrast, satisficing means choosing the first option that’s good enough. Often, the opportunity cost saved from satisficing is greater than the marginal value gained from optimizing.
That certainly addresses the footgun I mentioned.
EDIT: From the docs: Requests without the X-GitHub-Api-Version header will default to use the 2022-11-28 version.
And it would annoy me far more if my app that talks to GitHub inexplicably breaks in a few years because of a release I wasn’t aware of.
These changes make no sense to me.
There’s zero practical user benefit to NOT specifying the version, so why not enforce it? You’re creating a footgun otherwise.
Furthermore as others have pointed out, this is a purely cosmetic change. Using /api/$UNIQUE_STR in the URL vs. X-GitHub-Version: $UNIQUE_STR in the header are functionally equivalent, so…
Why bother making this change then? What was suboptimal about the previous way? What benefit does this bring?
I’ve moved a ton in my life, and I have an annoying habit of losing touch with friends when I move away. Out of sight, out of mind, ya know?
Anyway, to combat this annoying habit, I started scheduling monthly phone/video calls with each of those friends. It’s been a game changer, especially as folks have kids and busy lives.
I imagine that the arrow keys would control the movement of the empty space, right?
Show HN: I made a sliding puzzle game
Inspired by another recent puzzle game [1] and bored at home while sick with the stomach flu, I decided to create a mobile-friendly version of the sliding-tile puzzle game that I once played as a kid.How to play:1. Tap a square to move it to the empty square.2. Repeat until you've unscrambled the image.Options:- Allow swapping: Any image square can be moved to the empty square. (Easier)- Only...
Would be cool if there was an emulated version somewhere. Or we could borrow the author’s book and transcribe it to a modern language, ha.
Product Manager, Data Platform & Enablement
Want to be a product manager on a team that helps the largest audio entertainment company in North America understand and act on its listenership?
Apply here: https://jobs.jobvite.com/careers/siriusxm/job/oU6KffwJ
100% remote friendly. NO formal product management experience required. Folks with non-traditional backgrounds should apply!