I'm currently reviewing applications for a junior front-end position I advertised recently.
For those that applied, it's going to take a while to get back to you. I've gotten about 300 (close to 450 now, since I wrote this) applications. However, I think it would be useful to share some general feedback based on the applications I've received thus far. The goal here is honesty, so I hope it doesn't come across as harsh, but instead as a useful perspective from the other side of the hiring table.
🔥 The tech hiring space is a dumpster-fire at the moment. We need to start with the acknowledgment. It is not that you are not good enough, or doing something wrong. The market is over-saturated with junior applicants. According to Offerzen applications rose by 300% in only 12 months.
This is a work in progress. Please don't take this as something that will definitely happen, we all know what happens to well laid plans and I need to present it to the rest of the TypeScript team in order to figure out a lot of feasibility questions.
The examples in this PR assumes [CLI DX] Improve positioning of compiler error messaging info #45717 is merged
In 4.4, all diagnostic messages from TypeScript are treated the same, we have a massive .JSON file of ±2000 diagnostic messages which are used everywhere from compiler messages to CLI help. Aside from some simple string manipulation, these are effectively what we output for all error messages. I'd like to propose that we break this pattern, just for error TS2322.
TS2322 is our 'type x is not assignable to y' error, you'd see it for const str: string = 123
and I expect it is the most seen
Get the metadata and content of all files in a given GitHub repo using the GraphQL API
You might want to get a tree summary of files in a repo without downloading the repo, or maybe you want to lookup the contents of a file again without download the whole repo.
The approach here is to query data from GitHub using the Github V4 GraphQL API.
This is a quick-and-dirty walkthrough to set up a fresh project with Storybook Docs, Create React App, and TypeScript. If you're looking for a tutorial, please see Design Systems for Developers, which goes into much more depth but does not use Typescript.
The purpose of this walkthrough is a streamlined Typescript / Docs setup that works out of the box, since there are countless permutations and variables which can influence docs features, such as source code display, docgen, and props tables.
npx create-react-app cra-ts --template typescript
- Edit the file at
/Library/Backblaze.bzpkg/bzdata/bzexcluderules_editable.xml
. - Add these rules inside the
bzexclusions
tag:
<!-- Exclude node_modules. -->
<excludefname_rule plat="mac" osVers="*" ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/node_modules/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />
<excludefname_rule plat="mac" osVers="*" ruleIsOptional="t" skipFirstCharThenStartsWith="users/" contains_1="/.git/" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />