|
|
|
|
|
|
by somerando7
1568 days ago
|
|
|
I'm curious as to why CTO's or companies spend time writing these types of blogs. They're clearly aimed at programmers but: 0 interesting/unique content. Seems like it's copy pasted arguments from any discussion of Rust. Also, the part about a CTO asking other CTOs to give him a rundown of Rust vs Go is just comical to me... In total, as a programmer, I would be less likely to apply to work at a company like this. |
|
|
- For themselves, It documents their rationale and represents the first time they articulate this design decision to the public. It may help them calibrate how they talk about their engineering choices.
- For their customers, it signals something about their product. Rust has a reputation for being a language that can create memory safe systems, which increases reliability and robustness of software. This article serves the purpose to signal to their customers that the company values memory safety as part of their engineering practices.
- For their current and potential employees they signal about their corporate culture. They mention soon into the piece that they choice this particular piece of technology is welcoming to trans individuals, which might be interesting to know if you wanted to work there.
- For other CTOs it provides an anecdote about their experience and decisions, so hopefully other companies can make better decisions. Creating a climate where business decisions are communicated openly and honestly I think is a positive for all businesses.
I dunno, seems like a fine article to me with plenty to say and lots of people to say it to.