You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A github workflow to track progress of convertion JavaScript to TypeScript.
A github workflow to track the progress of converting JavaScript to TypeScript.
Last year, we migrated a large project form JS to TS.
We did this with ts-migrate, and we renamed all instances of any to $TSFixMe, to differentiate them from real uses of any.
Tracking the convertion over time
In order to see our progress on removing $TSFixMe, we build the a github workflow that adds comments to PRs with our progress, eg:
How to deploy a single app to a container from a pnpm monorepo using `pnpm deploy` in Github Actions
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.
I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.
But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.
If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.
Translating GitHub resource IDs to global node IDs
GitHub associates a unique resource ID (or "database ID" or just "ID") with each
API-accessible resource. For example, each [issue][issue-id],
[repository][repository-id], and [user][user-id] has a global ID. In my limited
experience with it, GitHub's REST API generally does not expose endpoints by
which resources can be queried by ID (though it does have some [undocumented
endpoints][repo-rest]). These resource IDs have been superseded by distinct
[global node IDs][global-ids] (node_id). GitHub's GraphQL API allows retrieval
of a node by its ID, called a "direct node lookup".
As you can tell, you likely don't have much reason to interact with the older
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This article aims to be a portal to installation and configuration of Cassandra. It is self-contained in the first place. It also provides links to the original articles.
When hosting our web applications, we often have one public IP
address (i.e., an IP address visible to the outside world)
using which we want to host multiple web apps. For example, one
may wants to host three different web apps respectively for
example1.com, example2.com, and example1.com/images on
the same machine using a single IP address.
How can we do that? Well, the good news is Internet browsers
Minify and templateCache your Angular Templates using Gulp
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters