"I mean, I don't say it's true, but..."
submitted by Pickle086
Another excellent article from @fasterthanlime -- https://fasterthanli.me/articles/lies-we-tell-ourselves-to-keep-using-golang
It take #golang as "averaging" language. It pulls juniors up, while pushes more experienced devs down. Basically stay in line and you will be "fine".
On the other side -- it is easy to start with and get back to. I love #rust but always feels like a full-time commitment :(
Just fixed another vintage plotter. This time a beautiful Roland DXY-990. Quality is exceptional, especially if you compare it to what we had here at similar time
Printing double Klain bottle with a vintage (1987) plotterXY3141 via DIY interface for #RPi 0 (under the brown PCB). Plotter, originally connected to #ZXSpectrum is now connected to home WiFi. Dah, even the @eevblog DMM next to it has more processing power :) #pl…
Another confirmation that Airbnb is taking digital nomads into account more as @levelsio predicted.
Yes, finally... We’ve made it really easy for Hosts to verify their wifi speed. Now, when you book an Airbnb, you can be sure it has good wifi.
Chytré a jednoduché rozšíření k-means algoritmu, které dá výsledek lepší a rychleji.
Discovered https://github.com/stateright/stateright and lost myself in the TLA+ rabbit-hole. Excellent resource is obviously THE Leslie Lamport's site: https://lamport.azurewebsites.net/tla/learning.html
I was not particularly looking for wasting 2h on transfer time today. Did I know that they were actually awesome thanks to a great podcast with @balajis
This is basically one of the ultimate productivity hacks (along with generic learn how to say "no"). Always worked great.
I am now trying to bring it into an existing team with a long history... we will see.
Default to saying "no" to meetings.
1. Avoid meeting without a clear purpose
2. Say "yes" to meetings with people, "no" to meetings for info
3. Info meetings can almost always be asynchronous
4. We still need 1:1…
Awesome. I had to spin own proxy solution for that last year. Time to go NATS native again. Thank you!
You can now connect to NATS server's Websocket port with the NATS Go client. Simply use the "ws://" scheme in the connection's URL. https://twitter.com/nats_io/status/1389604476768690179
Also option for naming the access key would be awesome :)
Have not found a way how to tune the policies (e.g. having midnight GMT on every machine may not be what you want). Small tweak for the (excellent) doc -- the created channel will be "stable" not "master" as used for jobset uri and package name.
Playing with http://floxdev.com (thx @grhmc for approval) found via @a_hoverbear . Really slick experience on the top of the Nix. Awesome to see BEAM support out of the box. Would be nice to have some ENV to turn on progress indicators instead of hanging for dep downloads.
Wooha JetStream is a big thing! Congrats @derekcollison
Have you heard? Our maintainers and engineers have been hard at work and we are ready to shout from the rooftops! 📣
NATS 2.2 | The JetStream Release is here! 🎉
In addition to the long-awaited addition of JetStream, NATS 2.2 is bursting with new features.