Tweets

You blocked @justincampbell

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @justincampbell

  1. Pinned Tweet
    Undo
  2. Undo
  3. Jul 19

    👋 Do any y'all cool people know someone with Kubernetes, Terraform, and Go experience, who would like a job? Varying levels of each ok. My DMs are open. RTs appreciated.

    Undo
  4. Interesting that a slower regional rollout had the opposite intended effect: the global playerbase swarmed to the initial region

    Undo
  5. vim-go can now add `if err != nil { return ... }` and detects the return types

    Undo
  6. The tech here is interesting, but I really enjoyed seeing what GC behavior/pauses meant for their architecture choices, Google's costs, and the success of Go

    Undo
  7. qwwqerooiuyrewqzxnuiij

    Undo
  8. slicked eels

    Undo
  9. Jun 30

    If you'd like to try out our game it's up on itch! It's for Windows, MacOS, and Linux systems 📸✨👻👻

    Show this thread
    Undo
  10. May 8

    An HN thread gave me the opportunity to explain some of the realities and challenges of hiring remote. This is something I’ve wanted to write about for awhile since I find a lot of misconceptions around hiring remote.

    Undo
  11. Undo
  12. Go into conversations with lists of questions Use silence to allow others to fill in information

    Show this thread
    Undo
  13. “It’s hard to change strategy in the heat of battle” “This is our special sauce” “We can make changes in the next release” means - I know the process is not working - I’m scared change will make things worse - I don’t trust the team to handle this change

    Show this thread
    Undo
  14. “We’ve learned from the past and we’re now firing on all cylinders” “The next iteration is going to get us where we need to be” means - Shit was bad - It’s not any different now but we’re still optimistic - Need to sound confident to stakeholders

    Show this thread
    Undo
  15. “What we’re doing has never been done before” “The team is facing unique challenges” “We target a niche audience” means - We’re at risk of missing the deadline - We don’t know how to fix it - I don’t trust the people in the room to fix it

    Show this thread
    Undo
  16. Spend more time listening to people’s needs

    Show this thread
    Undo
  17. 1) To stakeholders, our work is extremely technical and they don’t fully understand it 2) That’s not their fault, it’s ours

    Show this thread
    Undo
  18. From at :

    Show this thread
    Undo
  19. “Code should communicate intent”

    Undo
  20. - Spend more time seeing your users use your software - Use visualizations to describe systems and potential features to stakeholders

    Show this thread
    Undo
  21. Notes from ’ talk at : - Legacy code is when author is not there - Use analogies to communicate change motivations - Diagram program flow to understand system - Keep a log of your work, decisions, what people are asking, etc for later self-reflection

    Show this thread
    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·