I just spoke at my first ever conference. Thank you, @reactweek, for letting me talk about how we use hooks at @onepeloton. It was a blast! Interested parties can find my keynote and examples here: https://t.co/ew7Jljnrin
@jasonbrennan I wanna see the heroes win after an AI villain reboots suddenly. The explanation from one of the devs in the epilogue is “if we ever encountered an invalid state we just dumped all memory and started over 🤷”.
@markdalgleish@tailwindcss As someone who loves typesafety and has held out on tailwind, I think this would help. A big part of tailwind never clicking with me has been “it feels like a lot to learn”, and autocomplete/tooltip docs would _really_ help.
@BroaderImpact I’m a big fan of pair-programming something relatively mundane. Talk through the project like you would a coworker. Don’t expect them to know everything on the spot. Let them google. Make it feel real. It lets you both get a sense of what it’s like to work together.
Programming is chaotic magic. There are no rules. You ask a game dev “Can the player summon a giant demon that bursts from the ground in an explosion of lava?” and they’ll say “sure, that’s easy” and then you’ll ask “can the player wear a scarf?” and they’ll go “oof”
@TracketPacer I think it’s also totally okay to not love your job. Every time I hear someone say “no one wants to work” I immediately want to say “and that’s okay!”. I like my job, but there are plenty of days that I don’t wanna work. And that’s okay.
@KatieFujihara@cherthedev Comments are usually the best place to say why something is happening. Good abstractions can make it really clear what we are doing, but often aren’t great at explaining why we we are doing it.
@moyix If this is a case of “I like the extension I just don’t want it to bug me on startup” I don’t have any advice. But I do regularly disable extensions in projects which is still annoying to have to do but not as bad and VSCode remembers in your user settings.