I assumed I had just got a bad unit. Now I’m wondering if this might have been the cause.
As the parent comment said - but I was questioning about whether increased torque has an actual impact on tyre wear.
On top of that, at my last job, on my team of 15, I was the only one with kids, and only 1 of those 15 engineers were under the age of 30. At my current job, my team is 8, and again we're all about 30, and nobody is even thinking about kids at all.
It baffles me. And it's also a bit inconvenient that nobody else at work has such pressing obligations, it makes me feel bad (though not too bad at this point) that I *have* to log off at quittin' time, sharp, to go relieve my wife of some childcare and make a family dinner.
I created this because I found myself peeping inside type declaration files too often, and the only way to do that was by installing the package first.
tsdocs.dev helps you check the API surface of a good number of JS libraries and their past versions — usually a quick search away.
There's something powerful about speed and being able to answer questions in seconds that usually take minutes.
edit: The server might be overloaded with requests as we prime up our caches, but do visit back after HN's done hugging us to death.
You can show your support and help cover a part of server costs if this (or bundlephobia.com) saved you time.
Not much for instructions but it’s here is anyone is interested. https://github.com/jpatters/goodlife-receipts
I set up custom entry codes that I could hand out to anyone. Everyone got their own code, and it would text me whenever someone used a code so I'd instantly know who was coming. The text conversation was my timestamped access log. I also put time constraints on some codes so e.g. Doordash couldn't open the gate in the middle of the night, or I could set up a temporary access code for a party, and I rotated codes too, with text notifications if an outdated code was used.
I thought about making a paid app out of it, but it just didn't seem worthwhile. I didn't expect that many people would want to pay for it. For a while I was excited about a YC startup called Doorport that was going to make a hardware device that you'd install inside those dumb call boxes and make them smart with all sorts of cool features, better than my Twilio hack. But I think they pivoted to a much less interesting pure software thing and then got acquihired.
Maybe it's cause I had earlier experimented with a subscription instead of paying once for the new features.
Shoot me an email please, I'll provide you with some coupon codes so you can get the pro features without paying, just in case you want to try it out again.
I do, however, want to support partial clones and easier tools to cleanup the history and reduce the repo size.
libgit2 already supports filters and that’s all you need to build lfs support (actually, you don’t even really need to use them if you don’t want to). Lfs itself is not a feature of git. It’s a specification that defines a protocol for replacing large files with pointers (via the use of the smudge and clean filters) and uploading said large files to another location.
Source: I am the cofounder and former CTO of forestry.io, a git backed content management system, and I implemented lfs support in conjunction with libgit2 in that product about 4 years ago.