Consider adding a configurable setting that skips "14" when counting in order to memorialize the cited reason for your effort. It might also help others empathize with your child. :)
> This post can be thought of as an introduction to a really interesting problem space, and as a resource for people interesting in making use of some aspects of Vector Networks for future applications. I hope it succeeds in providing value to both developers being introduced to new concepts and ideas, and to designers interesting in learning more about the tool they know and love.
Seems like that was too far into the article for them to reach. But there’s always enough time for a lengthy rant about their own inability to focus for a few minutes (and how the article itself is somehow at fault!).
> When I star a repo I don't get notified when anyone opens a new issue.
You can customize your repository notifications in a granular way, including subscribing to issues (Watch > Custom > Issues), discussions, releases, etc.
This is the primary method I use to track OSS releases. More in the GitHub docs:
But people don't do that. Pretty much only the maintainer(s) of a project opt in to be notified of issues on GH. On Discord, by default the channel lights up if a channel has new messages.
Image capture isn't the only fingerprinting technique: there are much simpler signals like patterns related to content navigation (just one example: tap vs swipe for advancing paginated content), and the combination of such signals can create a strong fingerprint
Netflix doesn’t need to image capture because they know what content they are displaying. Swipes and taps count for little when the device is a set top box that matches every other set top boxes fingerprint.
A blog might also simply be a contribution to readers — distilling insights which required considerably more time to acquire than might be spent consuming their documentation.
Ben’s continuous mantra of observability has resonated strongly with me. I have learned so much more from researching and reflecting on the indexed artifacts of others’ public discourse than from any ephemeral meeting.
Observability is highly underrated for management. The best managers I’ve had have public calendars, so we can see what they’re spending their time. Priority is pretty clear when management is spending time on something
Great idea but it violates the mushroom management rule of keeping employees in the dark and dumping on them. Knowledge is power, and power is to be held tightly.
Practices that reduce the social status gap of managers above employees are rarely popular.
As an engineering manager, I'm sad for you. I believe in almost full transparency with my teams. The only things I keep private are personal items and things that are not yet ready to be shared.
Not sarcasm to truthfully describe the motives of many managers.
There are a lot of people out there not trying to do stuff but trying to be someone important. Those people want that separation between them and those they consider lesser.
It's nice to see aggregation and curation efforts like this!
It would be useful if the site offered a more compact view and an option for more items per page or "infinite scrolling" (the loading of more results after scrolling past a threshold). Within experiences like these where browsing is the primary mechanism of discovery, it's a positive UX feature to decrease the need for repeatedly clicking/tapping/etc. in order to continue to browse.
Is Slack the only integration? How about support for other platforms? (e.g. Discord is more popular than Slack) Will you support standardized formats like oembed (https://oembed.com/) so that any platform/service which supports such a format can render the code?
reply