Links why dtos in java

• How to use Java DTOs to stay secure: Short and sweet article about why the dto pattern exists. Security. Don’t send back more than needed to fulfill a requests as a baseline rule of thumb seems good to me.
• Conway’s Law: A system’s design resembles the communication patterns of the teams that built it. Interesting idea is to structure teams working on the same system at the outset along the module boundaries you’d like to see / encourage. We can use the effect to advantage rather than just accept it’s inevitable influence.
• Six Coding Interview Formats to Replace LeetCode Bullshit: This is nice. Much better than an algorithmic question + optimization. The idea is to do something that more closely resembles what people will do in work.
  • Solve a Problem with Code
  • Integrate with an API
  • Investigate a Bug (Failing test case?)
  • Write a Technical Proposal (take home)
  • Implement a Feature (give access to a codebase + a change spec, take home)
  • Review Code (comprehension, empathy, mentorship, constructive feedback, writing, judgement)