During the first 2 to 6 weeks on a job (it probably varies more than this) most corporate US environments expect significant amount of time to go to processing/onboarding. When providing status updates in meetings just state as much, usually with little to no specifics. I've yet to see anyone respond at all within the first month. What's remarkable to me is the amount of overhead/cost associated with these institutional mechanics, despite tools like Workday, which frankly I don't see as actually being effective. Staff counts of 2 and more (in addition to the new person) with these tools still can't manage to communicate with new staff where to go, where to send equipment, etc which reveals a significant need in the market.
Yeah a Stanford professor told me you need 6 months to be productive in a coder job. 3 months, others have said. To pull your weight, and then pull more than your weight.
Of course where I've worked the firing threats start on day 1, and they obviously expected (Unholster for one) that I work at home. Those guys wanted the whole install to be done at the end of day 1.
There is no such place in the US. And SF is not it either. San Jose appears to be steadily improving, though this is not a recommendation at all. This is my perspective traveling and living around the northern hemisphere awhile, including substantive time in SF. Manchester NH is within an easy Uber ride of BOS and may be of interest. Winters aren't so great but you can easily fly as far south as Puerto Rico, which has massive crime problems and barely functioning government. There are obviously various options in between. My opinion is that the US is generally inhospitable, SF included, and is unlikely to change substantively in the next several decades. California could start banging out housing, improve transit and reform healthcare delivery and it would probably take at least 20 years to catch up... to what you'll easily find outside the country. America is at the stagnation point in transition through institutional and socio-economic cycles based on what I understand and the solutions aren't super clear at the moment--at least not as clear as the problems.
A tremendously helpful article. Possibly one of the best HN shares I've seen related to software. Most code reviews I've seen professionally over the past decade are almost entirely stylistic one-way brittle dialogs over text of small to large pull/change-requests. When in reality these could, should, recommended to be (as the article shares) side-by-side discussions for dialog to improve the product being contributed to. It's really an effective way to ensure that someone else can pick up the work and go if the other gets hit by a bus, and in my own experience, when I lead with an explanatory walk-through exposes bugs (to myself) along the way--that even the reviewer often doesn't note. Thanks for sharing, software development practice is several decades behind... other practices, and content like this help to improve it.
For the benefit of anyone who doesn't have a lot of experience with call, bind and arrow functions ()=>{}.
No, these don't supplant one another and are separately useful in various ways. Reading the linked articles shows some of the related situations.
Yes I’m wondering why these various comments directly challenge this publisher and publication’s credibility? Especially without a substantive explanation since the content is available for this type of dialog. Strange.
> A mega journal (also mega-journal and megajournal) is a peer-reviewed academic open access journal designed to be much larger than a traditional journal by exercising low selectivity among accepted articles. It was pioneered by PLOS ONE. This "very lucrative publishing model" was soon emulated by other publishers.
The front-end world has been relatively stable since then. Sure, there have been experiments with other approaches (Cycle.js, Elm, Svelte, ...), but by and large React and its contemporaries are still by far the dominant players, and while they have evolved as well, their mental model is still largely similar, so I'd group them in the same "era".
