Jason Swett

@JasonSwett

Host of the Rails with Jason Podcast, author of Rails Testing for Beginners.

Sand Lake, MI
Vrijeme pridruživanja: svibanj 2009.

Tweetovi

Blokirali ste korisnika/cu @JasonSwett

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

  1. Prikvačeni tweet
    10. svi 2018.

    Want to get started testing Ruby/Rails but not sure where to start? Check out my easy (and free) Ruby Testing Micro-Course (featured in Ruby Weekly 390)

    Poništi
  2. prije 7 sati

    What are some of your favorite programming podcasts?

    Poništi
  3. prije 9 sati

    I only write two kinds of tests in Rails, for the most part: feature specs and model specs. I mostly skip view specs, request specs, helper specs, and everything else. More detail/explanation in the link.

    Poništi
  4. prije 12 sati
    Poništi
  5. 31. sij
    Poništi
  6. 31. sij

    Deploying a Rails application to AWS Elastic Beanstalk is typically a huge pain in the ass. I made a tutorial to help make it easier.

    Poništi
  7. 31. sij

    I've put some of my Production Rails videos up as a YouTube playlist. I just put up a new one yesterday.

    Poništi
  8. 31. sij

    Has anyone tried the "any new code must get a test" approach for adding tests to legacy projects? How did it go?

    Poništi
  9. 30. sij

    Having said all this, the coverage on my main app tends to hover around 97%. Not because I shoot for a high percentage but because I believe that coding is easier, faster and more fun when I write tests than when I don't. So skipping tests gives me the heebie-jeebies.

    Prikaži ovu nit
    Poništi
  10. 30. sij

    What about too little? Rather than looking to a coverage percentage, I'd ask: What's it like to work with the code? Is it fragile? Are deployments infrequent and risky? Are you afraid to touch stuff? Is the design poor? If so, you could probably use more tests.

    Prikaži ovu nit
    Poništi
  11. 30. sij

    Devs often wonder how much testing is too little or too much. I'll address the "too much" concern first: I've never ever encountered a team that writes too many tests. I've hardly even encountered a team that even writes ENOUGH tests. So, negligible risk at that end.

    Prikaži ovu nit
    Poništi
  12. 29. sij

    Ever wonder how other people go about writing tests in Rails? I write about it here, including how much of the time I do TDD, what kinds of tests I skip, and how I think about test coverage.

    Poništi
  13. 29. sij

    This obviously doesn't have anything to do with programming or really anything at all, this is just the kind of stuff I think about a lot because I'm not a normal person

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

    Interesting fact: It might not seem like presidents get shot that much, but 13% of presidents have been shot! (6 of 45) To put that in perspective, if I got offered a job that paid 100 million dollars a year but there was a 13% chance I'd get shot, I probably wouldn't take it.

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    28. sij

    I'm booking corporate training for Q2/Q3/Q4 of this year now. If you'd like me to come by your office and teach your team how to write fast Rails apps, let's do it!

    Poništi
  16. 28. sij

    I wish instead of whoami, pwd and ps, we had whoami, whereami and whatishappening.

    Poništi
  17. 28. sij

    My latest guest on Rails with Jason is ! Me and Sandi, along with guest , discussed: - Rails - Java and COBOL - Service objects and Interactors - Getting bitten by snapping turtles - Sandi's 11 bicycles Enjoy!

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

    Full Stack Panic ... that feeling you get when you read a JavaScript newsletter and don't recognize half of what's in it. 😭Nobody should feel it, but we all do!

    Poništi
  19. 27. sij

    Just thought of a great tagline for AWS Elastic Beanstalk: "Heroku for masochists"

    Poništi
  20. 27. sij

    When I'm stuck on a programming issue and I can't figure out a good solution, often I'll just move forward with a bad solution. It sure beats staying stuck, and once I've implemented my bad solution, a better solution often becomes abundantly clear.

    Poništi
  21. 24. sij

    For every piece of good-seeming advice there is an equal and opposite piece of good-seeming advice.

    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:

    ·