Course code: WEB-35
  • Years with company: 0
  • Years programming: 10
  • Primary programming language: Rust
  • Other programming languages: C, C++, Python
  • Unit test harnesses: Cargo, CMake (ctest), gtest, gmock
  • Something else: I also work on open source Rust crates
  • Test practice now: I typically add unit and integration tests when I am working on something that could have runtime errors that could result from my code, like parsers, algorithms, etc. In Rust I often avoid writing tests by using the type system to make certain error cases impossible.
  • Target system: I typically develop on Ubuntu, but I recently got a Mac with Apple Silicon, and I also use Windows. Basically, everything.
  • Dev tools: I typically use VS Code + Rust Analyzer + Cargo.
  • Build time: 11-30 seconds
  • Coding standard: I like to see the open source ecosystem reused where appropriate and contributions upstream rather than internal forks.
  • Function too long: If it is hard to read because the comments and code aren't sufficiently high-level to make reading easy then it should be split to improve code readability.
  • Code reviews: We often develop in a mob, allowing for live code review.
  • Code time: 80
  • Test time: 15
  • Debug time: 5
  • Favorite thing about dev: If we develop reusable, clean, and maintainable software, it can be evergreen and build upon the existing work of others to get us to a higher level of coding abstraction.
  • Least favorite thing about dev: I don't like when coding is performed without a plan for the overall architecture and code reuse.
  • Tdd knowledge: I am familiar with the process of writing tests in advance and making incremental changes to avoid getting ahead of yourself. I only do it when I am trying to implement something that is non-trivial.
  • Why are you attending: For work and to learn =)
  • Back