Hacker News new | past | comments | ask | show | jobs | submit | more goeiedaggoeie's comments login

As some other posters have said changing some of your habits might not make a meaningful change, but it is a change non the less.

Nature is also stepping up and bacteria is evolving in several places which eats plastic.

I agree that it is incredibly depressing once you realise how wide spread and poisonous to our environment the pollution is. As a society we need to find a way to bake the externalities into the price of every day items, else we will always suffer from the tragedy of the commons.


Part of the game is not to close the side channels of information. conventions for calling are very much part of the game. calling 1 Club vs 1 No Trump is a purposeful signal. Its a fun game to play if you don't take it too seriously


Side channels are explicitly forbidden by the rules.

https://en.m.wikipedia.org/wiki/Bridge_convention


I get that, but the reality is that people who take the game too seriously have long been doing this. Just because reality is not legal doesn't change the fact that it is reality. This is why not taking it all too seriously is so important. As I say, when you play against people doing this you can use it as a tell. Of course you can get angry and bang on about the rules as well.


How about 1 club vs. One cough club, instant 1 club vs 1 [3s pause] club or 1 club spitted out with a visible disgust?


I think it is all part of the game. Good opponents learn to read your signals as well. Think of it as reading a tell in poker.


No, it is not. Perhaps your circle likes it like this, but elsewhere this is cheating. It is forbidden by the rules and is socially unacceptable.


it is not about liking, and in my circle we swap partners and play with whomever is there, but I have played against competitive pairs before and it is clear it is happening. reality is how it is, not how you want it to be. this is not a hill worth dying on and this is why I will never take the game too seriously


using it is the first step. explaining it to others the next, and finally to really understand, writing about it so others understand it really embeds the knowledge.

This is why written cultures in engineering organisations are so powerful, especially if you disseminate the responsibility of writing.


I guess I’d say “using it” should be steps 1, 2, and 3. Explaining it and writing about it are generous ways to share your understanding, but in my mind that’s a different goal.


I have found that using "it" is a lot easier than writing about "it". It is not about being generous it is about deepening the knowledge in your mind and structuring it. different strokes and all that. In my engineering teams I enforce a "Written culture", from the bottom up (so mids and juniors are forced to write), as much as possible.


Turns out getting particles into our lungs are bad! I recently did some DIY on an old cottage on our land which was empty for years, I got a N100 mask since it was painted with lead paint which was flaking off and I was putting lead containment paint over it after brushing it down. An older person seeing me take this rudimentary precaution went about mocking me for being timid.


They also carry long overvalued leases on their books at a time commercial real estate is in the dumps still. Some of my friends have been climbing hard into Commercial REITS now for a few years, hoping for that big upswing in office work to boost them.


This is the statistical long tail indeed. I would also expect that a lot of these vases were buried in soil or on the sea floor where they were undisturbed for many years.


My 13 year old is doing some basic probability already at school, something I did not get exposure to until I was considerably older.


Sorry for asking a dumb question, but how is this different from using Jupyter to write your interactive documentation/runbooks and interactive tests?


While Livebook will mostly have an appeal for people already working with erlang/elixir, it does have a few features that are pretty nice.

- it’s collaborative (think Google docs for code) when several people are working on the same instance of a livebook;

- it’s easy to extend with so-called smart cells (which are essentially pieces of gui you can inject in your document https://news.livebook.dev/v0.6-automate-and-learn-with-smart... ). Smart cells are available for various tasks (db connection/ interaction, data frame exploration, ML tasks, maps), and building your own is relatively easy;

- you can turn a notebook into a web app ( https://news.livebook.dev/deploy-notebooks-as-apps-quality-o... )

- you can run your code an a remote elixir node by attaching to it (although this requires some knowledge of distributed elixir/erlang )


thanks for the detailed answer of the differences. The interactive (I assume using CRDT's) is a good feature, jupyter server does not have this and is at a time a bit of a hassle. Also deploying it directly as an app is pretty sweet.


Livebook actually uses state reducers as described here[1]. Except for cell content. There it uses Operational Transformation. The source code[2] is really instructional and easy to understand. I highly recommend to look into it :)

[1] https://github.com/jonatanklosko/notebooks/blob/main/article... [2] https://github.com/livebook-dev/livebook/blob/main/lib/liveb...


A great read, thanks so much!


> how is this different from using Jupyter

It requires you to run a far less common tech stack and limits your hiring to a vanishingly small subset of developers.

Paradoxically, that may be a good thing.


This is just, wrong. There's actually a huge number of Elixirists, but after this long in the game, we're used to cynical elitists...


Love it! yes, it might be better. We have found paying above market average and being tighter on interviews has a similar outcome.


Elixir market is already more high paying than python.


According to SO’s survey, Erlang is the highest paying technology or something like that.


Outputs markdown, easy to share.

Jupyter outputs JSON.


GObject is pretty cool, allow great interoperability. Used extensively in gstreamer


Leaders lead no matter what their job title is. If you think being a manager is what is needed to command respect then I think your view of leadership is skewed and you are only going to be authoritarian. If you want to grow focus on the outcomes you are achieving, engaging directly with the outcomes of the business and accelerating those is the way to get ahead. Frequently I see engineers who believe their work is to write code, this is not the right mental model, great engineers solve business problems through engineering, process design and at times simply through leadership and saying no. Ticket monkeys whose job is to code what is on a jira ticket and nothing but that, are limited in their use.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: