Yes, input type="number" is not the best, but when I ask for 2FA codes or credit card number a metric keyboard makes sense. And this is currently the best way I know to achieve it.
138 karma · joined May 3, 2019
Yes, input type="number" is not the best, but when I ask for 2FA codes or credit card number a metric keyboard makes sense. And this is currently the best way I know to achieve it.
In europe it is more common that you have things like a supermarket in walkable distance (or atleast short trip on a bike).
I see no problem with that if it is a small change that can de deployed safely. (for instance hidden behind a feature-toggle where applicable).
We tend to strive for small, short lived branches. We usually don't want PRs with more than a couple of days work - to keep them small, easy to test. It also makes the amount of changes going to production at any time small.
The best would be if any specific feature is small enough to only be a few days work. But out experience is that it is not allways easy to do that - and sometimes some features will take weeks before they are done.
On my current team, we want most tests to be automatic. But the manual regression testing that might be needed is mostly done by other developers. A separate test-environment is created for each PR, and the link posted in the pull-request. So when looking at a pull-quest we expect people to do both a code-review and QA.
In my team approving a PR means you approve for the code to go to production. So you need to consider both code quality and whatever QA is needed. But thats just our way t do it - other teams do things differently. And I think thats OK, there is no silver bullet.
I can't remember the last time I created a website in a professional setting that would work without JS. Everything is written in things like React, Angular and Vue.js these days. And that seems to be the case for most modern websites. Atleast things made here in Oslo.
But this is just my personal experience.
It is not uncommon to find multiple ticks on your clothes if you have been walking in tall grass. But they usually take quite a while before they find a spot to bite. So if you take some precautions it is not a big problem.
But like many other things, it has been exploited, especially by big corporations. And the patents no longer work as intended. And the big problem is that theres so much money on the line that is it not easy to change. I would assume large corporations already spend absurd amounts of money on lobbying for the patent-rules to work in their favor.
Patents as a concept I am all for. It is a good way to make sure that new entrepreneurs can make it to market before "big-corp" steals their idea and just push them out. But they would have to change how they work to stop patent-sharks and the big exploitations by said big-corp.
So in the end we would still end up not trusting it and rely on testing (hopefully as automatic as possible) before we could merge the upgrade.
In the end we just switched to using timestamp-based version numbers and just try to upgrade often enough so each incremental change is small. And try to have good automatic tests that can do most of the regression testing for us.
[1] https://icds.uoregon.edu/wp-content/uploads/2011/07/CryanDin...
In this case, I guess the developer wanted to use JSX to create it. And you could ofc use JSX without React. But most people are used to using it in react-context, and plan to use it in an react-app anyway.
So to answer your question, in my eyes it would be. Why not? If the devs plan on using it in react-app anyway, it's not their job to make sure it supports everyone elses usecase.
But it would be interesting to read a proper documentation of it.
My own opinion is that I don't know the correct way to do economics in the future. But I do think that we at some point should think very different. I don't think the current system works out for most people in the future. And UBI looks more like a band-aid than an actual fix.
- People at low average income will have more money (the UBI-increase will be higher than the tax-increase)
- Average income: You get as much as before.
- Higher income: you pay more in taxes than you get from UBI.
Basically it ends up being a way to move money from the ones with higher incomes to the ones with less. It will ofc still give some inflation as poor people have more funds for basic needs. But other people will have less - and the average person just as much as before. Limiting the effect of the inflation.
In my eyes, the reason much of the public sector is unproductive is not because it is not motivated by profit. But rather that it is too similar to large companies with loads different management-levels.
I once worked in the public sector when they embraced real autonomous teams with leaders that could actually make decisions when the team needed it. It was just as efficient as the best agile teams I have worked at in the private sector.
Is sniffing of traffic common in other countries?
With TS I don't need to spend as much time with these types of tests. I just let the compiler do it for it. If my function says in it's signature the argument can't be null I don't need to do null-checks.
In that way you kinda know which DNS they used.