I've built at least hundred of little tools here and there to improve my productivity to the point where single keypress is what only needed in every other context to run specific scenario.
I've tried to give it to my fellow devs around to make their lives easier.
The performance data from the linked arXiv paper: 965.9±3.4 [s] on AWS p3.16xlarge instance for program which calculates Hamming distance between two 8-digit hexadecimal numbers.
Estimated sec. per cycle: 0.794 [s].
Also, from from the appendix, it takes roughly 116 seconds on the AWS p3.16xlarge instance to calculate fibbonacci(n) for n=5.
Every single oscillating particle needs to travel more absolute distance when speed increases, so it will oscillate with lower frequency for the external observer, thus causing time dilation.
Could someone shed a light on economics of working on such kind of a project?
Aren't developing third-party client for the entity which you do not control and somehow compete with is typically a futile experience?
Doesn't it go against most of ToS-es directly (e.g. Discord/WhatsApp happily ban accounts using third-party clients) or indirectly (I guess no proprietary chat platform will be exactly happy having third-party clients that compete with their official and controlled app).
I mean how people justify building a business on it given that it essentially means that they have to play on the other's people playground by the rules which can be changed at any time. Like tomorrow Slack would decide to disallow any third-party apps and you're done.
TIL: apart from infinity (number, larger than any real number in absolute value) there are infinitesimal (number, less than any real number in absolute value and not a zero).
Edit: also, those infinitesimals were the subject of political and religious controversies in 17th century Europe, including a ban on infinitesimals issued by clerics in Rome in 1632.
I'm sorry, if you could build a model to predict markets, why will you post in to Kaggle to get $40k in prize instead of applying this model to your own broker account?
I'm fan of heavy key mapping customization to boost productivity.
The most productive remapping so far which I made is to globally remap (via xkb) Left Alt + HJKL to respective arrow keys. Works in all GUI applications which rely on arrow keys for navigation, plus standard Ctrl + Shift + Left Alt + H (Left Arrow) works to select previous word in text fields (e.g. in browser).
Next one is to remap Left Ctrl to Left Shift and to press it with upper side of the palm just below pinky (not sure how this part of the hand is called correctly) instead of utilizing finger for that. Works best on mechanical keyboards without bevels.
Also I find quite useful to remap keys 5-0 to Right Shift + Q (5), W (6), E (7), R (8), D (9), F (0). I find these keys are easier to reach and type without a mistake instead of using standard 5-0 keys which you should stretch your fingers to type.
For example, to type "()" I use Left Ctrl (remapped to Shift) + Right Shift + D, F which is easier to type without fingers leaving home row.
If you don't remember the particular command, why not to look it up for the first
time and then assign personalized alias, which is easy to remember?
Like with `tar` example and `zsh` you can even define suffix alias (`alias
-s`), so you can just type `./your-file.tgz` and `zsh` will invoke `tar -xzf
./your-file.tgz` or whatever you prefer.
That's essentially my problem with the open source.
I was an open source apologist some time ago, but since I quit full-time job
and started to freelance/working on my own personal projects I began to
realize, that I as an independent developer can't actually profit from it.
In fact, it takes a lot of my time to contribute to something and I get nothing
in return.
From my perspective:
* Behind every popular open source project there is a company (typically big),
which pays core team salary to maintain open source project.
Community is typically do work for free. The bigger the project, the better
for the company public image.
* Open source projects end up to be designed by committee, which inevitably
turns projects to bloatware, which are hard to maintain and hard to use.
* Increase in technology turn-over. Projects become hyped and die faster that
* Competition is becoming more difficult. Why to try to make another deployment
manager if there's Kubernetes?
* En-masse community memebers get nothing from contrubuting to projects while
doing a lot of work for free. One may argue that in return they get polished
product, but in reality that's far from true.
Doesn't seem to be a particularly tricky question unless I miss something, just basic probability theory calcs.