absolute100

26 ms·

361.
by absolute100 6y ago
Erik Torenberg wrote a post I wish I could have read when starting my career. It would have helped me figuring out how to pick companies to work at, people to work for, and companies to start: "[T]he biggest career mistake young people
362.
See Your Career as a Product – Erik Torenberg's Thoughts(eriktorenberg.substack.com)
3 points by absolute100 6y ago|1 comments
363.
by absolute100 6y ago
Jens-Fabian Goetzmann shares helpful formats you can experiment with when considering your organizational structure. Every organization has different needs to fit the people they have and the challenges at hand, so adjust the structure (and
364.
Establishing a Product Organization Structure – By Jens-Fabian Goetzmann(medium.com)
2 points by absolute100 6y ago|1 comments
365.
Our dangerous obsession with perfectionism is getting worse – Ted Talk(ted.com)
7 points by absolute100 6y ago|0 comments
366.
by absolute100 6y ago
Steven Sinofsky with an essay about a commonly abused tool - meetings: "the most important thing in growing a company or team is to of course focus on getting things done, but the only way to get the right things done is by having meet
367.
Reaching Peak Meeting Efficiency(medium.learningbyshipping.com)
6 points by absolute100 6y ago|1 comments
368.
by absolute100 6y ago
Silicon Valley’s predominant model is to raise unicorns. Traditionally, this is done through rapid growth. The problem now, however, is that this growth-at-all-costs methodology, which the Valley’s top players are exceptionally good at, onl
369.
Startups, It’s Time to Think Like Camels – Not Unicorns(hbr.org)
4 points by absolute100 6y ago|1 comments
370.
What kind of risk-taker are you: Maximax, Minimin, or Minimax?(cauzalai.medium.com)
11 points by absolute100 6y ago|1 comments
371.
by absolute100 6y ago
John Cutler's list is excellent, as it points to potential "org smells" or "process smells" that should catch your attention. As programmers, we are taught to look for "code smells" (things you should try
372.
When You Hear _______, Pay Attention – johncutlefish's blog(cutle.fish)
1 points by absolute100 6y ago|1 comments
373.
by absolute100 6y ago
I'd also consider setting early expectations in advance (otherwise people will always feel we can do more), and clearly state what will not be promoted. Lastly, communicate once a month (at least) changes in plans - features that were
374.
How to make your data science team faster (and speed up progress)(makingdatamistakes.com)
1 points by absolute100 6y ago|1 comments
375.
by absolute100 6y ago
This talk by Michael Dearing on the Minto's Pyramid is one of the best videos I've seen about how to communicate clearly as a leader. Added to my Anki Notes app as there are so many golden nuggets in it, I want to remember and app
376.
Executive Communication with Harrison Metal's Michael Dearing – Heavybit(heavybit.com)
4 points by absolute100 6y ago|1 comments
377.
by absolute100 6y ago
A friend recommended me to watch Ashley McNamara's talk. It's great to watch as I can imagine it would be relevant to many - with tips to prevent getting to a point where you're completely burnout. I try to do things in a way
378.
Ashley McNamara – The Thing About Burnout(youtube.com)
3 points by absolute100 6y ago|1 comments
379.
Thoughts on Conway's Law and the Software Stack (2019)(blog.jessfraz.com)
99 points by absolute100 6y ago|24 comments
380.
by absolute100 6y ago
"There are people thinking an interface or feature is secure when it is merely a window dressing that can be bypassed with just a bit more knowledge about the stack. " -- Jessie Frazelle shares one of the toughest problems when de