> The core of what we were doing (Writing code) dictated the core of our tool kit (IDE).
>
> Now that we're not writing code anymore it's very exciting to see how this unfolds in the tool kit.
So maybe the text area in your IDE becomes read-only. Even when not actively debugging, you still need to read code and efficiently browse through it as you review it. Because you always review code, don't you? Don't you??
For what it's worth, it's what caught my attention. I wouldn't have found it so captivating if it had only said "Fixing Google Nano Banana Pixel Art". To be clear, it's not because of Rust in particular. It would have been the same if it said "with C#", or "with Python", or even just "programmatically". And on that note: I feel disappointed. I thought I would be reading about the development process, and not just a product presentation.
After a certain number of open tabs, the titles are less truncated with vertical tabs than horizontal tabs. You also have more of the titles in your center view if you have the text distributed in a more rectangular shape than a technically-also-rectangular-but-much-more-elongated shape.
Language is defined by its speakers, as basically a "vote". I'm going to keep voting for "literally" meaning "this actually happened" as long as it's practical, because 1) there are dozens of other ways to emphasize something 2) we need some way to say "this is not an exaggeration".
Why a quantum leap isn’t the length of an Ångstrom will always sadden me. I’m sure there are other scientific concepts you can use to describe a Great Leap Forward…
So maybe the text area in your IDE becomes read-only. Even when not actively debugging, you still need to read code and efficiently browse through it as you review it. Because you always review code, don't you? Don't you??
reply