dogear

enter for all results · esc to close

Business

1,528 items in 12 lists

  1. source news.ycombinator.com

    )

  2. source news.ycombinator.com

    ) - Or how OKRs can be weaponized to prevent top managers to mess with the (already established) schedule.

    site link ↗
  3. “That's usually about the time I nope right out of the interview” news.ycombinator.com

    Bad signs of a CTO trying to recruit an engineering manager, or the perils of not believing in hierarchies.

    site link ↗
  4. source news.ycombinator.com

    ) - Some tips on how to balance which kind of information needs to be shared or muted.

  5. source news.ycombinator.com

    )

  6. source news.ycombinator.com

    ).

  7. Executives ratify decisions made on the spot news.ycombinator.com

    Tolstoy's thesis to business.

  8. Google's usage of OKRs news.ycombinator.com

    OKR grades are public, but not used for promotion. It was never taken very seriously there.

    site link ↗
  9. On VC funding and huge growth news.ycombinator.com

    “Startups need an exit strategy. (…) The idea is to raise money fast, hire experienced people for ancillary services and develop the application in a way so that it is able to hold up till IPO. Defer all costs for post IPO.” So from this angle, the only reason to join a startup…

  10. If I Close My Data Centers, What About the People/Jobs Lost? news.ycombinator.com

    F50's data centers being migrated to commercial cloud provider. But what about the people currently doing legacy stuff? The answer: retrain.

    site link ↗
  11. source news.ycombinator.com

    ).

  12. Things to look for when hiring remote workers news.ycombinator.com

    “1. You have to adhere to employment laws within the country you're hiring from; 2. To employ someone full time, many countries require you to have a legally entity within that country; 3. Prioritize countries where we have the most interest; 4. Keep a healthy timezone overlap…

  13. Best project management practices in 2018? news.ycombinator.com

    There is no silver bullet.

  14. You have only 4 options news.ycombinator.com

    “1. Change you; 2. Change the other; 3. Fly; 4. Stay and suffer.” A more concise way of saying the same thing as above.

    site link ↗
  15. source news.ycombinator.com

    ) - Examples in which developers that might pass tough job interview just fine are bringing negative value later.

  16. You need to be this tall to use (micro) services news.ycombinator.com

    Do not chase the hype. Yet. Micro-services only brings value past a certain infrastructure and organization size. This is a list of stuff you should focus on before bringing micro-services to the mix.

    site link ↗
  17. source news.ycombinator.com

    ) - Do not chase promotion for the title only.

    site link ↗
  18. What makes a Senior Dev news.ycombinator.com

    “Time, man. You gotta do your fucking time.”

  19. I try to optimize my code around reducing state, coupling, complexity and code, in that order news.ycombinator.com

    An engineer's perspective on which priorities should be addressed first to increase robustness of systems.

  20. As an Employee, You Are Disposable nelson.cloud

    “It's okay to like your job and employer. Just understand that, as an employee, you are disposable.” Also: “This is not news. If you are loyal to your employer and do not own a significant part of the organization, then you should take a good hard look at why you're loyal…

    site link ↗
  21. Things I Learnt from a Senior Software Engineer neilkakkar.com

    “I sat next to a senior software engineer for a year. Here's what I learnt.”

  22. Early-career setback and future career impact nature.com

    “Despite an early setback, individuals with near misses systematically outperform those with narrow wins in the longer run.”

    site link ↗
  23. What senior engineers do: fix knowledge holes mooreds.com

    “This is the textbook definition of a senior engineer. You see a problem, you solve it (thoroughly), you document it and you level up your team.”

    site link ↗
  24. 7 absolute truths I unlearned as junior developer monicalent.com

    “1. I'm a senior developer; 2. Everyone writes tests; 3. We're so far behind everyone else (a.k.a. tech FOMO); 4. Code quality matters most; 5. Everything must be documented; 6. Technical debt is bad; 7. Seniority means being the best at programming”.

  25. “Why does the tire company rate restaurants” mobile.x.com

    A great example on why you should investigate complementary businesses.

    site link ↗
  26. Notes on Technical Writing mkaz.blog

    An effective list of do and don't when it comes to writing documentation.

  27. Things I have learnt as the software engineering lead of a multinational minnenratta.wordpress.com

    Some interesting points here, some others needs to be challenged.

  28. The Greatest Sales Deck I've Ever Seen medium.com

    “1. Name a big change in the world; 2. Show there'll be winners and losers; 3. Tease the promised land; 4. Introduce features as "Magic Gifts"; 5. Present evidence that you can make the story come true.”

    site link ↗
  29. The product roadmap is dead: welcome to the age of problem roadmaps medium.com

    “Fall in love with your problems and not with your solutions.”

    site link ↗
  30. Book Summary of "Who: The A Method for Hiring" medium.com

    The essential of Who, a popular book on recruiting executives.

  31. Let's have no managers, instead of managers with no engineering experience medium.com

    The title is misleading, article's argument is: we don't need project managers if we already have product managers and scrum masters.

    site link ↗
  32. You're Not Managing a Team of Software Engineers, You're Managing a Team of Writers medium.com

    Because writing software is “a creative process which is by its nature unpredictable and personal, in an environment which craves certainty, predictability and consistency.”

  33. Mental Models I Find Repeatedly Useful medium.com

    Huge compiled list of mental models. Became the basis of book.

  34. Levels of abstraction in engineering management medium.com

    Another take on the differences between Manager, Manager of Managers, Head of Org and Head of Function.

  35. All the best engineering advice I stole from non-technical people medium.com

    “It's intriguing that the stuff that really seems to make a difference in the quality of software never seems to be about software.”

  36. Strong Opinions, Weakly Held — a framework for thinking medium.com

    “Allow your intuition to guide you to a conclusion, no matter how imperfect — this is the 'strong opinion' part. Then – and this is the 'weakly held' part – prove yourself wrong.”

  37. The different skills needed to be a successful CTO madewithlove.be

    The premise is a little misleading, as what is detailed there is the journey, in a startup, of the technical founder growing with the company to become a CTO. At which point the position described in the article is not CTO, but VP of Engineering.

  38. 100+ Lessons Learned for Project Managers llis.nasa.gov

    122 aphorisms providing insights into NASA project management success. Covers design, decision-making, managing staff, working with superiors and contractors.

  39. Recurring opinions or productive improvements — what agile teams actually discuss in retrospectives link.springer.com

    An 3-years analysis of a team's retrospectives, with dire conclusions: people keep forgetting what they already learned, keep discussing unsolveable problems out of their control, and keep debating opinions based on biased interpretations or incorrect understandings.

    site link ↗
  40. levels.fyi levels.fyi

    💸 Compares salary range, compensation charts, and benefits across big tech companies.

    site link ↗
  41. How the Digg team was acquihired lethain.com

    Acqui-hire of a whole team can be seen as a type of reorg. In which managers will have to negotiate the new employment contracts in bulk in one or two days: “Because acquihires are “star” oriented, if you're a senior leaders who doesn't explicitly refuse to move forward…

    site link ↗
  42. Developers spend most of their time figuring the system out lepiter.io

    “A hand drawn picture about the current system is a belief. Decisions should never be based on beliefs. Not in engineering. (…) As software is highly contextual we cannot predict specific problems. We can only predict classes of problems.” And that's why it is hard to estimate…

  43. I coached CEOs, founders, VCs and other executive: These are the biggest takeaways leowid.com

    Excerpt: “We're all just big, complicated bags of emotion walking around; Power comes with the ability to receive a No; Learning to manage your focus, not your time.”

  44. Team Leader Venn Diagram larahogan.me

    “A tool for gaining a shared understanding of responsibilities”.

    site link ↗
  45. Work at different management levels larahogan.me

    A great progressive breakup of what it feels like to work at different levels of management.

  46. Manager Energy Drain larahogan.me

    “How do I handle how tired I am as a manager? 1. Defrag your calendar; 2. Delegate messy and unscoped projects; 3. Say no.”

  47. Questions for our first 1:1 larahogan.me

    A personal list of high-level questions from a manager.

  48. Dear Startup: You have no idea how much that costs kyleprifogle.com

    “We are completely clueless about how long things should take.” Here is a trick to handle expectation of unreasonable estimates.

  49. The Good, the Bad and the Ugly Standup kristoff.it

    Author experienced 3 formats of stand-ups before ending with one working for his team, and concludes that “the details that make up a good meeting are subtle and the pursuit of an artificial standard of aesthetics will prevent you from doing the necessary experimentation to…

  50. next page of items loading…