Basic, but important:
Product teams should rarely prioritize Efficiency higher than Effectiveness. And yet so many do
How to tell them apart:
Teams that value Efficiency obsess over Speed & Process
Teams that value Effectiveness obsess over Customer Problems & Differentiation
@PhilakoneCrypto Just have to open an isolated margin account for it. In your case you could probably just leave it funded if you wanted to, but in my case it's only a few clicks to move funds into cross margin or whichever isolated account you want to trade in.
How to build a remote company:
- look for people great people, anywhere
- pay them through @remote
- meetings with @zoom_us
- write stuff down, all the time in @NotionHQ
- put your code in @gitlab
- get together if you can, don't work when you do
- have calls just for fun
We released patch 1.2 of #TheOuterWorlds today, and it includes a fix for the dreaded "the game thinks my companions are dead" bug, which I believe I spent more time investigating than I have for any other individual bug in my career (1/18)
🚨 📣 Announcing:
🏆🔥🏆🔥🏆🔥🏆🔥🏆🔥🏆
🔥🏆 https://t.co/He56i6S4yS 🏆🔥
🏆🔥🏆🔥🏆🔥🏆🔥🏆🔥🏆
💸 There's a HUGE discount right now too 💸
From total beginner to EXPERT tester with 8.5 hours of *super* high value-to-minute content (I don't waste your time), and ...
1/9
Most common mistake software developers make: putting stuff in the wrong place. Coupling responsibilities and concepts that should be kept separate.
For me, this is 95% of software development. Just figuring out *where* things belong.
One of the most valuable concepts I learned in school: Opportunity cost - The loss of potential gain from other options when an option is chosen.
This is why getting comfortable with saying "no" is important.
Every "yes" is an implicit "no" to something else.
Today is YC's Demo Day, where founders try their hardest to give away control of their company.
Let's celebrate bootstrapped and self-funded founders with our own "Demo Day". Reply with:
1. A description of your company in 10 words or less
2. MRR (if any)
3. Link to your site
The longer I do design systems the more I feel like seeing a lot very flexible APIs in your tools is a red flag. It's another thing in Decision Debt land. Thread:
Whenever a rule is added in a team, first ask:
Will the existence of this rule discourage future people from using their human judgement to make smart decisions in nuanced situations?
Optimist - The glass is half full.
Pessimist - The glass is half empty.
Developer - The glass is twice as big as it needs to be.
Product Owner - We need to put 3 times more water in that glass; Make it happen
The most frustrating thing in debugging is not finding the problem. It's when you find the problem, see the problem, fully understand and agree with the problem...and now don't understand how it EVER worked.
@sarah_edo@weskerfoot Is a shared context a requirement for what you are talking about here? Some patterns may look more complex than necessary if you don't understand the problem they solve. Vani assume your complaint that the problem is the bragging and not that the situation happens sometimes?