I've been working remotely for a few years now, for various companies and clients.
One itch I needed to sratch is timezone conversion. It's always a mental effort to figure out when someone in your team will be around, and to compute when you should schedule that meeting so that everyone invited gets a "respectable" time.
Here I present you whena.re, the most intuitive timezone viewer for your team ;)
It's been live for something like a year now, lots of people use it and feedback has been great so far,
I released a Slack integration so I'm hoping this will convince some of you to give it a shot if you've never tried it before!
Happy to discuss some more if you have questions or comments,
tl;dr:
governance is hard, there's no silver bullet, every system may be tricked.
"good blockchain governance" would rely on gathering the result of multiple "coordination flags" like a user vote, a coin vote, core dev decisions, etc.
Very complete "here are the limitation, in the end, just don't be dumb" article.
About the bribing part:
Could we get rid of it if voting is anonymous (I can't reward you with a bribe),
and we give right to coins that haven't moved for a certain amount of time (I can't ask for your money and your account has to be "old enough")
?
Since I couldn't find any explanation on the article:
> Snaps are containerised software packages that are simple to create and install. They auto-update and are safe to run. And because they bundle their dependencies, they work on all major Linux systems without modification.
Appears to be a packaging systems for (desktop) apps on linux with auto-updates and stuffs.
Interesting "we must learn/accept/fight to cohabit" view,
It's super American - Westerners centric though, what happens if decentralised currencies take off in emerging countries?
I want a similar platform with reproducibility built in:
your paper gets in the blockchain, if and only if, its results can be reproduced by other members ("Proof Of Reproducibility").
Exactly my cliché of the Clojure community: a discussion about simple things like testing and tooling becomes a place to brag about some random features of Clojure. Insulting my patience (or the original author) on the way is a new one.
You're just confirming my last point, professional Clojurist? Enjoy it. Others, be warned.
I've been learning & trying to use clojure(script) for ~2 years now.
A few things I miss in every other languages:
- The REPL: I usually don't need a debugger,
- Figwheel: that makes frontend dev a pleasure,
- reagent/reframe: are incredibly straightforward, there's no special syntax, no special constructs, just a few functions, a few concepts (dispatch / subscribed) and you're done,
- core.async: based on a simple channels / pipeline paradigm
But then you get into the practicalities of testing & writing code. Shady special cases[1][2], annoying testing tools[3], useless stack traces. And other issues everybody knows. Simple things that become a 30 min discussion with 3 different libraries and 2 blog articles to go through[4].
To me, there's this hardcore group of clojur'ist that seems to be hyper productive and keep introducing new concepts. And the "rest" (me at least), that are floundering.
You fight with useless stacktraces? Boom, transducers. You deal with buggy test runners? Bam, a new specification library with test generations.
I've started moving my code to ES6 and Go. The community is filled with helpful people, but it seems to me that if you're not writing Clojure professionally already, the language is becoming less and less relevant.
You may not know: on Unity you can saturate / desaturate the windows. I set them almost black and white and increase the saturation when I need it (shift + brigthness up / down).
I have no idea if it provide health benefits similar to the "orangy filters" but it's pretty nice on the eyes and, personally, it makes me happy to see the outside world with brighter colors than my screen.
We both agree, I'm just using this as a pretext to share this intriguing piece of knowledge. I find the concept much more intuitive than "getting back unused memory".
Especially when you look at the 90% memory usage on your OS, it still make sense with the "infinite memory simulation" definition.
I've been working remotely for a few years now, for various companies and clients.
One itch I needed to sratch is timezone conversion. It's always a mental effort to figure out when someone in your team will be around, and to compute when you should schedule that meeting so that everyone invited gets a "respectable" time.
Here I present you whena.re, the most intuitive timezone viewer for your team ;)
It's been live for something like a year now, lots of people use it and feedback has been great so far,
I released a Slack integration so I'm hoping this will convince some of you to give it a shot if you've never tried it before!
Happy to discuss some more if you have questions or comments,