2,740 karma · joined December 29, 2018
On the other hand, cash is a germ superhighway.
Unlike decentralized cryptocurrencies, this blockchain is not decentralized and participating requires creating a wallet and having it whitelisted by a centralized controlling entity.
Some form of identification, KYC/AML process has always been required to be an investor or non-trivial financial transactions.
The benefits of tokenization over the traditional approach are fractional ownership, faster settlements and transfers, 24/7 market, etc.
"Thinking" as a concept is just a vague predicate, just like being alive or dead.
The input has to be XML, but you can get there via YAML, JSON, tree-sitter etc. And the output doesn't have to be XML.
xsltproc is usually easy to install.
The Internet Archive happens to have many game ISOs for some reason.
protontricks and gamemode can be useful too.
Racing wheels are still not well supported IMO. Although on Linux you can map a racing wheel to any other peripheral and work this around.
Another thing is that streaming experience is not as good on Linux as it is on Windows. OBS exists but the whole ecosystem around it is largely not.
Still... Linux is my choice of OS.
If I am wrong, someone will point it out and I will have learned something new in the process.
I like this movie poster art. I think it conceptually reflects what you will see in the movie. It also looks genuine and authentic.
- You can be kind, but you also have to be kind to yourself (psychology)
- Collaboration works only when participants share goals (game theory)
- Everyone contributes to one shared output (systems thinking)
- Respecting your profession and honoring the effort that got you to your position (Aristotelian and Confucian role ethics)
- Success comes from discipline, self-restraint and honoring your responsibilities (meritocratic work ethic)
- Identity (and therefore respect) is not reducible to your role, position, recognition, skill level, or socioeconomic status (Eastern philosophy)
You are not there to win a popularity contest but to articulate what is needed clearly, keep people focused, unblocked and to get things done.
If you worry too much about being liked by everyone your mental health will suffer. You just have to accept some people won't like you.
Also comes across as insecure and less fit for leadership roles.
Just like if someone showed up drunk at work, showing up with an unacceptable behavior should be seen in a similar lens.
But at the same time, I do not believe in the power of "let's have a coffee" in a situation like this. There are core beliefs that a cup of coffee will not change.
If someone believes in playing dirty, believes in that basic respect is earned not given, and other rotten beliefs... that person was a bad hire, and needs to have an expedited firing.
A person that reached adulthood while being toxic throughout their life is probably competent at it at this point. While you were focused in acquiring your skills, they were probably getting better at being toxic. So you are probably not prepared for a direct confrontation with a veteran sabotaging jerk. Do not play a game you have never practiced as the away team because you are probably not going to win.
The more you have advanced your career, the more you have to lose while engaging someone. And in this case you have not much to win, against a person that has less than you to lose. Just using up your time and distracting you from your job is a win for a saboteur.
Anything you say can be held against you, so unless you've talked to a workplace attorney better stay out of it. If the situation is affecting you psychologically then engaging the person can affect you even more. Seek therapy if that helps, or channel your frustration through physical activity.
The best you can do is to limit your interactions to the professional level, and limit the topics to what he is working on. Everything else is your business and not his and you can seek additional collaboration at your discretion.
If someone wants to play a different game, let them play alone. It must be clear that the game is collaborating towards a common goal, and if you want to play a different one then you will be playing alone.
We are a band, we are all playing an instrument for the same song requested by a customer, and if you want to play another song I won't start playing the notes of your song that nobody requested.
You can be kind to others, but you also have to be kind to yourself, your employer, and have respect for your profession and the sacrifice others have made to help you attain the position you have.
Do not reward aggression towards you with attention and empathy.
You have to stay away from such people. The guy is likely someone with behavioral issues, bad personality traits and the undermining/sabotage could be a sign of a low skill workplace psychopath trying to manipulate and create a psychopathic fiction. You are not a therapist and it is not your job to fix that person.
When fire has nothing else to burn it consumes itself. Just don't add more fuel to the fire. Don't let that person be in your head, drain your energy. Do not ruminate about interactions with this person. Practice mental hygiene and focus on what's important: collaboration, your actual job, your goals, your friends and family, or something you can contribute in any way...
The first thing you will do, is to talk to individual people by name. Do not ask open questions that everyone can respond to, because he will use that opportunity to be toxic. If he does intervene in a toxic way, you will continue addressing the person you were talking to, by name, and not pursue his talking point. This is fair game because you were not talking to him.
Secondly, instead of having long meetings with the entire team about every topic, you will have a general high level meeting with the team, and dedicated meetings for navigating the actual solutions with specific team members. You will not discuss solutions at length in the front of the entire team, and if you do, see the point above. You will also try to have clear agendas and expectations for meetings.
Thirdly, if he wants to initiate a conversation, try to scope it to what he was working on. Until you mobilize him to work on something else or ask for his opinion, other initiatives are not his primary concern. You can ask "tell me how the initiative X is going", or "what are your current priorities at the moment" to frame the conversation, and steer the conversation so that it stays on topic. If he refuses to answer just say "he will revisit your priorities later" and talk to someone else.
Lastly, if he operates outside the direction given by you as a lead, or consensus of the team, document it. And if it has consequences, document them. Create a clear paper trail that shows that he is not an individual contributor that can be mobilized towards a goal and is a liability for the organization.
Until he fixes his attitude, never ask for his advice in terms of "what would you in this situation if you were me", but you may ask others this.
CTO has a different meaning at different levels of scale.
With a headcount of around 250 employees, you can still work directly on implementation. But with a headcount of 100,000, it doesn't make sense.
Not only this article dumps significant cognitive load on the reader. It's not well digested and not a soft landing into the subject. Worst of all, many Elixir articles assume familiarity with GenStage.
Compare it to this, which is not the best example but is a much more soft landing. https://doc.akka.io/libraries/akka-core/current/typed/actors...
- A RAD TUI like Microsoft Visual Basic 1.0 for MS-DOS
- DolDoc from TempleOS, with diagrams and sprites
- Clipper, DBase, FoxPro, etc
I guess all these differences translate into how the root must structurally develop to satisfy all those requirements and constraints.