Also one of my favorites is discworld scientist experimenting with ftl communication through succession by “modulating” a king above a pit of sharks an measuring his son at the other end of the world for “kingness”
3,667 karma · joined September 9, 2013
Also one of my favorites is discworld scientist experimenting with ftl communication through succession by “modulating” a king above a pit of sharks an measuring his son at the other end of the world for “kingness”
Headlines: 3.000 governmental sites use tracking cookies illegally, over 1.000 database management interfaces are publicly reachable, 99% of governmental email is poorly encrypted.
Now that I think about it, I think I haven't hit the tab key for indenting code in ages. I use cmd+] and cmd+[ to indent/unindent blocks of code in my default editor and doing so habitual for single lines now as well that I have 'unlearned' the tab key. For the few occasions I'm in a editor that does not have this keybinding I am actually hitting spacebar a few times as it is more predictable than whatever amount of spaces using the tab key would give me (or if it gives me a tab instead of spaces) and me having to dance around with the backspace key as well. Some editors I think use tab/shift-tab to indent/unindent blocks/lines of code, but not insert a tab. But then you are having 2 modes for the same key depending on the context.
Also the Battleship New Jersey YouTube channel has some nice content on this: https://www.youtube.com/watch?v=szxNJydEqOs
I heavily doubt that. A lot of people only care if it works. Just push out features and finish tickets as fast as possible. The LLM generates a lot of code so it must be correct, right? In the meantime only the happy path is verified, but all the ways things can go wrong are ignored or muffled away in lots of complexity that just makes the code look impressive but doesn’t really add anything in terms of structure, architecture or understanding of the domain problem. Tests are generated but often mock the important parts the do need the testing. Typing issues are just casted away without thinking about why there might be a type error. It’s all short term gain but long term pain.
If you mean the "When switching to an application, switch to a Space with open windows for the application" settings, this works only partially. When clicking the dock icon its behaviour depends on if there are windows in your current Space (virtual desktop) or not. And don't get me started on where macOS decides new windows should go.
Now I’ve settled with Zed as desktop editor/IDE and still use vim on remotes. The context switch between a desktop app en cli is big enough that it’s never a problem. I don’t even use the vim bindings in Zed.