Justin Beall

@dev3l_

Seasoned Software Engineer, Craftsman, Budding Technical Coach

Cleveland, OH
Vrijeme pridruživanja: ožujak 2012.

Tweetovi

Blokirali ste korisnika/cu @dev3l_

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @dev3l_

  1. Prikvačeni tweet
    25. ožu 2018.

    My project results for the month of November: - Books: 1.92 - Audio Books: 1.86 - GitHub: 42 commits (open source) - Podcasts: 19 - Blogs: 82 - Tweets: 319 Specific details can be found here:

    Poništi
  2. proslijedio/la je Tweet
    prije 8 sati

    No real change is possible without psychological safety, so start there.

    Poništi
  3. proslijedio/la je Tweet
    2. velj

    Code should contain all the comments it needs. Pro-tip: write code to need fewer comments.

    Poništi
  4. prije 22 sata

    Dockerized Python Flask app to AWS ECR/ECS using CircleCI - A tutorial to push a Python Flask Docker container into AWS using CircleCI. Nerding out for the weekend!

    Poništi
  5. proslijedio/la je Tweet
    31. sij

    I know it sounds so reasonable and people spend so much time on it, but it just doesn’t actually work very well. You aren’t going to estimate your way to predictability. People sure have tried hard, with the best intentions, and I’m not making fun of anyone here.

    Prikaži ovu nit
    Poništi
  6. proslijedio/la je Tweet
    31. sij

    My approach for helping struggling software teams/orgs never begins with "improve predictability." When asking for the P word, clients usually need something entirely different, like actual cross-functional teams (instead of component teams), better alignment with execs, etc.

    Poništi
  7. proslijedio/la je Tweet
    1. velj

    Always phrase your commit messages in the imperative.

    Poništi
  8. proslijedio/la je Tweet
    31. sij

    What are some reasons we can’t forecast properly? 1. Start date uncertainty 2. The assumption that “size” of work is the main contributor to lead-time (when it's idleness) 3. Over-utilization – people not working on what you think they are, but totally busy 4. Dependencies...

    Poništi
  9. proslijedio/la je Tweet
    27. sij

    The daily standup isn’t a status meeting—it’s a *coordination* meeting. If you’re not planning how to work together, but only reporting status, you can cut it. Or start collaborating more.

    Poništi
  10. proslijedio/la je Tweet
    29. sij

    While pair programming all-day, everyday is never going to be my speed, there are still plenty of times where pairing is just the right. At Basecamp, we've been using Tuple for this to great reviews. Shatters the argument you can't remote pair in hifi ✌️

    Prikaži ovu nit
    Poništi
  11. proslijedio/la je Tweet
    29. sij

    “Treat people who know less than you with respect, deference, and patience.“

    Poništi
  12. proslijedio/la je Tweet
    28. sij

    I see these Agile forecasting anti-patterns - 1. We focus on end date NOT start date 2. We don’t discriminate uncertain work from commonplace 3. We value certainty more than delivered value - We close down options too early - We avoid doing super-valuable risky things

    Poništi
  13. proslijedio/la je Tweet
    27. sij

    I distinguish quite strongly between "readability" and what I call "scannability". I think that our trade's pedagogues, even our very good ones, conflate the two, and in so doing inaccurately describe programming and ineffectively prescribe remedies.

    Prikaži ovu nit
    Poništi
  14. 28. sij

    If You Want to Change the World, Start Off by Making Your Bed - William McRaven, US Navy Admiral Start off the day completing a task the right way Measure a person by their heart Hope is powerful - only takes one person ^6m

    Poništi
  15. 25. sij

    Swagger and Web API - Part I: Adding Swagger to Web API project - Help page package is a good start but lacking things like discoverability and live interactions. This is where Swagger comes to the rescue

    Poništi
  16. proslijedio/la je Tweet
    22. sij

    One of the top most damaging pieces of advice given by largely non-technical people is: "Start with , and once you've gained experience with it, then adopt the technical practices." That either never occurs or happens after you've produced a big ball of mud.

    Poništi
  17. proslijedio/la je Tweet
    21. sij

    Learning is literally part of the job. A company that forces all learning outside the "normal" workday are actually forcibly extending the work day. This is an abuse situation, not a "wouldn't it be nice" situation. Same reasoning applies to "lunch and learns".

    Poništi
  18. 19. sij

    Started reading: Accuracy and Precision for Long Range Shooting: A Practical Guide for Riflemen - Brian Litz "In order to get better at hitting targets, we must understand what causes us to miss targets." Weapon Employment Zone (WEZ) - statistical analysis ^307p

    Poništi
  19. 18. sij

    Principle: - P PC Balance (Production / Production Capability) Priority to the Improvement of daily work surpasses daily work Attitudinal perception has a profound impact Use your RNI - Resourcefulness and initiative

    Prikaži ovu nit
    Poništi
  20. 18. sij

    Trust is the glue of life Where we stand depends on where we sit Inside out paradigm shift Interdependence does not subtract from independence Teach the material within the next 48 hours H1 - Be Proactive Between stimulus and response we have the power to choose

    Prikaži ovu nit
    Poništi
  21. 18. sij

    Started listening to: The 7 Habits of Highly Effective People - Powerful Lessons in Personal Change - Match the goal to principal The lens itself shapes how we see the world Inside out - examine your own motivations against your highest values ^704m

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·