Chernobog
There are a handful of rules that are nice to have in a TypeScript project to make sure devs don't do things that break type safety. Plus some that avoids mistakes from slipping through (even though the code is reviewed).
One thing I've found super useful is to have @typescript-eslint/ban-ts-comment enabled, but configured so that you can still use @ts-expect-error and the others as long as you provide a comment when doing so. This is so nice when doing code reviews, either someone has provided a very good reason for the exception, or it is clear that the same result could have been achieved with a better approach. Same goes for disabling eslint rules inline in a file, also allowed if commented. I feel that this is a very good compromise between being strict with linting, but also not letting linting get in the way.
The only pity is that I need VMware Fusion and it seems to be broken in the patched Ventura with no fix in sight. Stuck on Catalina for now on my 2012 rMBP.
Correct me if I simply have missed it, but is there an official NPM package available? I have seen https://www.npmjs.com/package/sorttable and perhaps some of the sites would drop the script tag if "npm install --save-dev sorttable.js" is in the instructions and they have a build step for their JS anyway. Just thinking out loud.
Edit: My personal opinion is that we should rid ourselves of the demand for dark web markets by regulating drugs. The regulations should focus on harm reduction, both for the users and society as a whole.
Everything got much easier after getting the diagnosis and medication as a 33 year old.
Adding insult to injury, the company behind the service loudly markets that they support Pride every year. The payment processor has pictures on their Facebook of employees attending the Pride parade... We're not a commercial entity, our activities are legal and we also march under the same (rainbow) flag.
Oh, and there is no reasonable appeals process. We initially applied for a different product a while back and got rejected since they had run our web page through Google Translate and determined that we were involved with "public group sex". Asking the service to get is in touch with the payment processor to clear up the misunderstanding was not possible, they just said there was no way to appeal and our best bet would be to contact them ourselves through their website.
/rant.
I realize many have reasons to get rid of Facebook entirely, but for me this was a reasonable compromise.
On a related note: I have an old scanner that I use about once every year. Drivers max out on XP support, so I installed Windows Fundamentals for Legacy PCs in a VM, which is a stripped down Windows XP. Perhaps someone in the W2k crowd would be happy with WinFLP as an alternative.
You don't have to be the world's best in the thing you pursue either, to get noticed. For many hobbies and interests, there is a scene. And there are so many ways to contribute to that scene, such as helping arrange events or arranging your own. This will put you on the radar among a lot of people, and shine positive light on you.
I maintain one frontend in this stack, and the review app produced will only contain my version of the front-end, and the API calls will go to the backends in the development environment.
Review apps for backend services will also point to the development environment if this particular backend needs to communicate with other services.
When a feature touches a frontend and a backend simultaneously, we can solve that in various ways. Sometimes the backend can be finished first, but if that's not feasible we can supply URL overrides for endpoints to the review app of the frontend, so it communicates with the review app of the backend (and uses the rest of the development environment for the other calls).
This works for us and might not be feasible for all projects/stacks/companies for various reasons. YMMV I guess :)
Our CI automatically deploys a "review app" when someone creates a pull request. This simplifies code review, QA and demoing!
Singular elements: data-test-save-button, data-test-name-input
Elements that are a part of a list: data-test-user={user.id}, data-test-listing={listing.id}
This allows us to name our elements with data test attributes, but also provide values to them where applicable.
I have also created a testSelector function that takes id and value, and spits out either [data-test-${id}="${value}"] or [data-test-${id}].
We have also experimented with letting shared components popuplate their own data-test-* attribute automatically based on other props. Like in our modal component, which sets data-test-modal={title}. data-test-delete-user-modal vs. data-test-modal="Delete user". But in the latter case, the dev does not need to provide the data-test-* attribute manually, since the component takes care of it.
I guess what we disagree on is whether that is an issue or not. What problems do you feel the current hooks API is causing, that could be solved with a different API?
I get that hooks are declared in the form of functions, and that pure functions are the desired pattern in many cases. But I like to think of hooks as hooks, not functions (emphasized by the naming convention of prefixing with "use"). We are in the context of React, after all, and I think it is comparable to critique of JSX because of "separation of concerns". Yes, valid critique in many cases, but not necessarily applicable to React.
Having been a React developer for over 5 years now, I think hooks solve a lot of problems that before would typically have been solved with Redux, Redux Saga and other libraries. Or with home made solutions, leading to various degrees of mess. From what I've seen, hooks have enabled React devs to write code that is even easier to understand, while also keeping things simpler and external libraries fewer.
Sure, you have a lot of good car choices today, but at some point it might be hard to find a car that has your other desirable specs in addition to being repair and modification friendly.
If everyone who bought a car was a well informed with at least a minimum of knowledge of cars, in addition to being able to calculate how repair costs will affect them over the time they own it, then sure. Let the market sort itself out. Since many aren't, let's keep regulations in place to ensure desirable properties.
Heck, imagine what safety features cars would lack if they weren't government mandated requirements...
Since it was for the police, a background check would be required. I politely told my department head that I would not pass that, and a short summary of my case. At that time I had worked for about 2 years and got a kind "we would never have guessed" and "you will get another project then".
As a side note: In our country, an employer needs a legitimate reason to do a background check, and they won't see crimes that are not relevant, or for some crimes - too long ago.
I bought one to run Windows on my Retina MacBook Pro. I only need Windows for gaming when visiting friends, and it works flawlessly for that purpose.