text stringlengths 0 1.39k |
|---|
• Software used for development |
• Code editors: Macvim, VS Code, Neovim |
• Vim setup and customizations (Brian Douglas' 1,200-line vimrc) |
• Tmux integration with Vim |
• Virtual machines and SSH connections for robustness |
• Hardware discussion: M1 Mac Mini, MacBooks, audio interfaces |
• Port forwarding and SSH config for accessing local hosts remotely |
• Using SSH to run a terminal-based audio setup and an iPhone app simultaneously |
• GitHub Codespaces for running development environments remotely, including using Vim in VS Code |
• Remote collaboration tools, including Codespaces and live sharing in VS Code |
• Experiences with remote work due to the pandemic, including working on different teams and companies |
• Discussion of productivity and workflow in a remote-centric world |
• Discussion of terminal emulators and their features |
• Comparison of iTerm and Terminal.app on Mac |
• Introduction to Kitty terminal emulator and its advantages (GPU rendering, ligature support) |
• Use of ligatures in font environments and potential performance issues with certain terminals |
• Personal productivity tools and methods, including Roam Research and daily notes/priorities |
• Discussion of note-taking and organization systems for personal and team use |
• Zettelkasten method for processing data inputs |
• Calendly and Google Calendar use for meeting scheduling |
• Obsidian and Dropbox Paper as note-taking tools |
• GitHub projects for task management and issue tracking |
• Using GraphQL API to automate blog post generation from issues |
• Automation with GitHub Actions and OneGraph API aggregation |
• Integration of Discord, Twitch, and other APIs for notification and content delivery |
• Client vs Relay |
• GitHub comments as blog post reactions |
• OneGraph tool and its integration with GitHub |
• Free services for development (Actions, OneGraph) |
• AWS pricing issues and charges for abandoned projects |
• Personal productivity tools and automation systems (OmniFocus) |
• Discussion of software for development and productivity, including automated workflows and single-inbox organization |
• Mention of specific tools such as OmniFocus, Vim, and Spectacle |
• Comparison of expensive tool options, including OmniFocus's $80 price tag |
• Hardware discussion begins with monitors and ideal setup configurations |
• Participants share their experiences with ultra-wide monitors for coding and productivity |
• Chrome extension Easy Window Resize mentioned as a convenient tool for resizing browser windows |
• RDM software used to change screen resolution on the fly discussed |
• Twitch streaming and hardware setup discussed, including use of Windows PC, Elgato capture cards, and OBS software |
• Discussing screen sharing and the challenges of getting the best output on remote setups |
• Introducing a resize extension that can improve screen sharing quality |
• Sharing keyboard preferences, including Apple Magic Keyboard and Magicforce ($39) mechanical keyboards |
• Touching on mouse setup, with the use of trackpads and Apple Magic Mouse |
• Discussing exercise routines for programmers to counterbalance sedentary work habits, with a focus on kettlebells |
• Mentioning camera equipment, specifically a Canon EOS M200 camera |
• The host, Brian Douglas, discusses his camera and lens setup, specifically mentioning the Canon camera and Sigma 16mm lens. |
• He explains how he chose the camera and lens based on their compatibility with memory cards. |
• Brian also talks about the importance of good lighting in video production, sharing a tip for controlling lighting by using blackout curtains. |
• The host is complimented on his setup, which he attributes to learning from YouTube tutorials. |
• Nick Nisi recommends an Amazon Basics monitor arm that he uses in his own setup. |
**Nick Nisi:** Hello, and welcome to JS Party. I am your host today, Nick Nisi. Hoy-hoy! And I am joined today by Kball. Kball, what's up?! |
**Kevin Ball:** Hello, hello. Calling in from a beautiful vacation home, excited to be on the air. |
**Nick Nisi:** I'm so jealous of your vacation home. It looks beautiful in the picture you posted in our Slack... Which you can join at Changelog.com/community. Join today and see Kball's amazing view! |
**Kevin Ball:** \[laughs\] |
**Nick Nisi:** And we have a special guest today - we have Brian Douglas. Brian, what is up? Hello. |
**Brian Douglas:** Hello! Glad to be here. I am super-interested in your view, too. All I see is a blank wall behind you though. |
**Kevin Ball:** That's true... I decided to go for internet connectivity over view while recording. |
**Brian Douglas:** It makes a lot of sense. |
**Nick Nisi:** Probably a wise choice, for sure... So today we are going to be talking about -- well, the placeholder title that we have is "Software and hardware for easier development." But really, we're gonna be talking about our suite setups. Brian, we have you on the show to talk about yours as well... I can just ... |
But yeah, we are gonna do that, and we thought we would start off with some software... So maybe let's start on that side and talk about some of the software that we use to make development and/or streaming easier. So why don't we start with development, and maybe start with things like where we all do our development,... |
**Brian Douglas:** I am in between -- I use Macvim as my main driver. I've been a Vim user since Thanksgiving of 2014. I took a week off and learned Vim, and I just can't really pry it away from my hands... But I also use VS Code. VS Code mainly because Vim is -- it's long in the tooth, and getting things like the Type... |
**Nick Nisi:** \[04:18\] I hear you, I hear you... You're making this really hard, because I did tweet right before this that I was gonna try really hard not to make this a Vim party... But I didn't know that you use Vim, so now it's really hard. \[laughs\] |
I do use Vim... I use Neovim for all of my development. I've used Neovim since probably 2015... But Vim straight away since 2011, probably. I'd have to go back and look at my dotfiles for the first commit, because I started that, and then I just haven't stopped. Yeah, I use that... I did go through the grueling setup. ... |
**Brian Douglas:** Mine's huge as well... |
**Nick Nisi:** Yeah... \[laughs\] |
**Brian Douglas:** But are you using IntelliSense though? |
**Nick Nisi:** I am. I'm using a plugin called coc.nvim (Conquer of Completion). That gives you access to the LSP, and it does IntelliSense, and refactoring, and GoTo reference... All of that cool VS Code stuff, right in Vim. So it's the best of both worlds, for sure. What about you, Kball? |
**Kevin Ball:** Well, let me tell you... I also am a Vim user, but I'm gonna take my Vim heritage back to 2003, when I first learned Vim for a Fortran class at my university... And have stuck in that -- I cheat on the setup front, so I actually stole Nick's setup. He publishes it on GitHub, so you get to download it an... |
I will say -- I should spend a little bit more time understanding it, because a couple times I've tried to modify it and it ends up a little funky. I have right now something I need to fix for my TypeScript setup that I don't love... But I'm a Vim user, and I'll go one dimension deeper, which is I also have my terminal... |
**Nick Nisi:** Yeah, I too live inside of Vim, inside of Tmux, and find that to be a fantastic setup. |
**Brian Douglas:** I attempted that -- so my previous employer was Netlify, and I was like the only person doing frontend, but everybody else touched all the backend, so I was indoctrinated with Tmux... But it never stuck. So I'm familiar, but I still just use the regular MacVim. |
**Kevin Ball:** A fun thing that can happen when you start doing all that though... So I had an incident almost a decade ago now; it was a coffee/MacBook incident, where the coffee met the MacBook... |
**Brian Douglas:** I'm familiar. |
**Kevin Ball:** Yeah, it was not a good time. And I learned, by the way, that if you Google for "How to get liquid out of a MacBook", or something like that... I am not the first person to have this. Google tells me there are over a million people who have had this problem and written about it, and went forward \[unint... |
So having that type of build environment that can live in the terminal in that way and has all the power that you want actually has a lot of robustness effects, as well. |
End of preview. Expand in Data Studio
2021 JS Party Transcripts
Complete transcripts from the 2021 episodes of the JS Party podcast.
Generated from this GitHub repository.
- Downloads last month
- 51