Towards Tooling; A Look at What is Missing From our Toolbox
summary
Claims that Ruby has great testing and deployment tools but no standard linting and weak visualization gaps are backed by specifics: RubyMine offers IDE-level debugging, memprof/perftools.rb show heap and CPU profiles, Reek/Flog/Flay plus Code Climate flag style but not semantics, Brakeman finds Rails security issues, and tiny projects like Heckle and FuzzBert try fuzzing. The concrete gap is missing robust static analysis and symbolic-execution tooling that generates real failing inputs and automated tests. static analysis and fuzz testers
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:29Are Rubyists Good at Testing
- 3:12Goals
- 5:17Tools
- 7:21Visualization
- 12:13Web Inspector
- 15:27Profilers
- 17:52Code Climate
- 20:30Ruby Lint
- 23:51Breakman
- 26:39Fuzz Testing
- 30:01Symbolic Execution
- 33:10Tools for Symbolic Execution
- 35:52Recap
related talks
27mThe state of Ruby dev tooling
01h 03mSwift Tools for Software Crafting 2024
32mSAST and Sensibility: A Rubyist’s Guide to Static...
18mJavaScript tooling has a blind spot: codebase-wide questions
41mWhat Developing With Ruby Can Teach Us About Developing Ruby
39mSteal This Talk: The Best Features Ruby Doesn't Have (Yet)
43m"Ruby Smells"
57mFuture of Developer Acceleration with Rails